[geeklog-devel] State of the Na^Wproject

[Blaine Lang]

Hum, the LOCK TABLES call in comment.php is generating a SQL error for me. 
I've contacted my host admin to change my DB perms.
I wonder if others will see this issue with 1.3.10 -  I suspect we would 
have heard by now.

As soon as I get the perms updated, I will test.

Blaine
----- Original Message ----- 
From: "Vincent Furia" <vfuria at gmail.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Saturday, October 30, 2004 10:01 PM
Subject: Re: [geeklog-devel] State of the Na^Wproject


> Vinny, how are things re: comments in plugins?

I think its done.  Just a minor problem in how comments.php was
grabbing variables.  It's working on my test site (using geeklog.net
DB).  Though I just noticed that I'm using the most recent (1.3?)
version of filemgmt even though geeklog has an ealier version (1.2?)
installed.  I don't think that invalidated my tests.

Blaine, can you try out the most recent lib-common.php and comment.php
with your filemgmt to make sure they work as you'd expect (as they
used to in 1.3.9)?

Thanks,
Vinny

On Sat, 30 Oct 2004 22:10:40 +0200, Dirk Haun <dirk at haun-online.de> wrote:
> Okay, I think I've fixed the issues with personal events (see CVS). Here
> are a few remaining issues:
>
> As mentioned in my other post, the regexp in COM_makeClickableLinks could
> need some work.
>
> Actually, I've been thinking if it was a good idea to do the parsing for
> links at display time. We've seen that parsing for the "related" links in
> stories used a lot of CPU power (hi to groklaw.net) - and now that that
> has been resolved, we're doing the same thing again elsewhere.
>
> The same applies to the autotags / autolinks.
>
> For the clickable links in text posts, it would be possible to do the
> parsing when they are saved (both comments and stories), although there
> are one or two issues with that:
>
> 1) Should we undo the change when a plain-text story is edited later?
> 2) Comments don't store whether they had been posted in plain text or
> HTML - that's done at display time by running yet another regexp over
> them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.
> clickable links + nl2br) when saving them). But that would mean that old
> comments would have to be converted.
>
> The whole point of autolinks, however, is that they ARE dynamic, so I
> guess the only way out there is to introduce an option to disable them.
>
> Thoughts on this?
>
> Vinny, how are things re: comments in plugins?
>
> That's all I can think of at the moment (well, it's enough ...).
>
> bye, Dirk
>
> P.S. I'll be offline for the next couple of days (back Thursday).
>
> --
> http://www.haun-online.de/
> http://geeklog.info/
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel
>
_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel