CMS Made Simple Caching Problem

[nielsenrc]

Specs:

Linux CentOS WHM/cPanel server running CMSMS 1.11.1 "Baltra"

I recently migrated the site to a new server, and since then the UDTs and GCBs periodically disappear with a comment <!-- [udt or gcb] blob does not exist -->

If I clear the 'cache' and 'templates_c' directories, the UDTs and GCBs are restored. I have tried disabling every caching setting I can think of in the CMS.

Multi-part question:

1) Does anyone know why this is happening? If so GREAT! Fill me in.

2) If not, does someone know how to permantently stop the CMS from caching at all? I'm OK with either solution.

[milehigh]

Try upgrading to 1.11.6. I had a similar issue that seems to have resolved itself after upgrading a site on 1.11.2 that was exhibiting that same behavior.

[Dr.CSS]

Upgrade to see if that helps as we only support the last 2 versions...

[nielsenrc]

Thanks guys - I will give it a try and report back.

[nielsenrc]

Well upgrading might solve the problem but it appears to fundamentally break the back end.

TBH - I don't have these problems in the Wordpress world. I think I'm just going to convert the site over to Wordpress and be done with it. Versioning and upgrading in CMSMS is just too much trouble.

[calguy1000]

1. The string 'blob does not exist' could not be found anywhere in CMSMS (I did a recursive search through ALL files). Therefore I would suspect that the problem you are having is related to either a custom plugin or third party module on your site. not related to CMSMS itself.

2. "it appears to fundamentally break the back end" provides no information as to what is causing the problem.

[edit]
3. You asked for support for a version of CMSMS that is not supported, when it is clearly documented that we do not support anything but the previous 2 stable versions of CMSMS.
[/edit]

We have insufficient information to be able to help you with your issues and therefore you have not gotten any constructive assistance.

Have fun with wordpress.

[nielsenrc]

I realize my post wasn't terribly constructive - I'll provide more detail:

1) The only custom module I use is one I ultimately wrote - religiously avoiding the API whenever I could as it seems to be deprecated and broken with every successive release. It's possible that somehow MySQL is returning this - but who knows. After enough 'what's wrong with the latest cmsms upgrade' me and my development team have lost interest in trying to figure it out. I've written a script to export CMSMS data directly into Wordpress - it's not bad. But you don't care about that so I'll move on..

2) I'm unable to edit pages. This has happened a few times as I have had to determine what has been broken in the latest CMSMS - like suddenly not being able to use require in a UDT or any other number of weird quirks we've encountered. It seems to be template related - but after scrubbing the template for a few hours and not getting anything in the way of a meaningful error message in debug mode - eh... moving on.

3) And you only support that far back for good reason: your team's development philosophy could well be summarized as this: "We do whatever the hell we want, you need to deal with it, and if you have a problem it's probably because you suck at PHP/Servers/Technology".

This message board is filled with snark from CMSMS devs making fun of posters and acting annoyed that people aren't having a good experience with such a finicky, aggressively non-backwards compatible CMS.

Granted, you guys do this on your own time as far as I can tell. Beggars cannot be choosers - I thank you for providing free software. However, there are things endemic to your development philosophy that have rendered me unable to continue to deploy your CMS for my company's projects.

I wish you all the best - and I hope that you can take this feedback to heart without becoming defensive and condescending and consider how you can improve both your software and your community by not trolling your own message boards and implementing better and more backwards friendly development practices.

Your idea isn't bad - but the execution could be much, much better. Respectfully.

[calguy1000]

The issue with UDT's in page templates was fixed in 1.11.4 or 1.11.5, and documented in the changelogs.

[Dr.CSS]

I had the same problem, no error message but unable to edit pages, I had to change all the {stylesheet} calls to {cms_styelsheet} and all was fine...