Support

hello,

I'd like to know if the ATP component might have something to do with unexpected problems when restoring a backup file (taken with Akeeba Backup of course).

A couple of months ago I restored my site very easily. Now I just can't get it right; the ATP 2.0 component is the main difference between then and now.

At last I finally restored a very poor version of my site. So I deleted the .htaccess file and another file, think it was called Admin Tools.htaccess or something like that. With that, the frontend and the backend came out as they should.

Backend seemed to work fine, but in Frontend all links to the the rest of the site (sections, categories, articles) were broken. Their behavior was like this:
site: www.new_site.com
link: www.old_site.com/section/blablabla...

Of course, they produced a 500 Internal Server Error.

So I made a new .htaccess file and now some of the links work, but not all of them...

I will attempt a new restoration, but before I go with that, please tell me if ATP can interfere with the restoration procedure at some point, and if there's anything I can do to prevent it.

Thanks a lot for the great support.

Hi, Nicholas, just a line to thank you for your reply. All is fine now.
Regards

Nicholas,

Sorry to come back with this subject.

Once again I tried to restore my site (just cloning it to see if it restored fine), and run again exactly into the same problem; that's why I'm taking back this thread.

The problem is that some articles' links work OK in the restored site; they show the new site's url, just like it should be.
But some articles don't. Their links keep the original site's url, so I get this:

"Forbidden
You don't have permission to access ( /section/category.html ) on this server.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."
------

To solve this problem, I did what you told me before:

1. Restore your site normally
2. Remove your .htaccess file from your site's root
3. Log in to your site's administrator back-end and go to Components, Admin Tools, .htaccess Maker
4. Expand the "System configuration" slider and edit the two "Host name for HTTPS requests" fields to read your new site location.
5. Click on "Save and create .htaccess" and you're set.

But it didn't work.

The only thing I think might be wrong with my restoring process, is at the beginning, when you have the default location of directories Temporary, Logs, and Cache. In my case, both Temporary and Logs directories got a red "NO". Should I make them writeable at the original site? With 775 permissions, or 777?

Or is it something related to the .htaccess file?

All seem to work fine in this cloned site, except some articles' links.

---------
At this point I'm not sure if this is an ATPro topic, or if I should start a new thread in the AkeebaBackup forum; please let me know.

Thanks for your advice.

Xpard,

Under no circumstances should you ever have to set folder permissions to 777. You should steer clear of anything which requests such things. In fact if you have changed folders to 777, depending on your server config can cause server 500 errors. Be warned that anything which requires such permissions should be avoided at all costs. Otherwise unless you know exactly what your doing server wise (their are situtations however not recommended for many) you pretty much asking for trouble.

Make sure when you rewrite the new htaccess file everything under system configuration is correct, including the root directory. Also make sure in configuration.php you change the live site variable to reflect the new domain. exactly as http:// (no trailing / at end)

Are you running a SEF url component, such as SH404 or similar? If so, that will almost definately be an issue. You will need to purge ALL url's using that component.

Let us know how you go.

Just adding to the permissions thing, folders should NEVER EVER be set above 755 and files 644. Full Stop. This means any and all folders, temp, logs, cache etc. In fact if you want to go the extra mile, change to temp and logs folder to another name, eveyone knows the standard joomla ones.

Truth be told on a 110% perfect system, it would hardly matter. That setup is rather complicated and not really something to be discussed here. Certainly not something suitable to a shared host or someone who is not a gury on server linux setups.

A educated guess, i would say 99% of hacked sites are through, poor file permissions practices.

Nicholas and Slaes,

Thanks very much for your help, all of what you both said was good information.

I tried the SEO and Link Tools and, just like Nicholas said, the problem was gone.

I'm still kind of newbie at Joomla, but have already tried many extensions --some of them really good extensions-- and don't know yet a single one that can compare to Akeeba's products. Plus, the quality of your support is great, especially for beginners like myself.

I will donate a few Euros in the coming days or will try to upgrade my subscription. I guess you Nicholas are the kind of person that doesn't think of money as the number one goal in life, but there's no doubt you deserve to earn lots of it.

Regards,