Hi there,

I've just updated the version of Amelia from version 5.2 to version 5.4. After the update, the booking form kept showing the load icon. I'm using "Booking forms 1.0".

Best regards,

I can confirm that this happened to me too. 

I have since gone back to 5.3

This has happened to me to. Where do you get the old versions of the plugin? I'd like to go back to 5.3 asap.

I do backups every 50 minutes so I was able to revert to my backup. I did not need an older version of the plugin. Was not able to find anything online thats trustworthy :/

Darn it. I didn't notice it in time, and I have a subscription service on the site so can't rollback to yesterday without potential other issues. I'll just have to take my booking page offline until Amelia support comes back to me.

As far as know, TMS isn't having any way to roll back to a certain plugin version, or download an older version. I've backed up the plugins before updating them so I was able to roll back.

First thing would of course be to make a backup, but it would really be nice if TMS would make a plug-in rollback possible, or to download the older version of a plug-in.

Yeah I made the mistake of not checking the events page right after updating, and didn't notice until the next day.

Thankfully, I found I had 5.2 installed on the staging site, so used those files. Events are back up now and I still have a ticket open, waiting on support. 

Hello Uroš,

Thanks for your reply. I'm sorry but that won't be a possibility for me. That would mean I have to update the plug-in on the live website which will prevent any customers from booking their appointments and possibly other things too.

If there's anything else i can help, i'll gladly help out, but this won't be an option.

Best regards,

Happens to me everytime there is an update too. This is ridiculous that we have to go through this every time there is an update.

How did you solve Georgi's issue? Can you share here so that others can learn from the solution?

Yes it would be great if solution steps are shared.

Hello,

Thanks for getting back to us, has this issue been marked to be fixed in the 5.5 update?

Thanks,

Najib.

Hello Uroš,

As this seems to be an issue that multiple people are experiencing, it looks like this is a generic issue. Currently the website is using Amelia v5.2 and is working fine, i'll wait till a new version has been released that'll fix this issue. If the issue persists i dont mind taking further action to solve the issue, but for now i'd say lets wait till a fix has been deployed in an upcoming version.

Thanks for the support and quick replies, Uroš!

Thank you. When can we expect the next update with this fix to be released?

Good day,

I noticed 5.4.1 has been released. Has the Employee description issue been fixed in that update?

Thanks.

Hello, 

Just got around to doing this. The new update does not resolve this issue. One still has to go back and alter the table.

Commands to do so from CLI are.

Connect to db:
mysql -u root -p'PASSWORD'
use WORDPRESS;
ALTER TABLE wp_amelia_users ROW_FORMAT=DYNAMIC;
ALTER TABLE wp_amelia_users
ADD description TEXT
AFTER note;

Ive tried these and they do work on bringing back up the plugin. I do how ever would like to get these commands confirmed by a developer please. Would it be wise to connect in as root?

Let me know!

Thanks,

Najib.

That’s fair,  are the commands them selves proper for the db change?

Thank you for your input! 

Hopefully others can benefit from our docs :)

Oddly, I reverted back when I had asked to confirm the commands. Updating to from 5.4 to 5.6 and doing it today with my original commands it would not work. I then reverted back and tried again with your suggested command and it was the same issue. 

I have noticed the following error after updating and running the db fix. 

This is how my table looks like after making the changes.

Ive reverted back to a working backup in the meantime.

Let me know what the suggested actions are.

Hi everyone,

I was hoping that the newer versions of Amelia would fix the issue, but that wasn't the case. Not very familiair with databases, but i managed to get the changes done after following the steps mentioned by Miloš; that worked!

Thanks a lot for the support and description on how to update the database.

Enjoy the coming days!

I finally attempted the update again, (had to because the notification short code bugs that were fixed in one of the updates were causing me issues).

In the attempt, the same thing happened and my events disappeared just like before. So I followed these instructions on manually adding a column. I am comfortable editing databases so this did not really worry me, but it wasn't as straightforward as I had hoped. I got a few errors and I'll explain here in hopes to help understand why some are having the issues and not everyone.

First of all, I am hosted with Cloudways.

When I attempted to add the column, I got this error:
Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs 10:08:15 SQL command

I contacted Cloudways support and they had to add this to the server configuration:

innodb_log_file_size = 512M
innodb_strict_mode = 0

I attempted to add the column again. This time it was successful, but I got this warning:

Warning 139 Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

Even with the warning, the site did seem to be fixed and my events loaded. I gave the error to Cloudways support and then they added this server settings to get rid of the warning message, so it can use ROW_FORMAT=DYNAMIC

nnodb_file_format = barracuda

I asked support if there was anything else I should do at this point since I already altered the table, and they said I would need to check with the plugin developer.

So, with this information:

1. Do I need to make any further changes to my database table/column?
2. I hope you can use this information and error data to further troubleshoot the upgrade issues I, and others, had during this update. Hopefully this helps others.

UPDATE. I just tried to update WP Amelia on another site, and this time the new column "description" was added to the table during the update, however it was added at the end instead of immediately after the column "note". 

I edited the table and moved the column up to be after "note". Do you know why this would happen, and how important is it that "description" immediately follow "note" in the database table?

@Traci 

Interesting! Im glad you got your to work out! Would you have the commands(Just to compare) that you used when adding to the database or did you use a UI?

opening a separate issue

Najib, I used a UI in the Cloudways Database manager

I have given that command a shot multiple times with no luck. Just tried it on the 6.0 update and still no luck.

Sorry for the delay. Had some time off in the holidays.

It seems this has not worked for me. It appeared to work on the site I have using events, but  my other site using appointments broke. Huge blocks of time(in the middle of the day) are now unavailable for admin making appointments (probably customers too).

I updated to latest version at the time (5.6) and in my new ticket, support is very unhelpful, since the now latest version is 6.1. https://tmsplugins.ticksy.com/ticket/3197758

Anyway, I have rolled back to 5.2, since that is the only version I have to rollback to, and Amelia doesn't offer past versions to help with this. Atleast 5.2 is allowing me to enter my appointments again.

My guess is that more columns were meant to be added between 5.2 and 5.6 and didn't get added or didn't get added correctly. I have no way of knowing.

So, just updating this post here in case anyone else has this issue. I want them to know that the problem is not solved with updates and updates seem to be getting worse. I am now going through and further testing my other site which uses events. Its currently on 5.2 and I need to track down any issues there.