Database error installing - existing SS on J3.3.6

Okay after some review, all the table fields are there and correct but in a completely different order. Nothing is missing.

So the error must have to do with the fact that the reinstallation/update is looking for fields in a different place in the table structure?

I think everything is working because the underlying code is probably using field names and not the column order of the tables. The only issue now is getting the latest version installed to fix the autotweet issue.

I am going to try and rearrange the columns using sql. If you have any other suggestions that would help.

The order doesn't matter at all.
For some reason the fields just were already present. There must have been a successful update before. For some reason either Joomla didn't update the last file it applied or you downgraded SermonSpeaker someday. I can't imagine anything else.

If everything is working fine now. You can leave it.

For the autotweet bug, can you try the package I posted in sermonspeaker.net/forum/sermonspeaker-5-...ent-update.html#4885 ? Looks like I forgot to release the fix... :unsure:

Yes order is not important.

So apparently there is some tag some where telling the installer to use one of the sql updates incorrectly. The one that is trying to add the new fields and they already exist.

I can't install the patch you linked to because of the sql error. I have to find why it's trying to add new fields that aren't needed.

edit:
It appears to be trying to run the sql 4.5.0 updater incorrectly. Not sure why.

You can try editing the schema information directly in the database. Joomla stores the latest file it applied in the #__schemas table. You need to look up the extension id of SermonSpeaker (com_sermonspeaker) first either in the extension table or Extension Manager.
If you change the version_id for SermonSpeaker in the #__schemas table to 5.0.4, it should not try to apply the SQL files anymore.

At leats in theory that's how it works. I never tried changing directly the value there

Woohooo!!!

Thank you so much for guiding me along! I really appreciate the fast "live" support.

The problem was a mismatched extension ID in the schemas table. Sermon Speakers ID in the extension table didn't match the schemas table for the version!!! A totally easy simple fix and the update worked perfectly!!!

I have no idea how these ID's got messed up. The update from j25 to j3 can be problematic so it might have happened during that process. I was terrified that I was going to have to do a bunch of editing of raw tables that would take a few hours... a bit of research with your help and guidance saved my day!

Thanks again!