Welcome to Geeklog, Anonymous Saturday, April 20 2024 @ 12:44 am EDT

Comments for Geeklog 1.3.8-1 bugfix release

Geeklog 1.3.8-1 bugfix release | 12 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Geeklog 1.3.8-1 bugfix release

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....

Geeklog 1.3.8-1 bugfix release

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

Geeklog 1.3.8-1 bugfix release

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?

Geeklog 1.3.8-1 bugfix release

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!

Geeklog 1.3.8-1 bugfix release

Authored by: Anonymous (Anonymous User) 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.

Geeklog 1.3.8-1 bugfix release

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

Warning: Javascript required to enable functionality

Post a Comment

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks