CMS Made Simple Forums

I understand your concern, but not to worry, is in the works. No release has come out recently because some work has come up and then the CMSMS core itself. But the project is not abandon-ware, and will soon see a new release.

postiffm wrote: ↑Fri May 24, 2024 4:50 pm Please don't take my question/comments as a criticism

No worries, I didn't.

Thank you. Could you outline how to filter those notifications? https://www.slingacademy.com/article/php-enable-disable-warnings-notices/ under Configuring Error Reporting I thought I was safe to suggest count would be a built-in: https://smarty-php.github.io/smarty/sta ... ier-count/ Well, it has ...

As stated before, the warning is not an error, so no need for a fix. Whether count is going to be a built in modifier or not, is for the smarty team to decide. In any case registering EVERY PHP function with Smarty as a modifier and then maintaining it (even if we only select a few of the more popul...

php.ini doesn't stop these errors appearing in the admin - can you advise other things i can try so that they can't be seen? (probably my lack of knowledge at play here) Well, it should! Maybe the server configuration considers the index.php under the admin folder as a different script environment ...

Warnings are not errors, and are there for a reason. These deprecation warnings are being triggered by Smarty and have the purpose to warn the developers that things will change in the future versions of Smarty. The way we are going to handle these changes are still under debate and we are not yet s...

For the moment you can safely disregard that particular red mark. Typically we make the choice to limit as both minimum and recommended the most recent stable versions of the branches we tested. That is the safest assessment not necessarily the lower nor upper limit of the versions that may work wit...

So I think... This is not "it looks like a bug related to a fix for newer php versions", - but rather a lack of serious testing and insufficient verification. - The release of this version despite the fact that numerous problems had been reported and not corrected prior to this release. Y...

creopard wrote: ↑Fri May 03, 2024 2:52 pmI guess there might be an issue with the "global" scope?

Possibly, thanks for sharing! We'll dig a bit more in the meantime.
Thx again!

If you have any possibility send me (via PM if you will) a test case. I'll try to reproduce it, thx.

Do you have any errors or warnings in either PHP error log or even admin log of CMSMS? There has been some reports of a different behavior of the {content ...} block with inherited templates and we are investigating the issue. It looks like a Smarty change but it may also be at the CMSMS parser leve...

It looks non disruptive enough to warrant a replacement, I'll probably do it if nothing else breaks. Thanks for the heads up.

I suspect that's the apache access log, not the php error log

I have an UDT which gets data from one LISE Instance while presave to another LISE Instance, but it's not working (Server Error 500) [...] Maybe an UDT with a LISE instance presaving to another LISE instance is not possible? First of all check your PHP error log, a Server Error 500 is a PHP issue a...

The only reason I can think of for that error to be triggered is for the <site_root>lib/plugins/function.cms_action_url.php to be missing or corrupted. Please check if that file is there or do a site checksum on the core files.