Updating to V 1.20 from 1.18 in Pantheon [#2472529]

keep getting error message when I update from 1.18 on Pantheon site. It wants to make 4 updates thru 1.19, the 1.19 fix and 1.20. Site won't open after each attempt

Parse error: syntax error, unexpected $end in /srv/bindings/7a64ac833d2a4c5492c625db133617e0/code/profiles/panopoly/modules/contrib/jquery_update/jquery_update.module on line 478

Comment	File	Size	Author
	Screen Shot 2015-04-16 at 8.35.54 AM.png	118.33 KB	frogrock

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

frogrock CreditAttribution: frogrock commented 16 April 2015 at 15:51

Issue summary:

View changes

Comment #2

dsnopek

he/him

English

USA

CreditAttribution: dsnopek commented 24 April 2015 at 12:46

Status:

Active

» Postponed (maintainer needs more info)

Can you share the content of the jquery_update.module file at profiles/panopoly/modules/contrib/jquery_update/jquery_update.module after the update attempt?

It seems like there is a syntax error in that file on your site.

Maybe a merge conflict? Did you change that file sometime before doing the upgrade, such that the changes the upgrade is trying to make are conflicting with the changes that you made?

Anyway, I just tried installing a fresh Panopoly 1.20 site on Pantheon and everything worked fine, so there is no syntax error in that file in the upstream repo...

Comment #3

frogrock CreditAttribution: frogrock commented 6 May 2015 at 18:02

thanks for response, yes, the same error occurred again trying to use 1.21. I didn't change anything. I did tell the update to resolve conflicts. Was that a mistake??? 7.1.0 is many years old. Is there a place to get the specific 7.1.7? I presume I need to dump the existing file and replace it with a new version of 7.1.7 or whatever.

Comment #4

frogrock CreditAttribution: frogrock commented 6 May 2015 at 18:30

ok realize that was a dumb ? can select verson in the module config, so am trying to reset to hopefully clean version of jq 1.7

Comment #5

dsnopek

he/him

English

USA

CreditAttribution: dsnopek commented 6 May 2015 at 19:00

The error in the issue summary is fatal error with parsing the PHP code in profiles/panopoly/modules/contrib/jquery_update/jquery_update.module, so this isn't an issue with configuration - it's a problem in the code in that file.

Can you do the upgrade then copy the contents of that file and share them here? Ideally, put it on a snippet service like https://gist.github.com/ or http://pastebin.com/ and include the link in a comment here.

Like I said in #2, there isn't a problem parsing that file in vanilla Panopoly, so it's some issue with that file specifically on your site after the upgrade.

Comment #6

frogrock CreditAttribution: frogrock commented 6 May 2015 at 19:02

so, have dumped jquery from profile/contrib folder and redownloaded and reinstalled jq2.5 and selected 1.7 in regular and admin modes and told pantheon not to resolve conflicts and get basically the same message when I try to upgrade what is now 6 updated versions of Panopoly. here message:

A conflict occurred attempting to merge upstream updates. The conflicts are:

CONFLICT (content): Merge conflict in profiles/panopoly/modules/contrib/jquery_update/jquery_update.module

Should I be selecting a different version of jq update?

Comment #7

dsnopek

he/him

English

USA

CreditAttribution: dsnopek commented 6 May 2015 at 20:01

Status:

Postponed (maintainer needs more info)

» Active

Try telling Pantheon to resolve conflicts. It sounds like you updated the jquery_update version at some point, so the updates that we made to it in vanilla Panopoly are conflicting. After the update, you can put the version of jquery_update you want to use under sites/all/modules (instead of profiles/panopoly/modules) and then you shouldn't get these conflicts in the future.

Comment #8

frogrock CreditAttribution: frogrock commented 6 May 2015 at 23:49

thanks. I must have as you said. I moved jquery over to sites/all/modules and it now works like a dream with 1.21 now installed!!!! should I still be using jq1.7 ???