Conflict between new versions of Weaver Xtreme and WPFront Scroll Top

  • Resolved jawill

    (@jawill)


    1 year, 10 months ago

    Looks like there is a conflict between new versions of Weaver Xtreme 6.2.1.3 and 6.2.1.4 and WPFront Scroll Top (also latest version). We’ve noticed it on few, some of our websites which use both, WPFront Scroll Top and Weaver Xtreme. When WPFront Scroll Top is activated, any attempts to update Weaver Xtreme theme to latest version renders 403 Forbidden page. So for now we’ve disabled your plugin to update the theme. Just to give you more info, some of those sites are also using WPBakery Page Builder with Ultimate Addons for WPBakery Page Builder. Some other sites on which we are also using both Weaver Xtreme and WPFront Scroll Top are ok. We like your plugin very much and we would like to use it on those websites in the future. Any advice how we can fix that issue? We’ve already contacted Weaver Xtreme theme and it looks like it is not the theme issue.

    On all those sites we are running latest versions of other plugins and WordPress, e.g.:
    Weaver Xtreme Plus – Version 6.2
    Weaver Xtreme Theme Support – Version 6.2.9
    WordPress 6.2
    PHP version 8.1.18

    Thank you in advance for any advice.

    jawill

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Swathi S

    (@swathiswpfront)

    Hello @jawill,

    Can you please check whether the Attach on Shutdown Option on the Settings page is enabled?

    If enabled, can you please test after disabling it?

    Thanks!

    Thread Starter jawill

    (@jawill)

    Hello Swathi S,

    We never used that feature on any installation of WPFront Scroll Top?on our websites, but I’ve double checked it on that particular website and the Attach on Shutdown Option on the Settings page was and is disabled.

    Thank you for all your help! Really appreciate it.

    jawill

    Plugin Support Swathi S

    (@swathiswpfront)

    Hello @jawill,

    Can you please give us access to the site where we can check and verify the issue?

    Thanks!

    Thread Starter jawill

    (@jawill)

    Hello Swathi S,

    Sure, but can I have a private connection with you, since I’m going to give you the URL and login details. Can you please give me your secure email address or something like it. Please instruct me how I can do it safely and not in the public forum. Thanks.

    jawill

    Plugin Support Swathi S

    (@swathiswpfront)

    Hello @jawill,

    You can get in touch with us through the below link:

    https://wpfront.com/contact/

    Thanks!

    Plugin Support Swathi S

    (@swathiswpfront)

    Hello @jawill,

    We have checked your site and found that the forbidden issue is only on the Home page and the scroll top button is working fine on other pages.

    Can you look at the logs for errors after enabling debugging in WordPress and also on the NGINX server, link is attached for reference:

    Debugging in WordPress

    Thanks!

    Thread Starter jawill

    (@jawill)

    Hi Swathi,

    For safety, I’ve sent you my response to your email (as directed before). It includes some error log entries etc. Please have a look.

    Sorry, but for now I have to deactivate scroll-top. Site owner needs the front page to be accessible for their potential clients. It is an active and working site. And only deactivating scroll-top guarantee at this point the visibility of the front page.

    Thank you again for all your help. It is much appreciated! Thank you!

    jawill

    Plugin Support Swathi S

    (@swathiswpfront)

    Hello @jawill,

    Your SQL mode rules are blocking our js file and that’s why it’s not working.

    So, it’s best to contact mode rules coder with those error logs, maybe they can help with this issue

    I hope this helps!

    Thanks!

    Thread Starter jawill

    (@jawill)

    Thank you Swathi, for all your help. It is much appreciated!

    jawill

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Conflict between new versions of Weaver Xtreme and WPFront Scroll Top’ is closed to new replies.