Welcome to Geeklog, Anonymous Tuesday, October 15 2024 @ 12:03 am EDT
Geeklog Forums
Bugs in Geeklog 1.4.0rc1
Page navigation
Standard "Go Daddy" Problem with Geeklog.
GoDaddy and Shield host etc.. Will NOT give LOCK access to your database.
Results in SQL error to error.log.
You as a user are not the owner of the database and cannot give yourself LOCK access to the databases.
As a fix users can comment out the following lines in Geeklog-1.4.0rc1
THIS IS NOT AN IDEAL FIX, and can cause comment to be lost in the database, overwritten, and data in the comment could be made public as technically two comments could end up with the same comment number.
Still if you have no choice here is the workaround that will get you going if your not afraid to lose a comment, or breach the security on a potential post.
847: // DB_query("LOCK TABLES {$_TABLES['comments']} WRITE");
873: // DB_query('UNLOCK TABLES');
978: //DB_query("LOCK TABLES {$_TABLES['comments']} WRITE");
997: //DB_query('UNLOCK TABLES');
Here's hoping we can get a warning file, and an option in the config file if we are stuck with a cheapy service provider who won't fix this for us.
Note: if its an option find a service provider that will give you LOCK access to your own database. No matter what they say, LOCK access will not allow someone to breach their security.
-Astrogen
GoDaddy and Shield host etc.. Will NOT give LOCK access to your database.
Results in SQL error to error.log.
You as a user are not the owner of the database and cannot give yourself LOCK access to the databases.
As a fix users can comment out the following lines in Geeklog-1.4.0rc1
THIS IS NOT AN IDEAL FIX, and can cause comment to be lost in the database, overwritten, and data in the comment could be made public as technically two comments could end up with the same comment number.
Still if you have no choice here is the workaround that will get you going if your not afraid to lose a comment, or breach the security on a potential post.
847: // DB_query("LOCK TABLES {$_TABLES['comments']} WRITE");
873: // DB_query('UNLOCK TABLES');
978: //DB_query("LOCK TABLES {$_TABLES['comments']} WRITE");
997: //DB_query('UNLOCK TABLES');
Here's hoping we can get a warning file, and an option in the config file if we are stuck with a cheapy service provider who won't fix this for us.
Note: if its an option find a service provider that will give you LOCK access to your own database. No matter what they say, LOCK access will not allow someone to breach their security.
-Astrogen
Status: offline
samstone
Forum User
Full Member
Registered: 09/29/02
Posts: 820
The blue menu bar (showing Preview, Editor, Publish Options, etc.) at the top of the Story Editor form does not use words from the language file, therefore it does not translate to other languages. I told all story admin to learn English quickly .
I hope this will be fixed before final release.
Sam
I hope this will be fixed before final release.
Sam
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Status: offline
andyofne
Forum User
Chatty
Registered: 08/31/02
Posts: 69
Status: offline
samstone
Forum User
Full Member
Registered: 09/29/02
Posts: 820
Quote by Dirk:
This has been fixes in CVS now.
bye, Dirk
Quote by samstone: The blue menu bar (showing Preview, Editor, Publish Options, etc.) at the top of the Story Editor form does not use words from the language file, therefore it does not translate to other languages.
This has been fixes in CVS now.
bye, Dirk
Now, nothing shows in the menu when the language is other than English.
Are these new words added to the language file?
----- Edited --------------
I saw the new lines in the English language file now. So please ignore this question.
Sam
Tom Duck
Anonymous
Here's a weird one: With both the Beta and RC, you can't change the comment mode on some pages between threaded, nested, etc. For example, try to change modes on the following page:
http://www.geeklog.net/article.php/geeklog-1.3.10#comments
It doesn't work (well, for me, anyway). This one works:
http://www.geeklog.net/article.php/geeklog-1.4.0b1#comments
Both examples are taken from the Geeklog Announcements page at:
http://www.geeklog.net/index.php?topic=announcements
http://www.geeklog.net/article.php/geeklog-1.3.10#comments
It doesn't work (well, for me, anyway). This one works:
http://www.geeklog.net/article.php/geeklog-1.4.0b1#comments
Both examples are taken from the Geeklog Announcements page at:
http://www.geeklog.net/index.php?topic=announcements
Status: offline
sakata
Forum User
Junior
Registered: 12/17/01
Posts: 25
Location:Japan
Hi, my post is actually not a bug report but some requests.
1. Is it possible to add 'img' in allowed_html tags.
2. When adding users with 'batch add', geeklog send e-mails to users. But I want to turn off this feature. It is good to select this feature using options.
3. For user name. 16 bytes are too short using Japanese name. Is it possible to modify it to something like 108 bytes?
1. Is it possible to add 'img' in allowed_html tags.
2. When adding users with 'batch add', geeklog send e-mails to users. But I want to turn off this feature. It is good to select this feature using options.
3. For user name. 16 bytes are too short using Japanese name. Is it possible to modify it to something like 108 bytes?
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by sakata: 1. Is it possible to add 'img' in allowed_html tags.
The IMG tag is filtered out for security reasons. You can easily add it (at your own risk), though, if your really want. See the FAQ for details.
Quote by sakata: 2. When adding users with 'batch add', geeklog send e-mails to users. But I want to turn off this feature. It is good to select this feature using options.
I don't really want to add new functionality at this point in the release cycle. Please submit a feature request once our project site is back online.
Quote by sakata: 3. For user name. 16 bytes are too short using Japanese name. Is it possible to modify it to something like 108 bytes?
The username is just that - a (short) user name, used for the login and as a "nickname". I don't think anyway would want to type in their full name just to log into the site, especially if you happen to have a rather long name ...
There's always the full name field in a user's profile where they can add their first and last name (currently limited to 80 characters, though that's a pretty arbitrary limit). We are working on making it possible to display the full name instead of the username everywhere in Geeklog (see $_CONF['show_fullname'] in config.php), but that's not fully implemented in 1.4.0.
bye, Dirk
Status: offline
sakata
Forum User
Junior
Registered: 12/17/01
Posts: 25
Location:Japan
Thank you for your reply.
I understand the situation.
That's a good idea!
I will wait it until 1.4.0 or 1.4.1.
Yusuke
I understand the situation.
There's always the full name field in a user's profile where they can add their first and last name (currently limited to 80 characters, though that's a pretty arbitrary limit). We are working on making it possible to display the full name instead of the username everywhere in Geeklog (see $_CONF['show_fullname'] in config.php), but that's not fully implemented in 1.4.0.
That's a good idea!
I will wait it until 1.4.0 or 1.4.1.
Yusuke
Status: offline
samstone
Forum User
Full Member
Registered: 09/29/02
Posts: 820
After years of using gallery, I still have to come back to search for the answer of why a user with Story Admin permission can't edit his or her own story. When I found the answer, I always wonder why I keep forgetting it is because the topic permission.
I wonder if this can be called a bug? Somehow, I feel this needs to be improve for userfriendliness, without compromizing privacy or security. Even Gallery has a config setting to allow owner to edit his or her own photo.
-----------------
After some thoughts, I think it is a bug because when a story is saved the permission boxes has owner read and edit checked. Since they are checked, logically the owner should be able to edit. Of course it is not a bug introduced by 1.4. It's an acient bug.
Sam
I wonder if this can be called a bug? Somehow, I feel this needs to be improve for userfriendliness, without compromizing privacy or security. Even Gallery has a config setting to allow owner to edit his or her own photo.
-----------------
After some thoughts, I think it is a bug because when a story is saved the permission boxes has owner read and edit checked. Since they are checked, logically the owner should be able to edit. Of course it is not a bug introduced by 1.4. It's an acient bug.
Sam
Status: offline
samstone
Forum User
Full Member
Registered: 09/29/02
Posts: 820
Tom Duck
Anonymous
Tom Duck
Anonymous
Quote by Tom Duck: If a user submits a comment with orphaned html tags, this can create some havoc. For example, if the user forgets to close a bold tag, then all following user comments become boldfaced. Ideally these orphaned tags should be stripped out, or the comment be rejected due to malformed html.
I mean: If a user forgets to use a closing bold tag some time after the opening bold tag...
Status: offline
Blaine
Forum User
Moderator
Registered: 07/16/02
Posts: 1232
Location:Canada
Quote by Julie: With the new 1.4 line I continue to get javascript (?) error,
even with the RC just released. It happens with IE 5.5.4134
for example I continue to get this in this page
http://demo.geeklog.net/admin/syndication.php
/! A runtime error has occured. Do you wish to debug ?
Line 218 Error : Could not get the cursor property
Clicking ok or debug shows error at line 221 or something like that
and a loop of alert boxes follow.
Switching to some other browser may be suggested but what is the problem
as this type of error was never seen in any of the previous versions.
even with the RC just released. It happens with IE 5.5.4134
for example I continue to get this in this page
http://demo.geeklog.net/admin/syndication.php
/! A runtime error has occured. Do you wish to debug ?
Line 218 Error : Could not get the cursor property
Clicking ok or debug shows error at line 221 or something like that
and a loop of alert boxes follow.
Switching to some other browser may be suggested but what is the problem
as this type of error was never seen in any of the previous versions.
Not sure of the cause to this JS error as I don't see the error with IE6 and FireFox - testing on the demo site and my devel site.
Geeklog components by PortalParts -- www.portalparts.com
Status: offline
ByteEnable
Forum User
Full Member
Registered: 10/20/03
Posts: 138
Status: offline
Dirk
Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by Tom Duck: It seems that if one changes their user preference, they no longer show up by username in the Who's Online block, but are instead listed as a Guest User.
Can't reproduce that. Are you using a theme that was properly updated? Does it also happen with the Professional theme?
bye, Dirk
Status: offline
tomw
Forum User
Full Member
Registered: 08/12/02
Posts: 300
Status: offline
Blaine
Forum User
Moderator
Registered: 07/16/02
Posts: 1232
Location:Canada
Mike Edwards
Anonymous
I've noticed that, in the advanced editor, in the body textarea, it keeps adding a "br" tag there in HTML mode if the Body Text box is left blank. I can see it when I switch into Plain Old Text. But if I erase it and flip back to HTML mode, it reappears. To make matters worse, it shows up on the article as (1 word - read more) even though there's no other text there. Weird.
It seems like there's an errant newline somewhere in there that gets repeatedly conveted to a "br" and inserted in there if the body field is blank. I just can't figure out where it's coming from.
It seems like there's an errant newline somewhere in there that gets repeatedly conveted to a "br" and inserted in there if the body field is blank. I just can't figure out where it's coming from.
Page navigation
All times are EDT. The time is now 12:03 am.
- Normal Topic
- Sticky Topic
- Locked Topic
- New Post
- Sticky Topic W/ New Post
- Locked Topic W/ New Post
- View Anonymous Posts
- Able to post
- Filtered HTML Allowed
- Censored Content