We've updated the two or three items we're using from the Rebranding plugin, but the WPMU update panel shows us as still being on 1.0.3 ... which means we still have the red update message at the top our admin pages .... we don't want to have to turn off admin notices but want to get rid of the alert .... any ideas on how to tell the update plugin that we are on 1.0.4 of the rebranding plugin?
We've updated the two or three items we're using from the Rebranding plugin, but the WPMU update panel shows us as still being on 1.0.3 ... which means we still have the red update message at the top our admin pages .... we don't want to have to turn off admin notices but want to get rid of the alert .... any ideas on how to tell the update plugin that we are on 1.0.4 of the rebranding plugin?
6593 pointsLike some sort of WPMU DEV GodExceptionally helpfulLifetime member
Keeper of the Dark Chocolate
—
18th November 2010 (1 year ago)
#
There's a couple of threads on this. Last time this happened, I forget if either the version on the local install installs wasn;t updated or the version wasn;t changed on their end. Make sure that the version number within the plugin file matches what's listed on the site here. edit: Date too.
And insert my standard disclaimer about the evils of auto updating.
10635 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Sales & Support Lead
—
18th November 2010 (1 year ago)
#
Hiya Tracy,
We've just been working on the Update Notifications plugin on our end so we may have a thing or two still to update. I'll let the developers know what's happening and see if we can't get it sorted though.
Changed remove permalinks to 1.0.5 and nothing happened, changing Login Image to 1.0.5 did remove the warning... if permalinks is moved back to what I had at 1.0.3 there is no warning, so it appears the warnings aren't consistent for the different plugin components in rebranding pack.
Also, all plugins I've downloaded have version of 1.0.3 of Update Notifications, which is out of date... may be a good idea to not include the update notifications in each individual plugin so that it doesn't have to be updated in EVERY plugin once it changes versions.... maybe a text file note about it and where to find it would decrease work in upgrading each and every plugin when it changes version while still making people aware of it.... just a thought.
Only the plugin with WDP ID: set to a valid ID will affect the update notification. I guess I forgot to mention which file to change the version number in. Anyway this shouldn't happen anymore as the Update Notification server was fixed only recently and that's what revealed this issue. We are sorry for the inconvenience caused..
I had to bring up a old topic but I am receiving notifications from that the re-branding-wordpress-mu plug-in needs to be updated, when I download the update and install the plug-in, I still receive notification that the plug-in needs to be updated.
I viewed the php file and the version said, 1.0.2.
10635 pointsLike some sort of WPMU DEV GodMindblowingly helpful memberLifetime member
Sales & Support Lead
—
6th February 2011 (1 year ago)
#
Hiya guys,
Yeah, the rebranding pack is causing some issues with the individual plugin updates. We plan to offer them individually to keep this from happening. We're working on it at the moment and should have this resolved next week. Sorry for the trouble.
Responses (8)
Keeper of the Dark Chocolate — 18th November 2010 (1 year ago) #
There's a couple of threads on this. Last time this happened, I forget if either the version on the local install installs wasn;t updated or the version wasn;t changed on their end. Make sure that the version number within the plugin file matches what's listed on the site here. edit: Date too.
And insert my standard disclaimer about the evils of auto updating.
Sales & Support Lead — 18th November 2010 (1 year ago) #
Hiya Tracy,
We've just been working on the Update Notifications plugin on our end so we may have a thing or two still to update. I'll let the developers know what's happening and see if we can't get it sorted though.
Thanks!
Developer — 21st November 2010 (1 year ago) #
@drmike is spot on. We haven't updated the version number in the plugin file.
New version (1.0.5) will be released fixing this, you can simply update the version number instead of upgrading from 1.0.4 as well :)
Member — 24th November 2010 (1 year ago) #
Changed remove permalinks to 1.0.5 and nothing happened, changing Login Image to 1.0.5 did remove the warning... if permalinks is moved back to what I had at 1.0.3 there is no warning, so it appears the warnings aren't consistent for the different plugin components in rebranding pack.
Also, all plugins I've downloaded have version of 1.0.3 of Update Notifications, which is out of date... may be a good idea to not include the update notifications in each individual plugin so that it doesn't have to be updated in EVERY plugin once it changes versions.... maybe a text file note about it and where to find it would decrease work in upgrading each and every plugin when it changes version while still making people aware of it.... just a thought.
Developer — 25th November 2010 (1 year ago) #
Only the plugin with WDP ID: set to a valid ID will affect the update notification. I guess I forgot to mention which file to change the version number in. Anyway this shouldn't happen anymore as the Update Notification server was fixed only recently and that's what revealed this issue. We are sorry for the inconvenience caused..
Member — 31st January 2011 (1 year ago) #
I had to bring up a old topic but I am receiving notifications from that the re-branding-wordpress-mu plug-in needs to be updated, when I download the update and install the plug-in, I still receive notification that the plug-in needs to be updated.
I viewed the php file and the version said, 1.0.2.
Please advise
Member — 4th February 2011 (1 year ago) #
We're getting the same messages here. I've re-installed twice.
Sales & Support Lead — 6th February 2011 (1 year ago) #
Hiya guys,
Yeah, the rebranding pack is causing some issues with the individual plugin updates. We plan to offer them individually to keep this from happening. We're working on it at the moment and should have this resolved next week. Sorry for the trouble.
Thanks!
Become a member