Upgrade of core from 5.4.1.1 to 5.4.2 throws latest DIG 1.6.1 back to stone henge (1.0.3)
Permalink Browser Info Environment
Well, maybe not exactly as the title suggests, but almost... I upgraded my core to 5.4.2 from 5.4.1.1 and now the dashboard tells me to update Deluxe Image Gallery from 1.0.3 to the latest 1.6.1. The strange thing is I did exactly that just two weeks ago, and when looking at my current changelog in packages/deluxe_image_gallery it suggests I do have 1.6.1 installed.
So has anyone else stumbled upon this problem or have a solution?
For what it's worth I'm on a centralized installation, but it shouldn't change anything.
So has anyone else stumbled upon this problem or have a solution?
For what it's worth I'm on a centralized installation, but it shouldn't change anything.
| Type: | Discussion |
|---|---|
| Status: | New |
Is the Deluxe Image Gallery part of the centralized installation or just in the one specific site? Also, in addition to checking the changelog, also look in the controller.php file (just next to the changelog file in the top level of the D.I.G. package directory) -- does it also say 1.6.1 for the version there?
DIG is a part of this one particular site and not in the core part of the centralization.
And yes, the controller.php file also says it's version 1.6.1
Any ideas as to why this is?
Do you think I could break something if I release it from my project and then connect it again (since I have done some modifications to the code and the db.xml)? And also, would it help??
And yes, the controller.php file also says it's version 1.6.1
class DeluxeImageGalleryPackage extends Package { protected $pkgHandle = 'deluxe_image_gallery'; protected $appVersionRequired = '5.3.0'; protected $pkgVersion = '1.6.1';
Any ideas as to why this is?
Do you think I could break something if I release it from my project and then connect it again (since I have done some modifications to the code and the db.xml)? And also, would it help??
FYI: Upgrade to 5.4.2.1 did not solve the problem either.
What if I manually update the packages table in the db to say 1.6.1 is installed? Would that solve the problem or is it just an ugly workaround since I can't find the real problem?
Edit: A refresh of the installed package didn't solve it either.
Edit: A refresh of the installed package didn't solve it either.
Ah well...
I checked the db and pkgVersion is only used in table packages so I changed the value to 1.6.1 which sort of solved my problem.
Now I just wonder how this could happen in the first place, since everything was working as expected.
I checked the db and pkgVersion is only used in table packages so I changed the value to 1.6.1 which sort of solved my problem.
UPDATE `concrete5`.`packages` SET `pkgVersion`='1.6.1' WHERE `pkgID`='12';
Now I just wonder how this could happen in the first place, since everything was working as expected.
Hi,
I have no idea how this could have happened -- sorry I wasn't able to help you. Glad you figured it out though.
-Jordan
I have no idea how this could have happened -- sorry I wasn't able to help you. Glad you figured it out though.
-Jordan