The "Is for new users registration" setting in the NEW CMS was not functioning correctly. When enabled, it failed to automatically add the email field to forms, activate synchronization with Salesforce Contact objects, or map the email field to Contact.email in Salesforce.

In the NEW CMS, it was not possible to link an ARS (Advanced Registration System) registration to a specific registration form, unlike in the Old CMS where this functionality worked as expected. This meant that when creating an ARS for registration, the system did not display the existing registration forms as options to link the workflow.

The payment component was not functioning in isolated environments. When testing new form field improvements with the payment component, it failed to redirect to PayPal or Stripe, which was unexpected. The problem was specifically identified when the site's locale was set to es-ES (Spanish - Spain), as PayPal requires a . (dot) as a decimal separator, and the es-ES locale uses a , (comma).

When using the "Save and Complete Later" option, any uploaded image was not being retained or restored.

The filter logic section in custom forms was difficult to read depending on the screen size.

This ticket addresses an issue where the "For Sharing Portal" option was missing from the new CMS layout. This setting is now included in the new CMS layout.

This release addresses an issue where the menu logic was not saving correctly in the new CMS layout. This has now been fixed.

This release addresses an issue where users were unable to assign visibility rules with session variables when creating or editing a page. This has now been corrected.

This release addresses an issue where the "Enable Custom Logic" feature was not functioning correctly with Listing Blocks in the new CMS layout. This has now been fixed.

This release addresses an issue where the ARS (Advanced Registration System) was experiencing problems, specifically with volunteer hour conditions not saving correctly and leading to 404 errors for sign-ups after editing. The root cause was identified as the use of special characters in the page name, which caused issues with friendly URLs.

The problem with "Branch Logic" editing mode when there were rules with a "greater than or equal to" logical connector has also been resolved.

This release addresses an issue where users were unable to move blocks within the new CMS layout. This has now been corrected.