CMS Made Simple Forums

Thanks Matt but I deleted via FTP /modules/CMSMSExt/* then uploaded from the backup of the Filesystem the v1.4.1 /modules/CMSMSExt/ so that would have also rolled back the moduleinfo.ini file, I didn't double check, but the FTP also didn't throw any errors or duplicate file conflicts. It is a myster...

Hi after doing a DB and file system backup, I have just upgraded from CMSMS v2.2.18 to v2.2.19 just to keep everything up to date. Also, the Hosting Co I use have an imminent end date on PHP8.0 so I also updated to PHP8.1. Toured the website and Admin back end - all good. Next step was do upgrades f...

SOLVED - data issue - notes provided in case anyone else suffers the same issue Just upgraded CMSmadeSimple from 2.2.16 to 2.2.18 and upgraded LISE by a version (or maybe 2) to LISE v1.5.5. I have approx 4 LISE instances running All 4 worked perfectly pre upgrades. Post upgrades 3 worked perfectly b...

question for the Dev Team I see that the bug has been fixed in the forge - is the fix (which I assume will be bundled in to 2.2.17) going to be released before the end of 2022 because PHP7.x ceases to be supported end of 2022 and this bug means that 2.2.16 can not be run in debug mode at all from Ja...

Thanks !!

I didn't see it listed on the fork page (https://www.cmsmadesimple.org/module-forking-project), so I failed completely to think to look at the Modules available.


Excellent thanks

Hi All I am overlooking something obvious ?. I have replaced FEU with MAMS and converted all the templates, embedded smarty, UDTs etc. For the simplest List user by Group use-cases that used to be done via CGUserDirectory I replaced it with {$mymembers = mams_smarty::get_users_by_groupname("gro...

Thanks DIGI3 I did in fact look for a link to the bug reporting for the core (I know how to navigate to bug reporting for modules) but I failed to find a link to bug reporting for the core - so thanks for that. And thanks to all of the Dev team, testers and translators for your excellent efforts And...

Hi Jean-Claude Etiemble Thanks for your suggestion - it is stock CMSMS2.2.16 + a few modules. CMSMS2.216 includes Smarty 3.1.31, not Smarty4.0 - I thought that CMSMS2.216 was supposed to be PHP8.0 ready ????. PHP7.4 is only 1 month away from end of life ( https://www.php.net/supported-versions.php )...

PHP8.0 CMSMS 2.2.16 config.php debug = TRUE php.ini display_errors=on php.ini error_reporting = E_ALL causes CMSMS to crash with error Fatal error: Uncaught TypeError: error_reporting(): Argument #1 ($error_level) must be of type ?int, string given in /homepages/38/d242029264/htdocs/acuk_cmsms2/lib/...

Wow that https://easythemes.ca/lise-instances/lise-leaflet a looks excellent - I wish I had found that 2 days ago.

Charles, in case you haven't realised it easythemes.ca is Matt Hornsby aka DIGI3 - thanks Matt/Digi3

Hi Charles Butcher As Digi3 hints in his later reply - it all depends what you need. If you just need an entirely static (non interactive, no directions) map then the Google Maps Static Map API is super easy - it is just an image tag where the source of the image is the https call to the google API ...

Try foreach ($children as $key => $value) In the old code the each returns the key & value pairs. The list assigns the key but ignores the value. In your attempted code you were looping through the children and assigning the value to a field called key. Whereas you want the field called key to h...

Just been testing a website updated to CMSMS2.2.16 that was running PHP7.4 which my HostCo end-of-lifes 31/12/22 so been testing it with PHP8 (but only after installing and swapping from various CG modules to instead use SmartForms, CMSMSExt and SMARTYExt) - and the website uses LISE. With PHP8.0 al...

OK narrow issue down the bug to /LISE/lib/class.LISEInstance.php

In the "public function InitializeFrontend()" line 178 the template_detail parameter has been overlooked - I will report a bug via LISE's tracker

After having updated core and all modues to the latest - been keeping an eye on the Admin log to see if an injection attacks are getting deeper in to the system than perhaps they out to ..... by sifting through the HTTP access logs I can see that this is the URL that still triggers the error message...