Support

The archive extraction, as documented, renames the .htaccess file to htaccess.bak. This means that your server falls back to its default PHP version which might not have mysqli enabled, hence the notice that there is no database support. As I've said in other tickets last week that page does not look for PDO MySQL. I'll publish a new version which does and is more accurate in that respect.

At the end of the restoration the htaccess.bak file is renamed to .htaccess unless you explicitly tell the restoration script to do something else. If you choose to instead use the default Joomla .htaccess it of course uses the htaccess.txt content we've already discussed why it does not work on OpenLiteSpeed. The default setting, using the htaccess.bak content, has been the same since 2006 when this was called JoomlaPack, Joomla was at version 1.0 and the latest PHP version was 4.4. There has never been a version of Akeeba Backup which put the files in a ZIP archive and creates a SQL export. While you can do that if you really want to it's a stupid way to go about it and makes it very difficult to restore sites across servers. JoomlaPack was written in 2006 to fix those problems coming from just ZIPping files and dumping the db. It was actually the continuation of work I was doing since late 2004 before Joomla 1.0 was released, back when the CMS was still called Mambo. The last time I used a plain old Zip with the files and the DB dump was 18 years ago, probably to the day.

Please ALWAYS specify that you are using OpenLiteSpeed. LiteSpeed is a completely different products which doesn't suck hairy balls.

I am not a spring chicken anymore. Going on 42, feeling like 102 most days :D

OK, let me backtrack and explain the database detection shenanigans.

The first page you see in the restoration script (main page) has the detection for required settings (site can't work without them) and optional requirements (the site will work if they are not met... most of the times, at least). One of these detections is about the database support.

There are two ways for PHP 7 and PHP 8 to support connecting to a MySQL database server (both are PHP extensions which need to be installed and enabled to be supported):

• The MySQLi connector library. This is the older one of the two and the only one which was supported until Joomla 3.4 if I remember correctly. It's also the only one supported in WordPress.
• The PDO library with a MySQL connector (referred to as PDO MySQL). Support for this was added later to Joomla and as I said WordPress does not support it.

Since the main page is common for Joomla and WordPress restorations I had only added detection for MySQLi on that page. If the MySQLi connector is not available (not installed or not enabled) the check appears as a red No.

The next page, the Restore Database page, actually does a better check. It checks for each connector separately and lets you choose which one to use.

So, if you have a Joomla site using the PDO MySQL database connector and your server only supports the PDO MySQL database connector you might see the main page saying Database Support: No. However, the very next page will show you a single option: PDO MySQL. Selecting it lets you restore your site.

I saw that problem last week and have rewritten the installer to now use a common detection code which also takes the CMS you are restoring into account. When you are restoring a Joomla site we check for both MySQLi and PDO MySQL. When you are restoring WordPress we only check for MySQLi (since WP does not support PDO MySQL).

So, for now, just ignore the error in the main page and click on Next.

Regarding the .htaccess file, you have the following options:

• Use the .htaccess file you had included in your backup archive. That's the default and it has always been the last nearly 17 years.
• Use the .htaccess provided by Joomla which as we saw does NOT work on OpenLiteSpeed.

Remember the initial problem you had and how we ended up discussing this in the Joomla issue tracker? Your original backup did use Joomla's default .htaccess file which does not work on OpenLiteSpeed. Therefore after restoration of that older backup you do need to edit the .htaccess file and remove the problematic lines.

If you now take a backup of THIS site, with the fixed .htaccess, and restore it on an OpenLiteSpeed server with the default settings you will not have a problem. Just don't choose the option to replace your .htaccess with the default since you already know OpenLiteSpeed does not work with it.

1. Forget everything I said and keep only this in mind: This is a known cosmetic issue, we will release a new version later this week.

2. No they are not. They are only selectable when there is a reason. Either way, YOU MUST NOT USE THEM. We have discussed the reason ad nauseam in the two tickets here and the Joomla issue.

> PS: Your ticketing system has save at the bottom when composing and at the top when editing .... It would be nice if they were both one or the other :-)

Not really.

When you are composing you are going through a form. It makes sense the last thing to see is the button to post.

When editing, 9 / 10 times you end up not making changes.