I had tested and set up Toolset on one of our sites, and now I was moving it to another. Both sites are on the same host and are identical. I exported all the Toolset settings and data from the first site and imported it into the new site.
Everything works, except inserting fields into views. When working on a View, I click on the "Fields and Views" button, it opens up the "Fields and Views Shortcodes" window where I can select what I want to insert.
But, no matter what I click on, the loading spinner displays and never disappears (see attached image). Nothing happens, even if I wait 10-20 minutes. This worked perfectly on our first site.
Do you have any ideas how we can begin to figure out what is causing this?
If you check in your browser console I expect you will see a JS error, can you confirm?
It seems like something went awry when transferring your site. The simplest and least-prone-to-error way to transfer a site is with a plugin such as Duplicator or All in One WP Migration.
How did you do it? Am I to understand you went to Toolset > Export / Import to export your Types and Views settings and then imported them on the target site, and it failed with the above problem?
Thanks for your response. We couldn't duplicate the site since they have slightly different posts/pages, but we did go to Toolset->Export and exported everything (types, custom posts, etc.). The new site was a clean install regarding toolset.
There is a js warning: "[Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience..." but that warning is also on the other site which works, so I don't think that's the cause.
Also note that we had only some test views on the original site. We deleted those before exporting and importing, since we wanted to create the views from scratch. So this issue is only on new views.
We had a custom plugin that was turning on error reporting with
ini_set('display_errors', 1);
and that was somehow affecting the Toolset plugins. Not sure why that same plugin was not affecting Toolset on our other site, but anyways we commented out that line and everything's working.
