2.0.11 is finally out!

So, it took much longer than expected, but here we have 2.0.11.

As I mentioned before, this version aims to address some issues that are in need of fixing for a while now.

These include a couple of major ones, such as:

  • Customers being added to the main side as admins in some edge case errors during sign-up;
  • Site duplication not being able to manage foreign key constraints – which broke data integrity with some important plugins, such as Bookly;
  • Incompatibilities with themes adding “beautifier” filters to the post content, replacing important elements, and breaking Ultimo shortcode/elements;
  • Incompatibilities with Avada, FluentCRM, Bookly, and more;
  • Sunrise has an additional check to prevent its functionality from being loaded when WP Ultimo is deactivated;
  • Plugin & Theme limitations not working properly – plugins were not being hidden or activated for accounts;
  • Blocking access to the front-end for expired memberships not working;
  • Much more, the full changelog can be found below.

Some other issues were addressed in a less-than-optimal way, such as updating payment methods. With Stripe, we now redirect customers to the Stripe portal, where cards can be updated. The ideal solution is already in the works for 2.1, which uses the Forms implementation we are building for that release.

In terms of new features, this version includes some nice additions, such as the ability of attaching specific domain selection options to a given Site Template, for example.

Other additions include:

  • A panel on the Customer edit page where all the meta data collected via registration forms can be viewed and edited;
  • When changing the status of a membership to cancelled, an option appears allowing admins to also cancel the membership on the gateway used.

On the 2.1 development

I’m planning to use the daily updates to add previews of the features on 2.1 and how they’ll work. In terms of a timeline, the aim is to have the first alpha out on Thu, April 21.

Thank you to all of our community members that help us validate this version on the past few days.

Kind regards,


Version 2.0.11 - Released on 2022-04-09
* Important
* Fixed: Plugin & Theme Limitations not being loaded, leading to plugins not being hidden, or auto-activated after registration;
* Fixed: Site duplicator now deals with plugins that have custom database tables with foreign key constraints - for example, Bookly;
* Fixed: Incompatibility between Avada and mapped domains;
* Fixed: Incompatibility between Avada and template previewer;
* Fixed: Incompatibility with FluentCRM breaking the registration flow;
* Fixed: Domain mapping issues on previous build;
* Fixed: Payments pending on trial plans;
* Fixed: Products with wrong duration after checkout;
* Fixed: Sites created in double in some circumstances - specially when using Stripe & Stripe Checkout;
* Added: A completely re-designed and re-written SSO module, built to work in a higher level of abstraction to support all current and future possible use cases; It deals natively with:
* Security: there's a token exchange protocol that verifies both sides of the auth process;
* Cross-scheme Auth: When we are not able to access remote cookies due to different schemes being used, we force a regular redirect flow to authenticate the customer regardless;
* Admin Panel Access: Prevents the auth_redirect function from sending the request to wp-login.php before SSO has a chance to kick in;
* Auth for different Domain Options: SSO no longer focuses on mapped domains only. It gets triggered anytime there's a mismatch between the target domain and the main network domain. This allows it to work with sites that were registered using different domain options offered on checkout;
* Loading Screen: the new SSO offers a setting that adds a loading overlay when SSO is being performed on the front-end;
* Support to Incognito Mode: most browsers prevent cookies from being set from third-parties, nowadays. Our SSO detects incognito mode and forces a full redirect, instead of trying to authenticate directly with the verify code;
* Added: Placeholders on Thank You page snippet code editor, to pass values to conversion snippets; 
* Added: Country classes with state and city lists to allow for more granular control over how taxes apply territorially, as well as to guarantee that valid billing address info is entered during checkout. At the moment, the following countries are supported: US, GB, BR, FR, RU, DE, NE, ES, CA, CN, ZA (this list was devised based on our current customer base, new countries can be added as requested).
* Added: REST API field requirements and descriptions are now compiled and saved as static files at build time. This is done because we use reflection on PHPDocBlocks to generate the documentation of the fields, and comments might not be available if op_cache is enabled on production, causing the REST API to break;
* Improvement: Add CNAME records from Cloudflare to the DNS checking results, in addition to A and AAAA;
* Improvement: Updated DNS lib to prevent memory leaks when checking for DNS;
* Improvement: Adds fatal error catcher when the DNS resolver runs into a memory limit error, although this no longer happens due to the above fix;
* Improvement: Using CSS grid to lay fields on the checkout field instead of flex/float. This cleaned up the fields markup a good bit and makes it more customizable. By default, the checkout form is a two-column grid, with fields spanning the two columns;
* Improvement: Better responsiveness on the checkout form, resulting from the use of CSS grid;
* Improvement: Replaced the old hacky implementation of the Site URL prefix and suffix blocks (disabled inputs) with a proper flex block with a prefix and suffix element;
* Improvement: Checkout field blocks use less opinionated HTML tags (div, instead of p) to maintain semantic value and escape the default spacing CSS rules applied to paragraphs;
* Other
* Fixed: Negative values on sign ups by country widget;
* Fixed: Remove the email error message on sign up validation;
* Fixed: Taxable toggle on product update;
* Fixed: Discount code migrator not bypassing validation rules;
* Fixed: Error on site creation process passing the customer rules in the main site;
* Fixed: Makes sure the auto-submittable script is only added after wu-checkout was loaded;
* Added: Filter available templates on template viewer with selected products in checkout form;
* Added: Option to add a page on main site to redirect customer in blocked sites; 
* Added: Hide customer sites from network admin top bar;
* Added: Created the wu_bypass_unset_current_user filter to allow developers to bypass the user unset on multiple account feature;
* Added: Possibility to see and change on customer admin page, the customer custom metadata set when user sign up.
* Added: An public api to customer meta data that handles sign up form titles and types of fields;
* Added: Memory trap to avoid memory limit fatal errors in some cases;
* Added: Support for Jetpack plugin in mapped domains;
* Added: Stripe Portal for customer payment manage;
* Added: Option to add a custom redirect path in Login block;
* Added: New image upload field layout with the stacked option;
* Improvement: New field for company logo on settings;
* Improvement: Block frontend site when a membership is not active;
* Improvement: sunrise.php install step on WP Ultimo Install Wizard;
* Improvement: better define of SUNRISE constant on wp-config.php on WP Ultimo Install Wizard;
* Improvement: Better UX on thank you page, showing if the site is in creation process;
* Improvement: Breaks the gigantic functions/helper.php file into lots of different small files with specific public apis, allowing us to make sure we only load what we really need in a sunrise time;
* Improvement: Adds a sunrise meta file to control whether or not we need to run ultimo tasks when Ultimo is disabled or not present;
* Improvement: First step in the direction of removing jQuery as a checkout form dependency given by dropping jQuery Migrate as a dependency;
* Internal
* Internal: Replaced all development scripts, build tasks, and more with the internal development library called MPB;
* Internal: Adds the Query Monitor panels to help debug issues while developing WP Ultimo core;
* Internal: Adds the development sandbox toolkit that allows developers to run and listen to particular events in a isolated context. Useful for timing how long a given hook takes to run, or to trigger build tasks that rely on a real WordPress installation running Ultimo to work;
* Internal: Updated node dependencies to their latest versions;
* Internal: Switched Tailwind to JIT mode, to save precious KBs on the generated framework.css file;
* Internal: Removed PHP Scoper as a composer dependency (it is now handled directly by MPB);
* Internal: Removed unnecessary composer dependencies;
* Internal: Updated composer dependencies to their latest versions;
* Internal: Finally switched the composer version internally from v1 to v2;

Share this post


2 thoughts on “2.0.11 is finally out!”

  1. Avatar of philipp lang

    Hi Arindo, thank you for your efforts! I will do some testing and updating my bug reports. Where would I find the full changelog? Best regards.

Leave a Comment

Your email address will not be published. Required fields are marked *

Related Posts

WP Ultimo 2.0.20 is available

Following a new release schedule, focused on bringing a new version each three weeks, today we make WP Ultimo 2.0.20 available to everyone. This new stream of releases is giving us a better time to work on more significant updates, changes to come, and a bigger window to run tests. This new version brings several

Read More →

WP Ultimo 2.0.19

Hello everyone, It took a bit longer than originally expected to release this build as it touched sensitive portions of the payment flow and we wanted to be extra careful with 2.0.19 testing. In version 2.0.18 we introduced a new form to deal with pending payments, A handy link to the payment form on the

Read More →

2.0.18, Woocommerce and AffiliateWP

Today we release WP Ultimo 2.0.18. It took us more than we thought it would, but we believe it was for a good reason since we added various improvements. We will detail the most important ones in this article. As always, you can find the complete changelog at the end of this post. An overview

Read More →

WP Ultimo 2.0.17 and 1.10.14

Hello, everybody. We just released version 2.0.17 as a hotfix for bug reported in the process of creating new sites with version 2.0.16. The patch was made available yesterday for affected customers and they confirmed its effectiveness. Of course, if you find anything weird, please, let us know and we’ll get to it as soon

Read More →

2.0.16 has been Released

Hi everybody. Today we are launching the 2.0.16. This is a small release to address some of the existing problems while we discuss our roadmap for the coming months with big news to arrive soon. Following the latest releases, we work on 2.0.16 to bring more consistency to the checkout process, adjusting the PayPal gateway

Read More →

A quick update on releases this week

Hey guys! This is a quick update to let you know that we will most likely not have a release this week. We’re spending some quality time as a team going over our backlog, organizing the items on our roadmap according to their priority, and planning the next couple months of development for WP Ultimo.

Read More →

Ready to get started?

Easily build your own WaaS platform with WP Ultimo!