Very cool. I tried and got new blank extension created after 3 correction with AI prompt.

Thank you for taking the time to respond and helping out. I will forward your information to our web-hosting IT staff and see if we can get this corrected. I thought for sure I had a screen shot of the errors, but was unable to find them. Anyways that's water over the damn now as we upgraded to 1.4.2 (fresh install) and now adding content into it. BYT Abantecart has really nice front end, and hopefully will get all our products in for the upcoming market season. Again Thank You for your time....

Thank you for the response earlier.

Just following up on this issue regarding the failed upgrade to v1.4.2 due to the DROP INDEX IF EXISTS syntax. As mentioned, our MySQL server version is 8.0.38, which supports this syntax  yet the upgrade still fails with the SQL error referencing:

DROP INDEX IF EXISTS `ab_lang_definition_idx` ON `ab_language_definitions`

1. open phpMyAdmin and run this queries:
create index `ab_lang_definition_idx` on `ab_language_definitions` (language_value(500));


create index `ab_settings_idx` on `ab_settings` (value(500));

2. run upgrade process in admin with key abantecart_upgrade_142

Few things I've come across
Cant seem to find where to approve a product review?
Cant disable transactions view. No point the customer having a transactions list if nothing is entered there automatically by the system, cant find where to add a transaction type either.
They might have bought something but the list stays empty unless I enter it but cant because I cant add a transaction type.
The cart doesn't seem to create an invoice for the customer, just an order. But there is an invoice number in the system (Maybe this is to be manually entered to correlate with an accounting package which is 3rd party?) But cant modify the invoice number.
Transactions is annoying me, cant make it disappear on the customer dashboard.

Hello.
The image error you’re seeing is most likely related to the PHP GD library on your server. Specifically, older versions of GD don’t support WebP format, which can trigger those types of errors even if you’re not directly uploading WebP images yourself—AbanteCart or the browser might be trying to serve them automatically if supported.
The good news is that this is usually an easy fix. I recommend contacting your hosting provider and asking them to make sure the server has an up-to-date version of PHP with full GD and WebP support enabled.

When you say the database was “corrupt,” could you clarify what exactly made you think that? Were there specific errors or behaviors? Often, a proper backup restore should resolve most issues unless the backup itself was incomplete or taken while the database was in an unstable state. If you have any logs or symptoms you noticed before the crash, it might help narrow down the root cause.