I am trying to make a new page with a new view, and update an existing view with a filter. Neither will allow me to update/publish the page. The update and publish button is disabled on toolset pages. Not on regular content.
Link to a page where the issue can be seen:
hidden link (I also made this page, but it won't show the view: hidden link )
I expected to see:
I have been trying to add a filter to the view to show all pages except "category=blog." I have no problem making the filter. But the page won't save. If you ask me, this is because toolset was linking to the development site URL. I changed it to the live site... and updated the plugins... but it is still acting like I have not registered toolset. I have. And the URL is in there... the key is registered. It isn't working.
I need this fixed today if possible. What do you need from me?
No. Please don't disable any of the other plugins, as the site is live. If you want to copy it down and try it that is fine, but not on the live site.
I am only having issues with the toolset pages.
I started to make a new toolset view today. That is when I noticed it. It would not publish/update. My thought was that it was due to the "license" being attached to the development site domain. And I changed that to the live site domain today and updated toolset plugins today. I tried to fix the problem that way, but apparently it is something else. You can check my license and the site domain matches the site.
Are you able to provide me with the PHP logs for your site ? As you can see on your site the view doesn't load but on the exact same site copy on my server the data loads. See Screenshots
Perhaps there is some data timeouts happening somewhere that is causing your view to not load completely.
I had another look at your site and it would appear that wordpress heartbeat is throwing an JS error on your page. This could also be related as this error doesn't occur on the duplicate.
I thought I would give you guys a resolution. The site had "Global Edge Security" software enabled at the host and it was the culprit. A cached version of the "authentication" would not clear till it was disabled and re-enabled. Now it works.