Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author wpdreams

    (@wpdreams)

    Hi,

    Are you reffering to this feature?

    I just tested and it seems to be working all right on our ends. We have not changed that part of the code within the current release, the issue might be in relation with something else as well.

    Can you please add a relevant URL where I can check out the problem? Thank you!

    All the best,
    Ernest M.

    Thread Starter dhampius

    (@dhampius)

    Yes, the same feature from the picture. I cannot provide a link yet, since my test instance is on a localhost related VM, but if you want, I can share my screen on Teams.

    To represent the issue, purge the cache from WP and from browser, reload the search engine and type something different than the string you have used before when It was working.

    My WP version is 6.1.1

    Thread Starter dhampius

    (@dhampius)

    Also, when I reverted to the old version of the plugin, the feature started working again.

    Plugin Author wpdreams

    (@wpdreams)

    I can’t seem to be able to replicate this in any way for some reason. Do you happen to see any error messages or anything in the browser console?

    Let me know if you have any dev/test environments where I can test this, I will test as soon as I can. Unfortunately I can’t do screen shares.

    Best,
    Ernest M.

    Thread Starter dhampius

    (@dhampius)

    Here you go.

    OS Ubuntu 22.04, tested on Chromium and Firefox.

    Plugin Author wpdreams

    (@wpdreams)

    Thanks!

    One of the errors on the console might be the cause of the issue. You may have a code in your site header (it refers to line 160 and 259), which are trying to use the jQuery as the “$” alias. However it seems like the “$” alias does not exists, that is a common cause for similar errors.

    Because that is a fatal error, it seems to be blocking further events or some of the script execution. Try looking for that specific line of code in your page source, if you resolve these errors it should resolve this issue as well.

    Thread Starter dhampius

    (@dhampius)

    Thank you for the answer, but I am using custom code for additional functionality and it is not possible to remove or edit it at this stage. I will stick with the old version.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘After upgrade from 4.10.3 to 4.11 automatic scroll to first match does not work’ is closed to new replies.