1.0.6 -> 1.1 upgrade problem

[qzy]

Hi there,


I'm trying to upgrade a production site from 1.0.6 to 1.1, but with no success. After unpacking 1.1 and starting upgrade.php I see this message in the browser:

In order to upgrade properly, upgrade needs to have write access to your config.php file. This is so any extra settings that have been introduced in this version can be set to their defaults.

Upgrading config.php...[done]

Cleaning cache dirs...[done]

Upgrading Search module from 1.1 to 1.3...

So as can be seen, Search module upgrade never gets done, and the upgrade process stops at this point.
No error messages, neither in the browser nor in the apache error_log. The site is down...and I'm in trouble.

Any suggestion would be great.

Thanks,
Balint

[tsw]

can you login to backend?

if yes, try to upgrade search there

if not you could move search out from module folder for a while and do the site upgrade and then move search back...

and if nothing else works restore from the backup you took before the upgrade (you did follow the upgrade process step 1. take a backup, right?)

[qzy]

Thanks, in the meantime I've done that. Removing Search module solves the upgrade issue. However after the successful upgrade, Search 1.3 does not install (which means that clicking to the "Install" button of Search in the module list causes the system to wait until the browser times out, while module status remains "not installed").
Though I'd need the functionality of Search module.
Any idea what to do? Instead of reverting back to 1.0.6....and yes, I've got all backed up. 

Balint

PS: Polls module also died of the upgrade.

[tsw]

polls module might not be upgraded to support 1.1

its hard to say what search is doing without any error..

I would start by writing die("here") stuff in method.install.php and see where its dying...

[qzy]

Well, polls is OK after some tries.

With Search I really needed to hack a bit: inserted a row to the modules table describing that Search 1.3 is installed. Since then searching is OK too, all I had to do is reindex the whole site content.


Balint

[lizziv]

I'm having a similar problem upgrading from 1.0.2 to 1.1, the upgrade runs until it times out at the Search module. I was able to do the upgrade by uninstalling the Search module and removing the modules/Search folder as suggested, however I'm not able to get the Search module working again after upgrading. I've left it disabled/uninstalled for now but would like to get it working again. Any ideas?

[qzy]

After I couldn't make Search work form the Module Manager either, I found this dirty workaround:
I copied the Search module to its place from the cmsms 1.1 install archive then inserted a row to the modules table, with something like this:

Code: Select all

insert into modules values ('Search', 'installed', '1.3', '0', '1');

Balint

[lizziv]

I've replaced the search module files, and inserted the record, then activated the module. When I reindex all content I get a 500 error. The {search} tag doesn't display the search box as it should.

Thank you,
V

[qzy]

Though I haven't come across something like that, I'd suggest recreating the modules_search_* tables (module_search_index, module_search_items, module_search_items_seq) from scratch.

Balint

[ITistic]

Is there a better solution to this problem yet? I am trying to upgrade from 1.0.2 to 1.1.3.1 and am having the same exact problem. I haven't tried the manual workarounds yet and instead just reverted to the backup. Is this going to be fixed so there is a clean upgrade path from 1.0.2 -> 1.1.3.1?

[qzy]

Hi,

I haven't found a better way than that. It worked once, and having my production sites upgraded this way was enough for me...


Balint