Andre

Thank you. Is this the expected behavior for future releases also?

I show 2 options for the Beta Tester plugin at wp-admin/tools.php?page=wp_beta_tester. The first is Point Release Nightlies and the other is Bleeding Edge Nightlies. Which should I have it set to if I want Beta or RCs without Alphas?

The expected behavior of the BETA tester plugin is to install an ALPHA? That’s silly. If that’s in fact the case can the RC announcement post be updated to make that clear? And the name of the plugin changed too?

On another note, when the real version of 4.1 is released will I be able to update to it using the built in updater on my installation that is currently saying it’s on 4.2 alpha (with the Alpha/Beta tester plugin deactivated)?

I’m having the same issue with updating to 4.2 alpha without the beta tester plugin activated and created a new topic as suggested – https://www.ads-software.com/support/topic/updating-takes-me-to-42-alpha.

If the expected behavior when the beta tester plugin is installed is for 4.2 alpha to be installed why does the announcement post for 4.1 RC1 suggest using the beta tester plugin to get RC1?

Is it due to a setting on my installation? It’s never jumped like this before and would like to understand why it did this time.

I had the same experience with the same version of the beta tester plugin. Will going from 4.2-alpha to 4.1-RC1 cause any problems?

Thank you. I believe the issue is deeper because some posts that are scheduled for the same time are posting as expected, which must mean something is firing the cron jobs.

JennyBHoney – Did you update to WordPress 4.0? I’ve noticed 3 posts missed their scheduled time since updating to 4.0 (2 missed on RCs and 1 missed on real 4.0). I believe all of mine were missed when multiple posts were scheduled at the same time and I believe it’s been the last post created of the group that was missed.

I think the same could have been accomplished if you us Multisite with either Multi Network (https://www.ads-software.com/plugins/wp-multi-network/) or Domain Mapping (https://www.ads-software.com/plugins/wordpress-mu-domain-mapping/).

I noticed it after merging several separate sites/installations into a multisite installation. My accounts on a couple of the individual sites were almost identical to each other with the same login, email, and nice name. I assume they had the same userid also because I believe I was the first user on a couple of them. What do you think of the possibility of the merging leading to the issue?

That worked. Thank you for your help and timeliness.

a:3:{i:0;N;i:1;s:12:”andrejcarter”;i:2;s:8:”kingston”;}

I didn’t post it earlier because I didn’t know if know this increased the risk to my site.

I’m having the same problem and I’m also using a Dreamhost VPS with PHP 5.3.x with Fast CGI, no X-Cache also.

I would like:

• An easy way to merge WordPress sites or at least have import/export include users and related data.
• A menu section for plugin settings so settings aren’t scattered all over the place.
• A Twenty Ten child theme that supports both BuddyPress and the bbPress plugin

Thank you reddshack!!!