I'm trying to upgrade a module, and I've put it in coder_upgrade's 'old' directory, and checked it under the 'upgrade' tab and hit 'convert files'.

I get a white screen with this text: Fatal error: Cannot use object of type PGPOperand as array in [...]/sites/all/modules/pgp/engine/pgp.editor.inc on line 160

I have tried to add casting and more if conditions to prevent this, but it just creates a similar error further along.

I'm not sure if this is pgp's problem or coder's, but I'll leave this with you to consider.

Comments

danielb’s picture

danielb commented

More info, I'm trying to upgrade node export from 6.x (from CVS) to 7.x

solotandem’s picture

solotandem commented
Assigned: Unassigned » solotandem
Category: support » bug

Yes, it belongs here. Thanks for finding this.

karens’s picture

karens commented

I ran into this when upgrading Date. Unfortunately I don't have any idea how to fix it.

solotandem’s picture

solotandem commented

Both of you, please download the latest code for both Coder Upgrade and Grammar Parser. Try the upgrade again. Let me know if it is still an issue.

karens’s picture

karens commented

I got this message when upgrading date with the beta2 version of coder, I never got this far using the dev version of coder due to a bunch of fatal errors, some of which I reported on the coder issue queue. I tried using the latest version of pgp with the beta2 version of coder and still get the above error, but I'm sure that's because you made changes on coder that are not getting picked up.

I'm going back to the latest dev version of coder and trying to work through the rest of the fatal errors so I can try to get the dev version of coder working to see if I still have this problem.

karens’s picture

karens commented

I finally got the rest of my fatal errors worked out and posted some patches and issues on the coder issue queue. With the latest code and those coder fixes I am no longer getting this error, so as far as I can see it is fixed.

Thanks!

solotandem’s picture

solotandem commented
Status: Active » Fixed

Marking as fixed based on Karen's response.

Status: Fixed » Closed (fixed)

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