CMS Made Simple Forums

PinkElephant, thanks for the comment! It reminded me to report the following: Dev Team, please note that there is a copy of doc/db_error.html in the data/data.tar.gz archive in the standalone Beta3 installer (cmsms-2.2-beta3-install.expanded.zip). Not sure if is also included in the PHAR installer. ...

Summary: The PHAR installer upgrade "resets" previously set 'root_url' and 'ssl_url' $config variable values which results in these variables no longer having their values automatically generated. Downstream effects impact the entire system. Details: I've been testing upgrades of 1.12.1 in...

Understood. But, just to be clear, can developer code catch and handle an CMSMS\Database\DatabaseConnectionException? If not, then while the loss of customization is unfortunate, it's not a huge deal. I'm old enough to remember when one could buy Generic "BEER" in the store--nothing but an...

In CMSMS 1.21.1, and earlier releases, the adodb_error() function would invoke an optionally user defined db_error.html page so that developers could customize/style how DB errors would be reported to visitors of that site. I have sites that use this. It appears, however, that this functionality is ...

Thanks for the quick fix!!

[deleted by thread creator]

Hi, I'm upgrading my modules to be CMSMS 2.0 compatible and I noticed that the debug_to_log() function no longer prints the $title parameter to the output file, as it did in CMSMS 1.x. I can work-around this change, but thought I would mention it as it seems this may have been unintentional. If you ...

jalasju wrote:

staartmees wrote:It would be good to post your system information.

I'd be glad to post them, but what information do you mean?

Hi,

You might have a look here:
http://docs.cmsmadesimple.org/troublesh ... nformation

Oops! I just realized that I am still using one workaround. So, I have to correct my earlier statement. While current versions of CMSMS do work better, TinyMCE still has some remaining issues. A workaround is detailed in my last comment (dated 2012-12-13 00:54) of TinyMCE bug report #8692

Hi,

This looks similar to an old TinyMCE error caused by a bug in its filepicker.tpl template. But, that was fixed a few years ago. Are you using the Insert/Edit Image button in TinyMCE as your "picture manager"?

Hi Andrew, Are you running at least CMSMS version 1.11.12? If not, you might consider upgrading to version 1.11.13 or 1.12. The latest versions have a wonderful new feature, dynamic root_url calculation, that, at least for me, resolved the remaining http: vs https: conflicts that I was seeing when u...

Thanks for your reply. I appreciate your considering and discussing this matter. I think, however, you misunderstood my earlier post(s). I suspect we agree more than disagree. ... I'm not sure why would you want to use $config['admin_dir']/configs/ ... it should always be tmp/templates/ in any circu...

That was an interesting digression regarding templates, but to get back to my original topic, Smarty config files , let me give a simple example to clarify: On a CMSMS 1.11.12 site, my first CMSMS stylesheet contained the following: [[$cfgpath=cms_join_path(realpath(dirname($smarty.server.DOCUMENT_R...

The config dir was specified to tmp/templates in 1.11 when we upgraded smarty versions. Thanks for the quick reply. I see now that the change to tmp/templates is only part of the picture. Since CMSMS' upgrade to Smarty 3, I've been using Smarty.net's recommendation of putting config files outside o...

Hi dev team, After upgrading a CMSMS 1.11.12 test site to CMSMS 1.12, I was surprised to find that my Smarty "config files" stopped loading on all {config_load} tag calls in templates and spreadsheets. I investigated and found something curious on line 96 of lib/classes/class.Smarty_CMS.ph...