• Hello,

    We are experiencing an issue with the Locate And Filter plugin after updating WordPress to version 7.0. Since the update, the post links generated with the |post_link| variable no longer work in both the navlist and the tooltips.

    Instead of displaying the correct post URL, the links are generated in this format:

    https://www.website.com/posttype-slug/'+decode((marker.post_link))+'

    When we roll the website back to WordPress 6.9.4, the links work correctly again.

    Could you please let us know if this is a known compatibility issue with WordPress 7.0, and if there is a fix or workaround available?

    Thank you in advance for your help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author dgamoni

    (@dgamoni)

    Hi
    fixed on new version 1.7.0

    Thread Starter ekebrice

    (@ekebrice)

    Hello,

    Thank you for the update.

    The issue is now resolved for the tooltips, but it is still present in the marker list/navlist.
    Could you please check the navlist as well?

    Best regards,

    Hey @ekebrice, I had the same problem since WP 7.0, the plugin was at the version 1.6.17.
    I managed – with AI help – to patch the output:

    add_action( 'template_redirect', function () {
    if ( ! is_page( 'your-page-slug' ) ) {
    return;
    }
    ob_start( function ( $html ) {
    $html = preg_replace( '/'(\s+)/', "'$1", $html ); // ' + -> ' + $html = preg_replace( '/(+\s)'/', "$1'", $html ); // + ' -> + '
    return $html;
    } );
    } );

    Don’t forget to replace ‘your-page-slug’ with your actual page slug when testing.
    The patch still holds with version 1.7.1.

    @dgamoni, thank you for the excellent plugin!

    Plugin Author dgamoni

    (@dgamoni)

    Hi guys!

    I’m spending less and less time working on this plugin, and I’d like to explain why these issues exist.

    About two years ago, the plugin was blocked because of strict security requirements. Until every line of code flagged by the automated security checks was fixed, the plugin couldn’t be published in the repository or used by new users.

    That’s why all these changes were made. Unfortunately, some of them broke existing functionality.

    Now, with the help of AI, we’ve finally figured out how to resolve the security issues while restoring the original functionality. However, this is a very time-consuming process.

    Since the plugin has only a small number of active users, and sales of the Pro version only cover critical maintenance, I can’t currently dedicate enough time to further development.

    The plugin has always been a great free solution with powerful features, and even today it still has no real competitors. That said, the codebase is over 15 years old, so it’s no surprise that it needs modernization.

    If you need the old behavior, working versions without these security-related changes are still available. For example, you can use version 1.6.15.

    Alternatively, you can use the Pro version. It includes many more features and doesn’t suffer from these issues.

    Thanks to everyone who continues to use and support this plugin!

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.