Data Conversion Issue

[barry1947]

Hi There Team,
I have an issue that I have a problem understanding. It is probably something that I have done.
I have a working version of 2.1.4 which I have changed the style and made mods to the style.
I had a running version of 2.0.19 and ran an upgrade to 2.1.4 which seemed to go great and it seems to run in native format. So my plan was to export the data via phpmyadmin and reimport into my dev version of 2.1.4. Following the data import it reported a problem in load.php. so I felt that I needed to run repair_settings.php because the paths had changed. sadly running repair_settings.php resulted in the following error messages. For security I have removed the actual paths and anonymised them. This is the error. Hopefully if I can resolve this and change the paths the rest of the system will fall into line.
Fatal error: Uncaught TypeError: strrpos(): Argument #1 ($haystack) must be of type string, array given in PathRemoved/repair_settings.php:941 Stack trace: #0 PathRemoved/repair_settings.php(941): strrpos() #1 PathRemoved/repair_settings.php(794): guess_attachments_directories() #2 PathRemoved/repair_settings.php(251): show_settings() #3 {main} thrown in PathRemoved/repair_settings.php on line 941
As usual I will appreciate and help.
Best regards,
Barry.

[Kindred]

You can not import a 2.0.x database into a 2.1.x installation.

There are a LARGE number of conversions done to the database by the upgrader

Repair_settings will actually  BREAK things if you run it before on the wrong version database.

You need to either upgrade in place
Or
Create a duplicate 2.0.x install, import the database and run repair_settings.php and THEN upgrade

After the upgrade,  you can copy the THEME edits that you made into the upgraded site.

[barry1947]

Hi Kindred,
Many thanks for your reply once again.
I WAS going through the upgrader first, but I think on the first occasion that I did not run the repair script. When I redid everthing and paid more attention to my steps that I needed i.e. run the repair script at the correct time, it was much better but I still ran into a different problem when the themes template could not be loaded. So I thought about that and went back to the orignal converted upgrade files that were still running fine on 2.1.4 but not on the Theme that I had done some work on. So I installed the theme on that system as well and then exported the database and imported it back into the target 2.1.4 that I have been working on. I ran the repair script to change the paths once again and lo and behold the template was found and loaded up without a hitch. so it does seem that there may be a problem following the upgrade and porting to a new target that the system cannot cope with the theme not existing, so instead of reverting to the default theme it throws an error. Of course I could be dumb enough to be wrong.
 
Everything seems fine now and I will probably need to go through this protracted data conversion a few more times before I go live. I have a bunch of expectant users
Best regards and many thanks for coming back to me once again and I hope that things are great in New England. The closest that I have got so far is the southern extent of Lake Champlain out of Vermont after driving from from Southern Virginia with a detour into Canada first lol.
Barry.

[Kindred]

Well yes...   if you copy a forum over,  it needs to have the same configuration as the original.  Themes and mods can be added, changed or removed after the move/copy is completed and confirmed.

(Files and database need to match)

You can always set up the default forum install,  do the upgrade and then add your custom theme afterwards