Django caching issue. Reloading browser shows and hides TinyMCE edits.

Doc4

Running a Django site that appears to be caching the site and not letting go of that cache and/or multiple caches.

When I make an edit in TinyMCE using the Frontend site editor and save, I can see the change but when refreshing the page the change is removed. This goes back and forth with every single refresh of the browser. I've tried this in a lot of browsers, btw. When running this locally everything is fine, it's only when it's pushed up to Opalstack that we're seeing this issue. If we restart the server the problem goes away, but we can't keep restarting the server with every change.

Example: https://abcjesuslovesme.com/intentional-journey-group/
Look at the section of this page (third image down) starting with "Read what others say about Heidi’s work:" We've made several changes to this section which will be are shown if you refresh the page a bunch of times, it cycles through them all. There is actually no content below the headline, it's been removed, and then I added three periods to the end of the last line "Get Intentional About Your Journey..." and sometimes all three periods are there and sometimes they aren't.

Does anyone have any idea what the heck is going on? We've been looking for quite some time now and we're not getting anywhere. We think it might be tied to the Django-front module possibly running on Opalstack but can't find anything obvious outside of that. Wondering if Opalstack has some settings we're missing. Any help would be appreciated.

Example editing image. Open this image in a new window, sorry.

Doc4

You can also see the issue in the main headline "Become Intentional in Your Journey." refreshing the page sometimes shows that period, and sometimes it doesn't.

nick

Hello,

I see what you are describing. We're not enabling any server side caching by default at our end. There are options to manage cache control for static apps, but it doesn't look like you have those set in the dashboard.

For purposes of debugging, you can try disabling cache globally for Django (to rule it out) by adding something like this to your settings.py in your dev environment to see if this resolves the issue.

CACHES = {
    'default': {
        'BACKEND': 'django.core.cache.backends.dummy.DummyCache',
    }
}

You might also be able to get more details using the Django toolbar (which can be installed via pip) and then observing the requests to see if anything stands out. Have you tried something like that? Beyond this you may need to open a support ticket with more details about your Django app for further investigation.

Doc4

Thank you Nick. You guys are the best.

After sleeping on it we finally discovered the problem, and in case anyone else has this issue, here is what our dev worked out.

From our Developer:

Turns out the changes applied to the django-front source code in development were not applying to the server.

This happened because we used 'pip uninstall django-front' and it reported that the module was uninstalled on the server, but we noticed that the custom UUID class that was added to the html element was missing.

Turns out the uninstall command did not actually remove the 'django-front' package and it was overriding our customized version. We've never seen pip fail to uninstall a package, but I was able to manually delete the package and django was then able to pick up our customized version of 'django-front'.

That cache setting on this thread did work for disabling the cache, and that seems like a good trick if we run into any cache issues in the future. I was able to use the default caching settings after I removed the old 'django-front' package.