CMS Made Simple Forums

I've just upgrade one of our sites from 1.7.x to 1.8.1 and when any system user tries to login we get the following error:

Fatal error: Call to undefined method Captcha::LoginPost() in /home/user/domains/mydomain.com/public_html/h17ey127eby1278/login.php on line 296

In case you're wondering, "h17ey127eby1278" is the name of our admin folder.

Any ideas? Thanks in advance!

Is that admin folder path specified in config.php?

replytomk3 wrote: Is that admin folder path specified in config.php?

It was! However, following the upgrade it had reset to /admin. Having put it back I'm now getting this error:

Fatal error: Call to undefined method Captcha::LoginPost() in /home/user/domains/mydomain.com/public_html/h17ey127eby1278/login.php on line 186

Thanks a lot for your help!

Did you run checksum verification?

Search this forum and Geegle for that error message "Call to undefined method Captcha::LoginPost()"

Try to reupload the /admin folder contents from installation file.

Did you update from 1.7 to 1.8.1 at once using the diff release?

The problem is that files in the admin dir has been changed.
In the package the admin dir has the default name "admin" (since the devs don't know your admin dir).
But if you renamed your admin dir the update won't have any success because your config.php points to the custom folder (with old files).
This is why the update changes the admin dir in your config.php back to the default value to be able to use the new files.

So when re-uploading the content of the admin dir i would suggest to use the base install package not just the diff.

Thank you very much for the help. The renaming of the admin folder appears to have caused the problem. I'd done a full upgrade from 1.7.x with cmsmadesimple-1.8.1-base.tar.gz. This gave me two admin folders, one named "admin" the other with our funky name.

I fixed the issue by deleting both of the above folders and uploading a new admin folder from the above file. Renaming the newer "admin" folder to our funky name did not fix the issue; in fact it threw lots of Autoloader errors.

It's all working great now.

I believe renaming the admin folder has to also be done in config.php so it knows where to look for it...

Dr.CSS wrote: I believe renaming the admin folder has to also be done in config.php so it knows where to look for it...

Yep, I had actually done that. There were a whole bunch of these Autoloader errors. If I remember next time I do an upgrade I'll force these errors again in case it's something experienced by other users.

My understanding of renamed admin folders is to rename them to admin before upgrading then after you rename it to your choice, works much better...