Mission Control Bug - 2.5 Update
-
-
- RJ Jacob
- Jr. Rocketeer
- Posts: 21
- Thanks: 0
- Definitely worked for me! Just an observation: I had already updated to 2.4 (several times...ha) however, even after the plugin was installed, the updater still showed 2.4 in the queue. I purged and tried "find updates" again and it showed up still. I cleared my browser cache and still it appeared. I backed up my site and then went ahead and updated. All went smoothly and still no more dupes. So I guess it worked like a charm, but I'm not sure if it should've happened that way or not.
-
-
-
- Ben Sandberg
- Sr. Rocketeer
- Posts: 117
- Thanks: 3
-
Andy Miller wrote:
there's no version number stored in the #__extensions tablepolite disagree;
the field "manifest_cache" has a JSON object of the XML manifest, created at the time of install, no?
My DB (from the test) has this value currently;
{"legacy":false,"name":"rt_missioncontrol","type":"template","creationDate":"February 3, 2012","author":"RocketTheme, LLC","copyright":"(C) 2005 - 2012 RocketTheme, LLC. All rights reserved.","authorEmail":"support@rockettheme.com","authorUrl":"http:\/\/www.rockettheme.com","version":"2.3","description":"MC_TEMPLATE_DESC","group":""}
But as RJ Jacob pointed out, all one has to do is update, and it's fixed. (meaning, no-big-deal)
-
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
-
That's true, but I see no reference of that by the updater. I'll dig into it a bit deeper though.
Update, it does appear to be used somehow, not sure how best to handle it as its embedded in that field. I can't sort or order based on it.
-
-
-
- Ben Sandberg
- Sr. Rocketeer
- Posts: 117
- Thanks: 3
-
Thanks for digging. You've gone *way* above&beyond to help with this issue.
It'll be fine, until the JBS releases the fix.
Thank you!!
-
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
- I think if i order the entries in the #__extensions table by extension_id desc. That way it should ensure that the latest rows, ie the latest versions are retained.
-
-
-
- Ben Sandberg
- Sr. Rocketeer
- Posts: 117
- Thanks: 3
- that makes sense. Let me know if you'd like another test.
-
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
- if you want to try this snapshot, let me know if it works better. Of course, you'll have to uninstall the previous version to get the old broken file back and recreate you setup you had.
-
-
-
- Ben Sandberg
- Sr. Rocketeer
- Posts: 117
- Thanks: 3
-
Same outward appearance; The Template/Style manager reports as v2.3, as does the J! Ext-Update Manager.
Upon further tests, *without* the plugin-fix installed, I've observed that the #_extensions table only has one element=rt_missioncontrol record. (with old data)
frustrating...
IMO, I think that anyone installing this plugin should simply install the latest MC version immediately afterward. That'll solve all this weirdness.
I'm happy to provide further detail -- let me know what I can tell you, or access I can provide.
-
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
- Apologies, seems the change didn't make it into that last snapshot. This one has it though
-
-
-
- Ben Sandberg
- Sr. Rocketeer
- Posts: 117
- Thanks: 3
-
YAHOO!!
That worked, no problems to note.
I am curious, tho -- how will this affect future versions of Joomla!?
Say that in some later minor 2.5 release, further changes are made to the files altered by this plugin -- how will the plugin perform?
Or will it need to be removed?
Just curious, as I'd like to deploy this on over 25 sites, but would like to be sure about forward-compatibility.
Thanks, Andy!
-
Time to create page: 0.064 seconds