Geeklog 1.3.8-1 bugfix release

Authored by: Euan on Saturday, August 09 2003 @ 11:31 PM EDT

Works for me.

Euan.

Server Information:
Operating System Linux
Kernel Version 2.4.20-13.8
Last Reboot 82days, 16:23min
Apache Version 1.3.28 (Unix)
Perl Version 5.008
PHP Version 4.3.2
MySQL Version 4.0.13

[ Reply to This | # ]

Authored by: Euan on Sunday, August 10 2003 @ 12:49 AM EDT

Just noticed: my gallery installation has become a little odd (gallery 1.3.4). When I view the gallery, I appear to be logged out - I have none of the admin permissions I used to have, and also appear to be logged out of geeklog. However, when I click out of the gallery, I am logged in.

Tried going through and manually entering the changes to the gallery files from scratch, but no luck: no admin permissions. Not sure if this is a problem of the Geeklog upgrade or Gallery (they released gallery 1.3.4-pl1 which I have upgraded to, but had the same problem with Gallery 1.3.4 and Geeklog 1.3.8-1).

Will post this in the forums too.

Euan.

[ Reply to This | # ]

Authored by: Makenai on Sunday, August 10 2003 @ 10:25 PM EDT

Hi, I just upgraded my version of a new test install.. upgrade seems to work ok, but I had trouble verifying one thing mentioned in the changelog:

- Words from a search query are now hightlighted in comments as well.

This still doesn't seem to work for me. I copied all of the files in the tarball to their correct location, honest. :)

Try the following link: http://www.pawelski.org/search.php?query=chump&type=all&mode=search

The word 'chump' should be highlighted in the comment that comes up according to the changelog entry. Or did I not understand it correctly?

[ Reply to This | # ]

Authored by: Dirk on Monday, August 11 2003 @ 03:41 AM EDT

That change description is a bit misleading. If a search word is found in a story and you go to that story from the search results page, then any search words that happen to appear in the comments will be highlighted as well.

If (as in your example) the search word only exists in a comment, then it's not highlighted since the link to the search result does not include the &query=searchword ...

Think of this as an incomplete feature. After all, we didn't promise any new features for this release ;-)

bye, Dirk

[ Reply to This | # ]

Authored by: mysitemain on Monday, August 11 2003 @ 01:55 AM EDT

I would like to upgrade from GeekLog v1.3.7sr2.

do I need to go to 1.3.8 first and then apply the patches or can I just download the 1.3.8-1 tarball and upgrade form there?

What plugins and versions are there known issues for on 1.3.8-1?

This info would be very helpful when posted with the file since I think most people want to know...

[ Reply to This | # ]

Authored by: Dirk on Monday, August 11 2003 @ 03:46 AM EDT

You can always upgrade from any old official version (that does not include Release Candidates) to the latest version by simply downloading the latest tarball and following the upgrade instructions.

So, yes, you can download the 1.3.8-1 tarball and upgrade from 1.3.7sr2 directly.

As usual, plugins that only use the Plugin API should continue to work just fine with this release.

Modifications to Geeklog's core files may need to be applied again - or they may stop working altogether. That's the risk you take when you modify core files ...

bye, Dirk

[ Reply to This | # ]

Authored by: mysitemain on Thursday, August 14 2003 @ 01:49 PM EDT

I have done some minor modifications to my current 1.3.7sr2 install and am concerned about just doing a straight upgrade on the existing domain, since our site is fairly busy.

I am wondering if the following scenario will work...

current install is on www.mydomain.com

I would like to run the upgrade from www2.mydomain.com which will upgrade the database but current users will still have the old interface on www host.

I do all my testing on www2 and make sure everything is working correctly.

I change www to point to the new version at www2 and clients automatically access the new version once I restart apache.

The process "theoretically" seems like it should work....

My main question is this: Is there an issue with upgrading the database to the current structure and still using the old 1.3.7sr2 release to access it until I have all my testing done?

Will there be issues if I am using both 1.3.7sr2 and 1.3.8-1 at the same time to access the same database provided the database has been upgraded to the 1.3.8-1 structure?

Thanks for any input....

[ Reply to This | # ]

Authored by: Dirk on Thursday, August 14 2003 @ 03:12 PM EDT

If you remove the two lines from sql/updates/mysql_1.3.7_to_1.3.8.php that drop the commentspeedlimit and submitspeedlimit tables then the 1.3.7 code should (and I stress "should" - no guarantees here) work on an updated (1.3.8) database (you can drop those tables later).

However, 1.3.8 is a major upgrade to the code base and I would really suggest taking the site down for the update. With proper preparation, an upgrade can be done with a downtime of 5-10 minutes.

bye, Dirk

[ Reply to This | # ]

Authored by: mysitemain on Wednesday, August 20 2003 @ 12:43 AM EDT

I don't know if I was all that clear... I want to upgrade to the full 1.3.8-1 but until I have it totally tested, I would like my users to continue to use the 1.3.7sr2 front end while I test the new 1.3.8-1 front end. I don't want to drop any tables on the new release.

Are there any tables or fields from 1.3.7sr2 that will be dropped in the upgrade process or are there just some new tables and/or new fields added into the existing 1.3.7sr2 tables?

[ Reply to This | # ]

Authored by: samstone on Thursday, August 21 2003 @ 12:35 AM EDT

1. About 8 feilds will be dropped, but they are quite useless anyway. The field for the users to enter IM, ICQ, etc. addresses. They are not actually dropped but will not be used.

2. Some fields are added.

Testing out in the background until it works, then switch it in a flash is how you should do with any active site. Please note that some thtml files are added to the layouts. (I am wondering where to find the added file list.) All the missing files, in you are useing 1.3.7 layouts, can be transferred from any 1.3.8 layouts. You don't have to create new ones. So each time the program tells me a file is missing, I just upload one from a set that comes with 1.3.8. So I can't tell you which ones are missing. But, you can always compare the directorys them side by side to find out.

Over all it works flawlessly. I just love 1.3.8!

[ Reply to This | # ]

Authored by: Anonymous on Wednesday, August 27 2003 @ 03:30 AM EDT

Thanks samstone.

Can you or anyone tell me which fields are not used anymore as well as which ones are added? According to Dirk's comments above, tables are actually dropped not ignored. Is there a complete changelog that explains the tables/fields in their entirety and what actually happens to them?

I have a billing package which is now fully integrated with GL and I want to make sure there are no conflicts. All signup/registration functions are handled by the billing software and the data is then exported to the GL database upon completion of registration.

This is why I have to do my testing as mentioned earlier.

[ Reply to This | # ]

Authored by: samstone on Thursday, August 21 2003 @ 12:54 AM EDT

Sorry, for not reading your message carefully.

Yes, as Dirk stated, you will be able to run 1.3.7 script on 1.3.8 database. You do need to shut down the site for a quick database structure upgrade.

Instead of using www2, I would use different directory name for GL and public_html, lets say, GL2, and public_html2.

Then, after testing out everything, you can suddently swich over to 1.3.8 by changing the directory names to the old ones and uploading the two newly edited files, config.php and lib-common.php. Becareful with the links in the layout header, though.

I am just telling you what I would do. But, for myself, my server was hacked last week and I had the luxury of rebilding all my sites with 1.3.8 using the mysql backup from the 1.3.7. It wasn't a smooth blue, but I love the new thing! GL have come so close to perfection. Can't imagine what 2.0 will be like.

Sam

[ Reply to This | # ]