What’s new in FacetWP 4.3.2
FacetWP 4.3.2 was released on August 19, 2024. Among bug fixes and code improvements, it contains the following new and changed features.
New visual code editor
Based on user feedback we built in the CodeMirror editor. CodeMirror comes already built-in with WordPress: it is used in the File/Theme Editor.
In FacetWP, the editor it is now implemented in three places: the code textareas in the Display tab and Query tab of Listing Builder listings in Dev mode, and in the Marker content field of the Map facet.
The automatic code coloring and indenting will help to prevent errors when writing template code and query arguments. The editor has a built-in search function. To use it, click in the editor, then use Ctrl+F (Windows/Linux) or Cmd+F (Mac).
Improved update notifications
Some users reported issues with not always seeing plugin and add-on update notifications, when new versions were available. This happened most often in WordPress multi-site installations.
We rewrote the update check code, which should fix these issues. If you are still not getting update notifications when you expect them, first try these suggestions. If that does not help, open a support ticket.
New Debug Mode warning
FacetWP’s Debug Mode is indispensable when diagnosing issues, also for our support engineers when debugging user issues.
However, Debug Mode should be disabled again when it is not needed anymore for troubleshooting, because it exposes some of your FacetWP settings and can influence loading speeds. To make you aware it is enabled, we added a red warning icon to the Settings nav item, and a warning label next to the setting itself:
Other fixes and improvements
In addition to the above, this update contains the following fixes and improvements:
- Hierarchical fSelect facets now support up to 6 depth levels in their indent CSS, where it supported only 3 before.
- Listing Builder Button items can now be translated with the facetwp_i18n hook.
- We fixed an issue with Elementor’s widget pagination malfunctioning when Advanced Custom Fields was also installed. The issue was caused by changes in Advanced Custom Fields version 6.1 that were interfering with FacetWP’s query detection logic.
- We fixed an issue with server cron indexing not automatically resuming after it had stalled, if FacetWP’s automatic indexer was disabled.
- We fixed an issue with the indexing of (label) values of ACF fields that are in nested ACF Repeater fields.
- We fixed an issue that caused out-of-stock products to still be indexed even when FacetWP’s Index out-of-stock products setting was disabled.
- The “Sort by” facet setting was given a default of “Highest count” to prevent a blank value in specific use cases after updating.