Upgrading from 1.7 to 1.8.0 - issues and solutions

[ivo.apostolov]

Dear users,
We noted some issues with the upgrade routines from 1.7 to 1.8.0 and we are currently working on solving them through a release of 1.8.1 maintenance version.

1. Upgrade is not done during the installation of 1.8.0, due to different prefix.
If your site uses prefix different thant jos_ the upgrade will not be successfull, due to a bug in the upgrade routine.
What you will need to do is to:
1. Unzip the file jf18_fix.zip attached to this post.
2. Upload the unzipped file to your root directory.
3. Run it once.
4. Delete the file.

This bug was discovered by hmueller and solved by Geraint Edwards. This one is already fixed in the upcomming release of 1.8.1

2. System bot, Content Searchbot and Language module are not updated during upgrade function.
This is caused by the fact that Joom!Fish 1.7 doesn't removes the files during the uninstallation. If you have used 1.7 and upgraded, but didn't removed manually these files before the installation of 1.8.0, they are not updated. Although, Joom!Fish will work and you might not notice any problems, you would not be able to use some of the new features of 1.8.0. Especially the parameters of the system bot and the language module are the same as in 1.7 and not like in 1.8, where there are additional features.

There are three possible solutions (do just one of them):
1. Uninstall and install Joom!Fish 1.8.0. The uninstallation routine of the extension will remove the files and after that it will upload the new one. It is a very simple operation and you will not experience any issues.
2. Replace the files manually. Take the files from the 1.8.0 package and replace the following:
mambots/search/jfcontent.searchbot.xml
mambots/search/jfcontent.searchbot.php
mambots/system/jfdatabase.systembot.php
mambots/system/jfdatabase.systembot.xml
modules/mod_jflanguageselection.css
modules/mod_jflanguageselection.php
modules/mod_jflanguageselection.xml
3. Inunistall the following bots and module only (not the whole Joom!Fish) and install them separately. Use the attached two bots and the module.
Uninstall the following bots and module:
- Multi lingual abstraction layer bot
- Multi lingual content searchbot
- JoomFish language selection

We appologize for the problems that these bugs might caused, but more or less there are determined by the fact that there were not a lot of users that tested the upgrade function in the Release Candidate. We will make our best to avoid such issues in future.

Regards,

[ladybug]

This bug was discovered by hmueller and solved by Geraint Edwards. This one is already fixed in the upcomming release of 1.8.1

Does that mean the release of 1.8.1 will be easier for upgrading from 1.7 to 1.8? Will this 1.8.1 release keep all the data that has already existed in v1.7? Because I want to make sure that the upgrading process won't loose any data before move on to the newer version. I am looking forward to the new release v1.8.1, currently I am using v1.7 and a little bit afraid of upgrading to v1.8.

Thank you so much, Joom!Fish Team, you did a wonderful job!!

[ivo.apostolov]

Upgrading will be fixed in 1.8.1, if you are running 1.7 with prefix jos_ there is no issue.
In whatever upgrade process we talk, no data is lost. Current issues are that break the usage of the fish, but the data is untouched.

[ladybug]

Upgrading will be fixed in 1.8.1, if you are running 1.7 with prefix jos_ there is no issue.
In whatever upgrade process we talk, no data is lost. Current issues are that break the usage of the fish, but the data is untouched.

Thank you for your reply!

You mean if I am running 1.7 with prefix jos_ tables in database, there will be no problem, right? So, that also means all I need to do is un-installing v1.7 first (backup before un-install, of course), then installing the new v1.8, that's all, right?

Just want to make sure before do any actions!! Thank you very much for your help!!

[kiwaki]

I tried the solution 2 (replaced manually the files), but I still have a problem with the following message "Overwriting global config value is currently disabled for this site. You must set this config value in the jfdatabase system mambot to enable it in the frontend"

[ivo.apostolov]

Thank you for your reply!

You mean if I am running 1.7 with prefix jos_ tables in database, there will be no problem, right? So, that also means all I need to do is un-installing v1.7 first (backup before un-install, of course), then installing the new v1.8, that's all, right?

Just want to make sure before do any actions!! Thank you very much for your help!!

This is exactly what I mean.

[ivo.apostolov]

I tried the solution 2 (replaced manually the files), but I still have a problem with the following message "Overwriting global config value is currently disabled for this site. You must set this config value in the jfdatabase system mambot to enable it in the frontend"

You need to enable that option from the system bot. This is not an issues, it is just OFF on default.

[kiwaki]

You need to enable that option from the system bot. This is not an issues, it is just OFF on default.

Thanks Ivo. So easy when you say it
It's working now. The only thing is that the message still appears, but it's working well.
Cheers

[ladybug]

Thank you for your reply!

You mean if I am running 1.7 with prefix jos_ tables in database, there will be no problem, right? So, that also means all I need to do is un-installing v1.7 first (backup before un-install, of course), then installing the new v1.8, that's all, right?

Just want to make sure before do any actions!! Thank you very much for your help!!

This is exactly what I mean.

Thank you so much for your answer!!!

[obibikenowan]

escuse me but I have much difficulties with english language.
I understood if my tables have jos_ prefix we have not problem.
My tables have not jos_prefix. What can I do ? To use the release 1.8.1. but after ? I delete the old files by the new files of the relases ? and I don't lost my existing traductions ?