Support

Akeeba Backup for Joomla!

#8977 Front end users can not log in after backup

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by user43506 on Wednesday, 03 August 2011 09:56 CDT

user43506
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 1.5.22
PHP version: 5.2.12
MySQL version: 4.1.14
Host: Yahoo
Akeeba Backup version: 3.3.1

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

Description of my issue:

I restored my site using an Akeeba Backup. I can log into the backend but no users can log into the front end.

I can create new users in the backend but the newly created users can't log in. When I try to log in as a user it just takes me back to the page as if I didn't log in. I have used multiple browsers and reset the browsers. You also can not create a new user from the front end.

The site is http://www.countryplacesinc.com if that helps.

Thanks,
Andy

nicholas
Akeeba Staff
Manager
Please give me the following information by means of a Personal Message so that I can help you:

- A link back to this post so that I can remember what the issue is
- URL to your site
- Super Administrator username and password

This will allow me to figure out what is going on and solve it. Thank you in advance!

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

nicholas
Akeeba Staff
Manager
Thank you for your PM!

This issue seems to be specific to this particular server and site combination. After careful inspection, everything that should be restored is restored. The only thing I observe is that this particular server screws up the URLs. I think that this may be the root cause of this issue. Sorry, I can't help with that. It's not a problem caused by Akeeba Backup and, therefore, outside the scope of the support I can provide through this forum.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user43506
Thanks for looking into it.

Does this mean that Akeeba backup may not be compatible with yahoo site hosting? I used Akeeba to move my site from localhost to the server in a test directory and then to move the site from the test directory to the root location and everything has been working.

The login function worked fine before the install from the backup. Any suggestions of what to do? Or where to look... I'm having no luck finding anyone else who has had a similar problem.

Thanks,
Andy

nicholas
Akeeba Staff
Manager
Since the restored site in the subdirectory worked, the problem can't be with Akeeba Backup. In fact, as I said in my reply above, the problem is how the server is parsing the URLs. When you try to submit the login form, you will observe that there are two question marks in the action URL of the form. I could replicate this issue even by turning off the SEF URLs and deactivating sh404SEF's plugins (so that I'm sure it's not a sh404SEF issue). This means that the server is returning the current URL in such a way that Joomla! can not parse it correctly, causing this issue.

Based on the fact that the login to the administrator subdirectory worked and that logins did work when you had restored your site in a subdirectory, I can only assume that this issue occurs only for the root directory. One solution would be to place the whole site in a subdirectory and use either a "splash page" index.html file on the site's root, or a .htaccess on the site's root to redirect visitors to the main site inside the subdirectory.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user43506
Thanks for all of your help! I figured out what it was. There was "whitespace" on one line of my index.php file. I had redirected the page to troubleshoot a problem and when I deleted the redirect I left a blank line. It only seemed to effect the front end user log in so I didn't notice it when it happened.

I hope this info helps if you ever run into a similar problem.
Thanks again!
Andy

nicholas
Akeeba Staff
Manager
Ah, that explains it! The whitespace caused the PHP headers to be sent before Joomla! had a chance to set the cookie, killing the login.

Out of curiosity, how did that whitespace end up there? Did you modify Joomla!'s core files?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user43506
I edited the index.php file manually to test something for another problem we were having. When I deleted the portion that I changed I must have left a blank line. I found the problem by looking at the Joomla log files and Googling the error it was throwing.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!