Hey folks, how are you doing?
First of all, I’d like to apologize for my absence on the Facebook group. To be completely honest, the constant queries on updates and potential release dates were having a negative impact on me and were reflecting on the quality of the work and the team’s moral, especially as we encountered a couple of major roadblocks.
Sorry for that.
We’ve been working non-stop on this new version and now that we think most of the unknowns are behind us, I’ll get back to our schedule of regular updates and keeping up with the community.
This update is long overdue, so here we go.
I have just released the Alpha 5 of WP Ultimo 2.0 to our group of early testers. It has been nearly 2 months since our last post where I claimed we were almost there. Since then, we hit some roadblocks with the migrator from 1.X to 2.0, which is a major piece of the puzzle for this release. I mentioned this before, but we have some very large networks running on WP Ultimo and we need to make sure the migration path for 2.0 is clear and as hassle-free as possible.
We like the idea of being loyal to our existing customers and prioritizing their needs, so we won’t release 2.0 without the migrator for new networks as many suggest. That might sound like a good idea but it could also cause a number of other issues that would be a nightmare to fix later on.
The Alpha 5 build brings the state of the admin portion of the plugin to pretty close to its final form.
It also implements most of the speed optimizations we could do by this point. Our internal tests show that the performance is at least on par with the current 1.X version, the difference being that the 2.0 is built to really make use of WP caching APIs, so if you have something like Redis or Memcache active for object caching (as most managed WordPress hosting providers do today), performance should increase even more dramatically.
API endpoints and auth using key/secret should be working as well on this build, but we’re still working on the documentation.