🐞 Fixes​

• Options: Fixed issues with options saving (on the start screen of mapsvg control panel)
• Permalinks: MapSVG didn't work with disabled Permalinks in WordPress. This has been fixed.

🐞 Fixes​

• Duplicate: Duplicating a map now correctly updates the map ID in the "CSS" tab, preventing conflicts with the original map.
• Shortcodes: fixed rendering issues of shortcodes in mapsvg templates

MapSVG has been checked by PatchStack team and they found a few security issues. All of them have been fixed!

🐞 Fixes​

• Security issue: fixed "arbitrary file download" security issue
• Security issue: fixed "privelege escalation" issue
• Security issue: fixed "broken access control" issue
• Security issue: fixed "sql injection" issue

🐞 Fixes​

• Security: fixed minor security issues

🐞 Fixes​

• ACF filters: fixed filtering by ACF fields. ACF fields were not available to choose as a fields connected to filters.
• CPT: fixed handling of post type names containing dashes
• Layout: fixed invisible address drop-down field which gets hidden behind other fields

🐞 Fixes​

• Minor bugfix

🐞 Fixes​

• Security: Improved SVG file sanitization. For users with the unfiltered_html = false option, SVG files are now sanitized: MapSVG removes JavaScript code and other potentially dangerous elements and parameters. By default, unfiltered_html is enabled for Administrators and Editors on single-site installations, and disabled for everyone except Super Admins on multisite installations.
• Security: MapSVG now blocks the use of shortcodes in map templates unless they are explicitly added to the list of allowed shortcodes in the MapSVG settings. You can configure this option by clicking the "Settings" button on the MapSVG start screen.

🐞 Fixes​

• Minor bugfix

🐞 Fixes​

• Templates: fixed rendering of WP posts in templates

🐞 Fixes​

• Vulnerability: removed SVG file path traversal possibility during file uploads
• Vulnerability: sanitize SVG files, remove JS code