5.9.9.2
Última10 correções
Corrigido
- Login form stayed stuck with a hidden button when a security plugin redirected the login to a two-factor step (for example Kadence or Solid Security) or the server returned an error. The form now continues to the two-factor page, and on other errors shows a message and the button again
- Google Sheet / CSV API connector returned the rest_forbidden error instead of the sheet rows, so the field picker of dynamic elements showed only numbers and single letters. Requests to the site's own CSV route run in the same request now, and error responses (HTTP status outside 200-299) are not used or cached as rows anymore
- Visibility conditions and Visibility block - custom field conditions with {TIMESTRING:...} failed for fields that store Unix timestamps, for example WooCommerce _sale_price_dates_from and _sale_price_dates_to. Rules like _sale_price_dates_from = {TIMESTRING:now} work now
- Exist / Not exist conditions failed when a {TIMESTRING:...} value was left from a previous comparison operator, and numeric ranges like 0|100 were always false
- PHP warnings in the metaget REST route when the editor previews a Meta block of a query loop (postId 0). The latest post of the selected post type is used for the preview again
- translations from the plugin languages folder (for example created with Loco Translate) were not loaded because of a wrong text domain path
- Prev / Next labels of numeric filter pagination stay translated when pagination is rendered again after an AJAX filter request
- filter panel keeps the meta conditions of the query block and combines them with the selected filters, and the sorting of the query block is kept until a sorting option is selected in the filter panel
- Site option bindings can read the values of fields registered on ACF and ACPT option pages by their option names again (options_my_field, box_field)
- numeric dynamic values (for example ACF image IDs) are returned as strings to the editor, and empty ACPT repeater data no longer throws warnings