Skip Navigation

[Escalated to 2nd Tier] Problems with Toolset since migrating from a shared server to a dedicated server

This support ticket is created 5 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 22 replies, has 4 voices.

Last updated by Waqar 5 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#1361129

Hi Tom,

Thanks for the update and glad that the views are sorted out.

This new report about the Access and the settings screen, are you experiencing this on the main live website or on a localhost copy?
( note: the login information that was provided earlier for the live website are no longer working )

Whether it's a live website or a local install, I'll suggest the following steps to troubleshoot:

1. Please make sure that WordPress, the active theme and all plugins are updated to their latest versions.

2. You can turn WordPress debugging on ( ref: https://wordpress.org/support/article/debugging-in-wordpress/ ) and check if any errors or warnings are shown on the screen or in the server's error logs. This should provide better insight into the possible cause of the issue.

3. If the issue is limited to only one install (either the live website or the localhost copy), then it would mean this is something specific to the server's configuration and not the web site's content (database and files), in general. This is why it is very useful to test the website's clone on a second location/server.

I hope these points will help and you're welcome to share the latest clone/snapshot of the website, in case the issue still persists.
( ref: https://toolset.com/faq/provide-supporters-copy-site/ )

Note: Your next reply will be private.

regards,
Waqar

#1361331

Hi Tom,

Thank you for sharing the admin access.

The earlier backup package is much different than the current state of your website and for this troubleshooting, I'll need the current backup.

Do I have your permission to create and download a new duplicator package from your website?

regards,
Waqar

#1361361

Yes you have my permission Waqar.

#1361843

Hi Tom,

Thank you for your permission and I've downloaded a freshly created duplicator package from your website.

I'll be performing some tests on your website's clone on my server and will update you with my findings, as soon as this testing completes.

Thank you for your patience.

regards,
Waqar

#1361847

Thank you so much Waqar!

#1362105

Hi Tom,

During troubleshooting, I noticed that the issue with the tab switching for Toolset and Access plugin's settings originates from the "Social Login & Invitations" plugin.

You'll note that these tabs will start switching properly, as soon as this plugin is disabled.

This plugin loads its script files on all admin screens when they should be loaded only on its own settings screen. This is not something specific to Toolset plugins and other plugins which use tabs in the admin area can also get affected by that script.

Although we can't make any changes to how that plugin loads its resources, I've shared this report with our concerned compatibility team for further review. I'll keep you updated on the progress through this ticket.

For now, a quick fix can be to either keep that plugin disabled or replace the code in the plugin's "admin.js" file ( /wp-content/plugins/twistpress-social-login/assets/js/admin.js ) with the following code:


jQuery(function($) {

    $('body.toplevel_page_twistpress-social-login .enable').on('change', function() {
        if ($(this).val() == 1) {
            $(this).closest('.form-table').find('tr').removeClass('hide');
        } else {
            $(this).closest('.form-table').find('tr:not(:first-child)').addClass('hide');
            $(this).closest('.tp-social-login').find('.info').addClass('hide');
        }
    });

    $('body.toplevel_page_twistpress-social-login .show-info').on('click', function(e) {
        e.preventDefault();
        var el = $(this).closest('.tp-social-login').find('.info');

        if (el.hasClass('hide')) {
            el.removeClass('hide');
        } else {
            el.addClass('hide');
        }
    });

    $('body.toplevel_page_twistpress-social-login .nav-tab').on('click', function() {
        $('.nav-tab').removeClass('nav-tab-active');
        $(this).addClass('nav-tab-active');

        $('.page-tab').hide();
        $('.' + $(this).attr('data-page')).show();
    });

});

I hope this helps and let me know how it goes.

For a new question/concern, you're welcome to start a new ticket.

regards,
Waqar

#1362237

Hi Waqar

Thanks, you did a good job.
Yes keep me updated on the progress through this ticket.

Thanks a lot for your help.
Regards,
Tom

#1362337

You're very welcome Tom and glad I could help.

I'll update you once I'll hear back from the compatibility team.

regards,
Waqar