1. Home
  2. Community
  3. Installation and Upgrade
  4. Bonked upgrade from 2.06 to 2.1.0

This website can use cookies to improve the user experience

This website can use cookies to improve the user experience and to provide certain services and functions to users. Cookies contain small amounts of information (such as login information and user preferences) and will be stored on your device.

Enable All Cookies Privacy Policy

Bonked upgrade from 2.06 to 2.1.0

Installation and Upgrade 27 This topic was started by ,


avatar
rasp1 64
From: -
Bonked upgrade from 2.06 to 2.1.0

I'm not sure why this is happening, but I'm assuming that this is going to happen every time I upgrade the CMS. Could you please fix this? It is getting rather annoying.

Jason
Bonked_upgrade_part_2

Notice

This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic

1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
The sites 5, 6, and 7?

Then run the following 3 queries in phpMyAdmin:
DELETE FROM esselbach_ct_preferences WHERE preference_website = '5';

DELETE FROM esselbach_ct_preferences WHERE preference_website = '6';

DELETE FROM esselbach_ct_preferences WHERE preference_website = '7';
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
Here is the screen shot. They have been growing since the last two updates from 2.06-2.07 and 2.07-2.1.0. So the last two updates have bonked the site,and added these extra sites.
Extra_sites
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
Is there any way to delete the three other three 'contentteller' websites from my install? I don't see a way to do it in the manage websites tab/menu.

Can you post a screenshot from manage websites?

Also, is it safe for me to upgrade to 2.1.1?

It works fine here but I don't know if it fails again on your configuration. I migrate the machine in my office later next week to an Intel Mac, so I can do some additional testing with VMware Fusion.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
Is there any way to delete the three other three 'contentteller' websites from my install? I don't see a way to do it in the manage websites tab/menu.
Also, is it safe for me to upgrade to 2.1.1?
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
I don't know how, but I did send the information to your support@ address.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
You could open a trouble ticket. Please include FTP and phpMyAdmin login.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
It looks like the latest back up is bad/corrupted. What are my options? I don't want to lose a weeks worth of content.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
Yes, this is possibly the best until the problem has been worked out. You never should upgrade a live installation to a major release without testing it first.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
what do I do? restore from backup?
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
No, this makes no difference.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
It seems to be correct.
Could this have been caused by the 2.x being installed in the same database as 1.x?
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
Can you check the settings (website url etc.) of the websites?
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
Better, but now it is showing every site with the same content as the anavrin site. But the manage websites seems to be working properly, but with extra entries.
Bonked_upgrade_part_2_1
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
I see, there is no website with ID #1. Try adjusting the script to ID #4

Replace the following line:
$query = $database -> dbquery("SELECT preference_key FROM " . DB_PREFIX . "esselbach_ct_preferences WHERE preference_website = '1'");


with:
$query = $database -> dbquery("SELECT preference_key FROM " . DB_PREFIX . "esselbach_ct_preferences WHERE preference_website = '4'");


Let me know if this fix the problem.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
OP 64
From: -
The script didn't work.
1 Re: Bonked upgrade from 2.06 to 2.1.0
avatar
Editor
0
From: -
I will look into it. In the meantime run the fixwebsites script from the other thread to fix the database.

Notice

This topic is archived. New comments cannot be posted and votes cannot be cast.