(Not yet checked for trunk)
After running installer with upgrade we get the message "Invalid database run installer..."
Running installer don't changes anything to database, but the message is still displayed.
It is a consistency "deadlock by soft".
The lonely thing generated by installer is a reset which needs to reset manually the admin account and clear all caches and cookies (see #4066 admin login problem).
!!!Going on 12/06/2011
I need to check the soft.
The message is sent by "installer" $installer instance of class installer in installib
It checks before the validation of patches on db using $installer->recordPatch($patch) for each one.
recordPatch function in installer records the patch into tiki_schema as done with his full date.
The concerned (got by a var_dump) patch is "20110904_shoutbox_def_tweetid_tiki"
is not into the tiki_schema table.
So the test functions, but the tiki-install failed to make this patch on another version OK, as it is defined.
__When it runs now (installer at 8.1 level) it don't tries to make the upgrade. This is the deadlock.
What is done if an old patch is not there !!!
More there is no report at all.__
? I began to look at, but I don't know this part of the soft.
!!!Going on 12/06/2011
In my opinion, there is no solution with a good reliability while :
run a comparison to find which version is really installed
When last functions is unable to treat all patches, the database needs to be treated by somebody who knows exactly what he is doing, the upgrade can be complex.
The whole problem is that it is impossible to be sure that an old patch as been well done without the treatment that I describe here. This process give the necessary security and reliability.
It needs work but it is not terrible.
The particular case treatment :
In my case it have been simple. The level of tiki_shoutbox was 4.1 but as empty I have replaced it with the last version. The installer in 8.1 could not run 20110904_shoutbox_def_tweetid_tiki2010 because 2010_better_column_fix_tiki.php had not run for unknown reason in his time (the other update of the same patch had been done normally before... nothing to explain).
We cannot, we must'nt risk bugs for this problem
!!!Going on 12/06/2011
Know everything above.
Show.tiki.org snapshot creation is in progress... Please monitor http:///snapshots/ for progress. Note that if you get a popup asking for a username/password, please just enter "show" and "show".
Password reset was successful
Password reset failed
Show.tiki.org instance destruction is in progress... Please wait...
The public/private keys configured to connect to show2.tiki.org were not accepted. Please make sure you are using RSA keys. Thanks.
Unable to connect to show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is currently under maintenance. Sorry for the inconvenience.
Unable to get information from show2.tiki.org. Please let us know of the problem so that we can do something about it. Thanks.
Show.tiki.org is in the progress of creating the new instance. Please continue waiting for a minute or two. If this continues on for more than 10 minutes, please let us know of the problem so that we can do something about it. Thanks.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
The URL for the show2.tiki.org instance that demonstrates this bug is at: http://. Note that if you get a popup asking for a username/password, please just enter "show" and "show". This is different from the initial login and password for a new Tiki which is "admin" and "admin".
For the install log, see http:///info.txt
Note that if you see PHP errors or a Tiki claiming to be missing third party software, the instance creation is probably not finished. Please wait a couple minutes and reload.
Snapshots are database dumps of the configuration that developers can download for debugging. Once you have reproduced your bug on the show2.tiki.org instance, create a snapshot that can then be downloaded by developers for further investigation.
Snapshots can be accessed at: http:///snapshots/. Note that if you get a popup asking for a username/password, please just enter "show" and "show".Create new snapshot