Distro Update Manager: version error on panopoly_wysiwyg

Blergh! Thanks for reporting this.

The downloads for distribution releases (like Panopoly) are built automatically by a packager script on Drupal.org - we just specify the versions in the drupal-org.make file (which we did correctly).

I've opened an issue with the Drupal.org infrastructure team:

#2455457: Packager incorrectly built Panopoly 1.19 (panopoly_wysiwyg at wrong version)

Hopefully, we'll get this resolved soon...

I believe I encountered this issue as well with a small twist. My upgrade path was as follows.

1. Updating from 1.18 to 1.19 did not include the 7.35 core update.
2. Manually updating to core 7.35 afterward resulted in the message:
   • Distro Update Manager: panopoly_wysiwyg version 7.x-1.18 does not match .make file version 7.x-1.19 from panopoly.

I'm reverting back to 1.18 for now.

Using the Panopoly 1.19 release with the incorrect version of panopoly_wysiwyg is perfectly safe!

You'll be missing a patch to fix a bug in the WYSIWYG module, but you didn't have this fix in 1.18 either, so if you didn't notice it then, you won't notice it now. :-) The only problem you'll probably notice will be the "unsupported version" message, which you can fix by manually updating panopoly_wysiwyg to version 1.19, if you'd like.

Unfortunately, according to the Drupal.org infrastructure team, the only way to correct the problem is to make a new Panopoly 1.20 release. :-/

We've decided to wait until Wednesday, March 25th to make the 1.20 release, so that we aren't inundating you guys with new releases. Assuming the packager script works correctly that time, all the correct versions will be included in the download for 1.20 and this problem will be solved!

Thanks for your patience and understanding!

I've got a couple of upgrades scheduled for this weekend. Can we just replace the one module after installing 1.19 and end up with what will be 1.20? Or are there other changes coming in 1.20?

@greggmarshall: Yes! Like I said above in #4, using Panopoly 1.19, even incorrectly built, is perfectly safe. And you can update panopoly_wysiwyg to version 1.19 to eliminated the "unsupported version" message.

However, Panopoly 1.20 will also contain some other minor, unrelated bug fixes, because we've already committed a couple of things since the 1.19 release. :-)

Same as eawheeler for me, updating from 1.18 to 1.19 did not include the 7.35 core update.
Will try updating from 1.18 to 1.20 when it's released.

@Farliec: Did you update Panopoly following the Upgrading Panopoly guide?

While there is the issue with Panopoly 1.19 having the wrong version of panopoly_wysiwyg in the download built on Drupal.org, it DOES have Drupal 7.35! So, this isn't something that will be fixed by Panopoly 1.20.

Made the 1.20 release! The versions of the modules all look good this time. :-) Closing!

Hi Panopolistas,

Just re-opening this one as it is such a good match with my problem.
Updated from 7.25 to 7.27 today and got these two :

(Image Resize Filter 7.15 > 7.16)

Distro Update Manager: image_resize_filter version 7.x-1.15 does not match .make file version Unknown from panopoly_wysiwyg.
Includes: Image resize filter

(Linkit 7.x-3.3 > 7.x-3.4)

Distro Update Manager: linkit version 7.x-3.3 does not match .make file version Unknown from panopoly_wysiwyg.
Includes: Linkit

These modules have never been manually modified and they only exist within the Panopoly profiles directory. So... I'm a little surprised to not find this exact issue in the queue as I would have thought others had encountered it much before now.

I'm guessing it's a personal problem...but no idea how to fix it up or why it happened.
Any clues much appreciated!

Kind regards,
JB

I just did a fresh install of Panopoly 1.27 on Pantheon and didn't see this problem. I also downloaded the .tar.gz from the Panopoly project page and verified that it included the correct versions, so even if the problem does exist, it isn't caused by the Drupal.org packager like this was last time.

I suspect something went wrong with your upgrade. Did you follow the instructions in the "Updating Panopoly" guide?

https://www.drupal.org/node/2272177

Or, is it possible that you have other copies of those modules in your sites/all/modules or sites/SITENAME/modules directories?

(FYI, it would have been better to create a new issue than re-open a closed one. If you have the time, it'd still be great to move this to a new issue! Otherwise, I'm going to have to remember to reset the fields on this one back to their original values when we're done solving your problem... Thanks!)

Heya Dave, Sosorry to cause you extra work! I'm never quite sure which protocl to follow when chasing a closely-related issue.
Re-closing this one now and I'll start a new one.
FYI, I'm doing a raft of updates now. Last night I did several nearly identical updates and had no issue. Just now, I ran into the same problem.
Again, these are differetn sites/servers and there are no polluting duplicate modules.
Closing now...will pick it up on new thread and reference this one.
As always, thanks heaps for your assistance and commitment to an excellent package!