Amelia totally not working on multiple fresh installs.

Hi there.

This sounds quite strange. We just installed the lite version on a fresh website, and it worked fine.

These issues are hard to troubleshoot without having any insight into the site that’s facing the issue, but can you please check your error log and see if there are any errors in there?

Also, if you have access to your database, navigate to the wp_options table (wp_ is the default prefix, but in your case, it could be anything, so look for your_prefix_options). In there, search for “amelia_settings” in the “option_name” column. That returns one row, so edit that row, and use CTRL+F to find “pdoBigSelect”. Change it from false to true, save the table, purge all cache from your website and try again.

Let us know if that helps or not.

• This reply was modified 2 years, 4 months ago by ameliabooking.

Hello there,
Thanks for your response. It so happens that the problem might have been with the software Local by Flywheel environment that has been causing this issue. I had to do fresh installs on XAMP and everything is working fine. So that issue is cleared.
But another warning arises when get to customize the appearance of my theme. There is a warning that shows up before the customizer window is fully opened; Warning: Cannot modify header information – headers already sent by (output started at C:\xamp\htdocs\my_site_name\wp-content\plugins\ameliabooking\src\infrastructure\WP\HelperService\HelperService.php:40) in C:\xamp\htdocs\my_site_name\wp-admin\customize.php on line 126.
The solutions i googled up for such a warning have not yielded any results. But the plugin is working fine. Just wondering if it cannot cause some errors in the future.

Kind regards.

Hello again and sorry for the late response.

That’s just a warning about provision headers sent by another plugin and it shouldn’t cause any issues with the plugin (or your site).

Our developers are aware that this happens on some installations, and they’ll work on it in the future, so hopefully, this warning will be removed with one of our future updates.

At the moment, you can disable debugging in wp-config.php file, and the warning will be gone. Debugging mode should be enabled only when you’re actually debugging some issues on the site, and warnings like this aren’t dangerous.

Kind regards.