Support

 Hello,

I backup my site from live server and restore on my local machine for testing purpose. The restoration on my local machine went well. I can view front-end site and work on back-end. One issue that I found so far is I have a search module, when I type keyword and click search, I received error said "could not find driver ".
Did I miss something during the restoration?
Thank you,
M

Please check the setup on the actual search module, does it include a fixed path? That would be a reason you would get a "can't find" error. It used to be a pretty common thing, but we don't see it as much now.

The second suggestion is to clear your browser cache. It may be picking up settings from the live site.

Thank you for your suggestion.

The search module just link to a menu and it link to index.php?option=com_search&view=search, so I do not think it is a fix path.

I clear my browser cache, but I am still get an error when I search. We have an assumption that the restoration process did not pick up the path correctly and it might cause this issue.

What is proper process to perform a Joomla Migration vs a Joomla Restoration with AkeebaBackup and using AkeebaKickstart tool. We would like to set up a copy of our current site backup on a different server/environment with different paths than Joomla’s backed up directories. We have tried to restore the backup using the tool, and encounter behavior which suggests that the paths/rewrite rules/configuration changes restored from the backup into this new environment with the Akeeba config modifications are not working correctly. Some paths update, others do not.

Please advise.

Thank you,

M

You would need to rebuild the data for Joomla!'s built-in full text search. Those tables are generally very large and of limited use when restored so they are skipped by default in the backup. But the "missing driver" message doesn't make any sense in that context.

If you are using Admin Tools' .htaccess Maker, you always need to change the urls at the bottom of the settings page and regenerate your .htaccess file.

Beyond that I really can't think of any hard and fast rules for things that you have to change for a migration. You need to manually create the new database, the installer can only restore data, it can't create the database. There are many things that can go wrong, but they depend on server setup, url, php version and about a million other factors. There is a post-restoration troubleshooter page here: https://www.akeebabackup.com/documentation/troubleshooter/post-restoration.html.

Two things that can affect paths are the $live_site variable in the configuration.php file. Joomla! usually picks up this properly on its own, but you need to set the site path when it doesn't. The home page is usually "scrambled" and you get 404 errors on other pages when you need to set the variable. Another thing to watch is the RewriteBase setting in .htaccess, but that is usually not used.