Upgrade and Migration

Trying to successfully migrate, once Database was changed, all sermons, and speakers showed up. I noticed there were no Category's and attempted to add one, and change each sermon individually. (since no sermon showed on front end) But when attempting to save (even with no change) recieved the following:

Save failed with the following error: SermonspeakerTableSermon: :store failed
Unknown column 'modified' in 'field list'...

Checked database, and it seemed alright, is there possibly a missing column?

Yep, it looks like the database field "modified" is missing.

How exactly did you migrate SermonSpeaker? It's crucial that you do exactly the steps described in the FAQ and forum, otherwise you may end up with incomplete databases. You probably didn't use SermonSpeaker 4.0 but a newer release. Quoting the first sentence from the FAQ entry:

Migration is supported from SermonSpeaker 3.4.2 and higher to SermonSpeaker 4.0. While newer versions may work, it's not tested. It's recommended to upgrade to SermonSpeaker 4.0 and if it was successful use the Joomla updater to get the latest release of SermonSpeaker.

There is indeed a bug in the migrate script in newer releases. I will fix that. But that's why I strongly recommend to use SermonSpeaker 4.0, because this is tested

Thanks for that, but I had errors when I did the upgrade the first time to only 4.0, so I used the latest this time. I have no isuues adding sermons, so I will manually add them all back in, but is there possibly an easy fix?
Probably not.

Usually the errors are there for a reason

You can have a look at /administrator/components/com_sermonspeaker/sql/updates/mysql. In this folder you have SQL commands for each SermonSpeaker update. Normally Joomla will apply the needed ones on an update.
You need to check each file and apply the commands on your database, using phpMyAdmin or a similar tool. In the files, the tables are noted with a prefix like this "#__", you need to adjust this to the prefix you use in your tables.

If I installed Ver 4.4.11 should I apply all 4.4x.sql?

You can start with 4.4.3. The ones before should already be done by the migrate script.