Skip Navigation

[Resolved] Changes do not show up on site

This support ticket is created 5 years, 1 month 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.

This topic contains 2 replies, has 1 voice.

Last updated by maxfieldB 5 years, 1 month ago.

Author
Posts
#1354481

I am trying to:
See the changes I made to toolset happen on my site

Link to a page where the issue can be seen:
hidden link

I expected to see:
The changes I make on the backend

Instead, I got:
Previous versions of the site

Hello, I've run into quite a few problems getting my site up, and what is making it much harder to move forward, is the fact that I oftentimes make changes on the backend, only to *not* see these changes show up in the actual site.

For instance, I am attaching a simple view where the archive has been changed, with no change on the front end. Backend: "producedbyA" and the front end continues to read "produced"

All other changes, such as CSS, images, content, etc, take place immediately whereas Toolset changes are unpredictable as to if or when it will actually change something. Hitting the "clear custom fields cache" in settings does not help.

I have also cleared my server and browser cache.

I have become frustrated with how difficult it has been to set up a simple map with custom fields, and this issue of not seeing the changes go live, is making that frustration worse. You can see for instance that the setup of the k-12 archive is completely different than what is showing up not he site.

Can you please help me troubleshoot this?

Max

#1354483
Screen Shot 2019-10-02 at 5.00.05 PM.png

This is the image that shows the difference in text, but additionally none of my filters are showing up.

#1354493

Apologies. I am very embarrassed to admit that this was a *dreamhost* server problem. Please feel free to delete this ticket - sorry for the trouble!