Resources

Getting started

Support

Development

Topics

User Functions

Events

There are no upcoming events

What's New

Stories

1 new Stories in the last 2 weeks

Comments last 2 weeks

No new comments

Trackbacks last 2 weeks

No new trackback comments

Links last 2 weeks

No recent new links

NEW FILES last 14 days

No new files

Welcome to Geeklog Saturday, May 25 2013 @ 12:50 AM EDT

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

  • Geeklog security issues (and 1.3.7sr2 update)
  • Authored by:Dirk on Wednesday, May 28 2003 @ 05:12 PM EDT
There were database changes from 1.3.6 to 1.3.7 - or rather fixes for wrong values in some of the older versions.

There have always been database changes when the Geeklog version number changes (e.g. from 1.3.6 to 1.3.7, but not from 1.3.7 to 1.3.7sr1).

And 1.3.6 is not a "black sheep version" - not sure why you would think that.

bye, Dirk
  • Geeklog security issues (and 1.3.7sr2 update)
  • Authored by:Anonymous on Wednesday, May 28 2003 @ 05:52 PM EDT
My point is that my geeklog-1.3.7sr2/sql/updates directory has upgrade scripts for lots of versions but nothing for 1.3.6 to 1.3.7. If there are db changes, then shouldn't there be a script? Apparently not, since it says "the installation script" which I now see is different from an "sql update script" (as found in sql/updates) will do the changes for me. Which leaves me wondering why there isn't a php file for 1.3.6 to 1.3.7. Oh well, i'll try installing and see what happens. Thanks.
  • Geeklog security issues (and 1.3.7sr2 update)
  • Authored by:Dirk on Wednesday, May 28 2003 @ 06:27 PM EDT
Simple reason: The changes from 1.3.6 to 1.3.7 are hard-coded in the install script.

bye, Dirk