Tony,
>Report this as a bug to
>http://project.geeklog.net/ and we'll need to finally make this a
>priority and get it working right.
The actual problem here (that you could have a single quote in a topic
ID) has already been fixed in Geeklog 1.3.9rc1. To quote from the history
file:
- Single
Ah, good catch. I read through too quick. Anyway, the thing that
annoys me most about Geeklog right now is the fact that topic ID's are
text-based instead of numeric values and, unlike most other primary keys
in Geeklog, these you can key in yourself. This is simply bad legacy
code from Geek
I am not using the Journal Plugin. Just staight-up geeklog. The topic I
was creating just happened to include the word Journal.
Tony Bibbs wrote:
Again, note that the *fix* will happen in the journal plugin's code.
If you find it and fix it please send the fix to
[EMAIL PROTECTED] Thanks fo
Again, note that the *fix* will happen in the journal plugin's code. If
you find it and fix it please send the fix to
[EMAIL PROTECTED] Thanks for looking into this...
--Tony
Chris Besignano wrote:
I realized why the error occured but was unable to resolve the issue.
Geeklog simply locked u
Drago, yes, I realize that. Please note that this *isn't* a geeklog
problem, it is a problem with the journal plugin that I wrote. It's up
to each individual plugin to handle their DB interaction. When I get
around to it I'll make the fix, I just wanted to provide you the short
term fix to y
I realized why the error occured but was unable to resolve the issue.
Geeklog simply locked up and kept returning the SQL error no matter
which page I accessed. I agree that this is something that should be
validated. It shouldn't be much work to make it happen, maybe I'll poke
at it this weeke
This is something geeklog should protect against. Either escape the data, or
validate it prior to injecting it into SQL. If there are plans to do this in a
future version that's fine, but I don't think it's reasonable for geeklog to
expect users to provide it with valid data.
The other thing I wou
the problem is the journal name has a single quote (') in it. Change
"Chris' Journal" to "Chris Journal" and all would be well.
--Tony
Chris Besignano wrote:
Hello,
I am runnning geeklog 1.3.8-lsr4 on linux. I attempted to add a new
topic, but left a space in the topic id. Now I get this S
ary 02, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [geeklog-users] An SQL error has occured. Please see
error.log for details
I couldn't get the PHP to compile. Like I said in my last repsonse, I
just enabled it instead. So perhaps it's something related to PHP.
I'll put some effort
lf Of
[EMAIL PROTECTED]
Sent: Monday, February 02, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [geeklog-users] An SQL error has occured. Please see
error.log for details
I couldn't get the PHP to compile. Like I said in my last repsonse, I
just enabled it instead. So perhaps it's somet
I couldn't get the PHP to compile. Like I said in my last repsonse, I just
enabled it instead. So perhaps it's something related to PHP. I'll put some
effort into getting it to compile though, when I get some free time.
I really have to express my appreciate though for helping as much as you ha
I beg your pardon. You are correct. I installed mysql-standard-4.0.17.dmg.
PHP I enabled, that's right.
Quoting Dirk Haun <[EMAIL PROTECTED]>:
> Neil,
>
> >I'm using Mac OS X.3 Panther 'Client'.
> >
> >It came with mysql, just not configured to run automatically at startup,
> ditto
> >for
Neil,
>I'm using Mac OS X.3 Panther 'Client'.
>
>It came with mysql, just not configured to run automatically at startup,
ditto
>for php.
Hmm, has this changed with 10.3? Previous versions included PHP
(disabled), but not MySQL.
bye, Dirk
--
http://www.haun-online.de/
http://www.macosx-faq.de
I'm using Mac OS X.3 Panther 'Client'.
It came with mysql, just not configured to run automatically at startup, ditto
for php.
Quoting Dirk Haun <[EMAIL PROTECTED]>:
> Tony,
>
> >This is wrong:
> >
> >"(.sid = gl_comments.sid)"
> >
> >there should be a table name before ".sid".
> >
> >Not sure
Tony,
>This is wrong:
>
>"(.sid = gl_comments.sid)"
>
>there should be a table name before ".sid".
>
>Not sure why that is happening, though.
We've been through this a couple of times in the forums already. Seems
like Apple is shipping some, how should I put it, not-quite-working
components with
This is wrong:
"(.sid = gl_comments.sid)"
there should be a table name before ".sid".
Not sure why that is happening, though. Submit this as a bug even
though experience tells me this is usually a user-mistake during the
installation process rather than a bug. We'll try and reproduce it.
As it turns out set $_CONF['hidenewcomments'] = 1;'ing seems to mask the
symptoms.
Thanks go out to Dirk! :)
Neil D
[EMAIL PROTECTED] wrote:
Hi,
I just installed GL last night and finally got it running this morning.
The page comes up but it says :
An SQL error has occured. Please see erro
17 matches
Mail list logo
