We need to verify that the upgrade process from 7.x-2.x to 7.x-3.x works correctly, or at least identify the problems so they can be fixed.

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

One bug has been reported already: #2124517: Custom displays Default out after upgrading from 2.x to 3.x

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Verify upgrade process from 7.x-2.x to 7.x-3.x works » META: Verify upgrade process from 7.x-2.x to 7.x-3.x works
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Version: 7.x-2.x-dev » 7.x-3.x-dev
PeterStub’s picture

PeterStub commented

I can confirm that after an upgrade from 2->3 - exported through features - none of our defaults were available. I can see them in my list of features - and they need to be reverted - but I cant. The checkbox is there and it says Reverted - but its not.

Just tried a clean installation with version 2. Created some defaults with different layout/content. Did a feature export. Then installed a new site with version 3. Added my feature and enabled it. Nothing - empty dropdown when creating new article. Disabled feature and then a default showed up.

Is there anything I can try/do?

Tks

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: #2155813: Plan for Panelizer 7.x-3.2 release » #2413267: Plan for Panelizer 7.x-3.3 release

Bumping this to v3.3.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: #2413267: Plan for Panelizer 7.x-3.3 release »

Pulling off the release schedule, not sure when this will be completed.

helmo’s picture

helmo commented

When running the db update hooks in an upgrade from 2.0 to 3.4 I get:

Executing panelizer_update_7104	
Performed update: panelizer_update_7104	
Executing panelizer_update_7105
SQLSTATE[01000]: Warning: 1265 Data truncated for column 'view_mode' at row 1	
Performed update: panelizer_update_7105

Aegir thoughtfully rolled back to let me try again.
I then did it manually and when starting the update process a second time with the two db_add_field() calls from 7105 commented out I managed to let it continue.

And later on:

Performed update: panelizer_update_7121                                                                                                                                                                                                                                         [ok]
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) AND (entity_type = 'node')' at line 1                                         [error]
Performed update: panelizer_update_7300

This looks like #2790289: Update 7300 Fails due to Error 1064 for which I was able to create a patch #2790289-3: Update 7300 Fails due to Error 1064.

azinck’s picture

azinck commented

I get exactly the issues as helmo when updating from 2.0 to 3.4.

I took out an issue to fix the problem with 7105: #2796175: Database warning when executing panelizer_update_7105()

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

I'm going to work on this within the next few days, apologies for the delay.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Please test the patch I added to #2124517: Custom displays Default out after upgrading from 2.x to 3.x and let me know if that solves the problems when upgrading from 7.x-2.x.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Fixed

@helmo: The view_mode field is set to VARCHAR(128), do you have an entity with a view mode name that is longer than 128 characters?

The main entity configuration variable is fixed, if anything else is wrong then please open a new issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.