CMS Made Simple Forums

I have them, but only "by accident" in that I was formerly using whatever the default login template was. I just now specified it explicitly so I would know in the future. I created a new testuser, and the FEU users list shows this one as "Unsafe" as well, same tool tip reason gi...

I did not know anything about csrf. Here's my call: {FrontEndUsers action="login" logintemplate="FEU login form" returnto="parent-home"} I see the {cge_form_csrf} several places in an admin search, including in the FEU login form. Search Templates (5) FEU chsettings for...

Just upgraded to 2.2.10. My one frontend user cannot log in now. I see in FEU Management that the user is marked as "Unsafe" in red. The pop-up "tool tip" warning says this: This users password us using an old hashing mechanism. The user should change the password. (I tried to ty...

Tried it on a different computer. Double checked that I was in binary mode in FileZilla, and it worked. I'll post back if I find out what was going on.

Thanks DIGI3...I don't have command-line access on this host, so I'm not sure if I can do that.

I put the installation php into public_html as I am always accustomed to doing, then I run it from my browser and get this: Fatal error: Uncaught exception 'PharException' with message 'phar "/home/user/public_html/cmsms-2.2.9.1-install.php" SHA1 signature could not be verified: broken sig...

I understand totally where you are coming from, and my mindset is not to argue about it. Summary of the issue: A mail authentication failure caused CMSMS to not be able to complete the login process because I had attached a UDT to the LoginPost event, which UDT tries to send an email. When the email...

Rolf--Thank you very much. That got me in to the admin panel. The AdminLoginNotification UDT and/or interaction with the LoginPost event was unhappy. Bottom line: email authentication was broken somehow to the bluehost smtp server. Once I fixed that problem, then all of this went away. It would be n...

Is there a flag I can pass to login.php to have cmsmadesimple start up in "safe mode" so it won't do anything it doesn't have to do, like email an admin login notification? I know that defeats the purpose of the AdminLoginNotification, but I'm just trying to think of ways to get around thi...

Found something in the error logs: [14-Aug-2018 21:44:04 America/Detroit] PHP Fatal error: Uncaught exception 'phpmailerException' with message 'SMTP Error: Could not authenticate.' in /home1/atwozoom/public_html/aahcdc/lib/phpmailer/class.phpmailer.php:1692 Stack trace: #0 /home1/atwozoom/public_ht...

After successful upgrade to 2.2.8, the frontend of my website works just fine. But now I can't log into the admin panel. I get this: This page isn’t working www.aahcdc.com is currently unable to handle this request. HTTP ERROR 500 This problem has been going on in one form or another since I upgrade...

Similar to https://forum.cmsmadesimple.org/viewtopic.php?f=7&t=77402 Create new cgblog article. Put title, contents, tags, etc. Hit Apply. Nothing appears to happen except that the Apply button is "oranged." Change status to published, hit Apply again. Same thing. No indication either ...

OK, this is weird. Now I could use some help. To get in, I reinstalled = freshened the installation. Then when I opened a new tab and visited sitename.com/admin, it popped me immediately into the admin panel, no password needed. 1. So I logged out. Tried to give the admin and password again, and it ...

The problem re-appeared today, where I can get to the login page, but I cannot get into the CMSMS admin panel. Chrome reports:

This page isn’t working
<sitename.com> is currently unable to handle this request.
HTTP ERROR 500

I upgraded a site from 2.2.6+fresh modules to 2.2.7. Frontend worked, and admin login screen appears, but login to admin panel failed with error 500. Realized I forgot to check PHP version. 2.2.7 requires >= 5.6. I was running 5.4.43. Oops. So, upgraded through cpanel to 5.6.32. Same problem. Then r...

False alarm. Mistake on my part. Somehow accidentally moved .htaccess out of public_html into another folder. Put it back and all is happy. Sorry if I caused some worries over there.