Update: we had another post show up and that one displays the spam phrase as expected. The one that does not was actually unapproved prior to the XF2.2 update.
Prior to updating to 2.2, posts which were automatically unapproved for including a spam phrase would show this as the reason when viewing the content in the approval queue. After updating this no longer shows, so unless you happen to know what phrases are in the spam phrase list you won't...
If you do the steps I had above it should fix it for you, @tajhay. I would also recommend looking at your server config, since I think it's something with how MySQL, Apache, or PHP is configured that causes it to happen. We made a number of performance changes to all three so I don't know...
I was able to fix it by doing the following:
Close the forum
Export the database sans the xf_template_phrase table with this:
mysqldump -v --single-transaction --quick --default-character-set=utf8mb4 --ignore-table=database_name.xf_template_phrase database_name >...
It seems like the TABLESPACE for the table still exists, so you can't create the table again. MariaDB doesn't support dropping a tablespace so you're stuck.
In my case I made some MySQL/MariaDB config changes to /etc/my.cnf, nuked the db, imported our XF1.x import and upgraded again - no more error like before. This is just a guess, but I think our innodb_buffer_pool_size was too small for the size of the table. It's that or it was a timeout issue...
MySQL version5.5.5 (10.2.20-MariaDB), which is interesting since I thought MariaDB was based on the newest version of MySQL. During my furious Google searching of the last day or so I read there was a bug in pre 5.6 versions of MySQL that could cause that issue with a table being stuck in use...
Media Gallery, yes. I did a fresh install again using the same DB export and so far haven't got this to happen. The only add-on I didn't install this time around was "[Widget] Popular threads and posts 1.1.2". Steps from this most recent test:
Create new db
Import db export via shell
Upgrade...
This isn't our live install, fortunately. We purchased a new server so I'm doing test imports on the new server with the same .sql export I used on our current staging server and locally on my own machine. I figure something must be getting borked during the import or because of the new server...
Did you find out anything more about this, @DoogiePC ? I am seeing this happen on a new server when doing a test install and upgrade to XF 2.0. Interestingly, I did the except same upgrade on a test install on our old server and a local docker setup and this never happened with either of those...