PHP Web host changes screwing with the .htaccess file

When we turn on friendly-aliases, it screws with the login abilities of MODx. If friendly URLs are enabled, when you go to save a document, it boots you back to the login screen. With some of the older versions of modx we are unning, it does the opposite, where the front-end only works with friendly-urls and wont let youlogin if friendly-urls are enabled.

Since our webhost has made some changes to its php configuration, all our MODx sites before version 1 are now giving us this unusual error.

Can anyone point me in the right direction with this?

I have not changed the original .htaccess file that comes with the MODx installation.

We also are having issues with a few older MODx versions since our webhost has changed its PHP configuration.
Im not sure which version of MODx we are using because we cant access the manager folder!

When I type in http://www.mydomain.com.au/manager

it returns:

http://www.mydomain.com.au/index.php?q=manager/index.html.var

All of these sites were working fine no changes have been made to the .htaccess file...

Anyone recognize what the problem could be?

OK I have another update... one client’s website was booting them out of the manager area. They had an empty .htaccess file in the public_html folder. So it seems the presence of a .htaccess file, regardless of what is inside it, is playing up with php sessions/ modx login area. Anyone experienced anything like this?

Definitely haven’t seen anything like that before. I would suggest discussing this with your host to find out what changes they have made that altered the way your sites worked.

Thanks for the reply, it seems like there was conflict with having a custom php.ini file and a .htaccess file in the same directory? I’m not sure why but after they upgraded for security purposes they both couldnt be present. Im pretty new to all this Im not sure if that is a newbie mistake or not? After I ditched the custom php.ini files the sites worked fine.