CUNY Academic Commons

Thanks, Boone. Sorry to bother about this--I'm getting some pressure from the other folks at the Segal Center--they're wondering when today the new theme might be pushed through. They are wanting to send out a press release today and would like the website to be ready along with it.

On a related note--and let me know if I should open a new ticket about this--we noticed that when we make updates to the website using the dashboard, those changes aren't reflected until the next day. Is this due to a caching process that is in use on the commons sites? If so, is there any way this site could be exempt from that process at least until we get the site up and running?

Thanks so much, Boone.

Alex

Alex - I will do the release within the next two hours, and will update this ticket when it's done so that you have the info.

On a related note--and let me know if I should open a new ticket about this--we noticed that when we make updates to the website using the dashboard, those changes aren't reflected until the next day. Is this due to a caching process that is in use on the commons sites? If so, is there any way this site could be exempt from that process at least until we get the site up and running?

If I recall correctly, the "updates to the website using the dashboard" you're talking about are all related to the Advanced Custom Fields plugin. Is that correct? If so, then it's likely that the underlying cause is a bug in ACF that results in the cache not being properly flushed on save. If it's all settings, then it's likely a Commons-related bug.

Again, working from memory: on our previous server environment, I'd hardcoded an exception so that your site(s) didn't utilize the persistent object cache, because of the ACF bugs. It appears that these changes didn't get ported to our new server this summer, as we had to switch caching engines. I'll readd the exception. Can you please verify the URL that should be excepted from the caching layer?

Quick update: I searched on Google and found this ticket where the ACF devs basically admit that there is a bug, but then say that they'll only fix it if they hear lots more reports. This was a couple years ago. Oy. https://support.advancedcustomfields.com/forums/topic/unable-to-change-fields-once-ive-created-them/

I may take a few minutes today to see if I can spot the specific bug in ACF, as it'd be far better to fix it there than to disable caching for your entire site.

Thanks, Boone. That's frustrating that they're not fixing it! I'll let them know that we're experiencing the issue so that maybe they'll work on it for future updates. Squeaky wheel, right?

In case you still need it, here's the commons url for the current prelude website: http://preludenyc16.commons.gc.cuny.edu/.

Thanks again,
Alex

Alex - the update is live.

The ticket for ACF is at https://redmine.gc.cuny.edu/issues/6058. You're a watcher.

I've also blacklisted all prelude* sites in our cache system, so you shouldn't have the invalidation problem for now.

Thank you so much, Boone!