install / upgr... > Bug (closed)

Upgrading db issue from 0.07991 to 0.0801 / #5952

MoveBookmark

Summary

closed
Sep 20, 2007
100%
Sep 20, 2007 / spacecake
Nov 28, 2007 / spacecake
View previous 8 versions
spacecake, pixtur
 

Attached files

No files uploaded
This is my first upgrade, I read the upgrade instruction but got stuck. I made backups of files and of the streber DB.

After copying files like in the upgrade manual and going to the page:

Problem: the version of current database (0.07991)does not match the current version of streber (0.0801)
try upgrading

I click on the installation/upgrade link, old settings are all in place, I just put the admin password in the field, and click to go.

The next page is something like this:

Proceeding...
checking mysql connecting to 'localhost'...
GOOD
Connection using mysql_connect SUCCESSFUL

Make sure to not overwrite existing streber-db called 'db_name'
POTENTIAL PROBLEM
DB 'db_name' already exists

checking version of existing database
FAILED
could not get propper db-version table entry. Please view Installation Guide on hints how to proceed.

Installation failed

Can anybody help ?

I tried Potential Upgrade Fix and I can´t upgrade to the last version, no result. Good thing that I made db backup :P

7 Comments

eh

Sep 26, 2007
Get the same error
Porting a streber installation from one system to another one works fine - as long as the same streber version is used. But migration from, as is in my case, version 0.0796 to version 0.0801 fails with the same error as described above. I mean there must be a database... with all my data that should be preserved.

For me this issue is somehow related to Provide empty database for installation.

spacecake

Sep 29, 2007
Reply to Get the same error
I see, you have an even older version of the DB :(

This particular error made me re-think of using this utility further. If I cant upgrade, and my work/business relays on it, and problems still occur, sorry but product is no good.

This error (yes I call it an error, not a bug), was posted 8 days ago, and not even a hint from devs. For now I am considering and testing DotProject for future, will see...

rgrds,
Space

guest

Sep 26, 2007
same error
...

eh

Sep 29, 2007
Reply to "Reply to Get the same error"
Hi spacecake

Even streber is not perfect in some situations (as other sofware isn't too) I'm very happy with it - using it daily in a team of 4 to 5 people for internal SW project management and as a ticketing system.

Not getting a response in within one to two weeks in an open source project should be acceptable. My experience with certain commercial software is even worse...

Some months ago I also made a post here and got feedback the same day - so it all depends of availability of the developers and probably how they feel at the moment.

I also evaluated DotProject a year ago but decided to use streber. Can't remember in detail what the reason was, but for sure streber's very intuitive and modern user interface and its focus on what it aims to be - a slim PM system for projects of average size - had strong influence on my decision which I don't regret.





spacecake

Oct 5, 2007
version 2
Update
Did anybody managed to fix this issue with upgrade procedures ?

or I will need to clean the DB and make a new install ?

.. and need to hire a small 7y old boy from China/Malaysia pay him 2 cents/hour to manually port from old to the new Streber installation all the items ? ..

guest

Oct 5, 2007
To fix this, please edit database table {prefix}_db manually
To fix this issue please leave only one row in {table prefix}_db table in your database and run upgrade process again.
I had same problem because I had two rows in this table. After I have deleted one upgraded process completed successfully.

spacecake

Nov 28, 2007
Upgrade successful
With deleting this extra row, the procedure went like a charm.

altrough after upgradind, there was a "%% strip slashes" issue, which I solved:
 
 

Comment / Update