Description of problem: I'm running wordpress through OpenShift. Upon being prompted to upgrade my installation by wordpress to 3.9.1 I upgraded. After the upgrade the notice to upgrade would not go away so I upgraded again. I might have even attempted the upgrade a third time. Regardless, wordpress now appears to be in some sort of loop. I have received at least 12 emails informing me my installation has been updated. http://blog-steveno.rhcloud.com/ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Looks like the version of Wordpress on that site is 3.9: <meta name="generator" content="WordPress 3.9" /> The cartridge has already been updated to 3.9.1, but it looks like the wordpress-driven upgrade from 3.9 to 3.9.1 is failing.
After running the upgrade in the wordpress admin console, the admin console still shows 3.9 as the installed version. I see this on my gear: [....rhcloud.com app-root]\> grep -R "\$wp_version = " . ./data/current/wp-includes/version.php:$wp_version = '3.9.1'; ./build-dependencies/3.9/wp-includes/version.php:$wp_version = '3.9'; ./runtime/data/current/wp-includes/version.php:$wp_version = '3.9.1'; ./runtime/build-dependencies/3.9/wp-includes/version.php:$wp_version = '3.9'; ./runtime/repo/php/wp-includes/version.php:$wp_version = '3.9.1'; ./repo/php/wp-includes/version.php:$wp_version = '3.9.1'; Looks like the downloaded version of wordpress is still in the build-dependencies folder. Are the build or deploy hooks copying original downloaded files on top of wordpress-upgraded files? This would be bad... the upgraded databases could be accessed by old code.
I won't spam this every time I get an email, but as an FYI they continue to roll in. My latest was today (May 12th) at 3:55PM according to the time stamp in Gmail.
That's due to wordpress automatically trying to update itself. I think you can turn that off for your installation until we figure out why the update process isn't succeeding: http://codex.wordpress.org/Configuring_Automatic_Background_Updates
I'm also getting emails from no-reply about an update of WordPress 3.9.1 to 3.9.2. It hasn't updated it and keeps sending me emails over and over. Can something be done?
I have the same issue, updating from 3.9.1 to 3.9.2, but I don't have automatic updates on, so I'm trying to do it via the Wordpress Dashboard. It appears the upgrade completes, but then shows you a 'Welcome to 3.9.1' page, and the update shows as still available on the 'available updates' page.
http://fedoraserver-wgblog.rhcloud.com/ is having the same issue with a notice coming in every twelve hours reading: Howdy! Your site at http://fedoraserver-wgblog.rhcloud.com has been updated automatically to WordPress 3.8.4. For more on version 3.8.4, see the About WordPress screen: https://fedoraserver-wgblog.rhcloud.com/wp-admin/about.php WordPress 3.9.2 is also now available. Updating is easy and only takes a few moments: https://fedoraserver-wgblog.rhcloud.com/wp-admin/update-core.php Keeping your site updated is important for security. It also makes the internet a safer place for you and your readers. If you experience any issues or need support, the volunteers in the WordPress.org support forums may be able to help. http://wordpress.org/support/ The WordPress Team
Hi, for what it's worth, I set up the blog Stephen mentions in comment 7 and I just used the Wordpress cartridge that was provided in the OpenShift UI. There wasn't any special / exotic setup involved.
After I tried the manual update some time later I started getting the automated update emails, and I've been getting approx one a day since my post above.
Any progress on this? It's really quite irritating...
I just tried updating my blog again since Wordpress 4.0 is out. Still broken. After going through the automated update process for 4.0 it still comes up with the "Welcome to 3.9.1"...
This is back again now and this time I'm getting two messages every few hours telling me that my site was upgraded to both 3.8.5 and 4.0.1.
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.