In the coming weeks.™
I'm sure that this will happen during the upgrade--other than maybe once or twice over the past 13 years, I might have had to manually do something to the database. As long as your database login has privileges to ALTER tables, you should not have to touch it.More InnoDB tables (hope I'll figure out how to convert the tables that will need converting... and that they will not be as stubborn as Christians ).
I'm sure that this will happen during the upgrade--other than maybe once or twice over the past 13 years, I might have had to manually do something to the database. As long as your database login has privileges to ALTER tables, you should not have to touch it.
Starting with XenForo 2.3 we are automatically converting most of the remaining tables to use InnoDB and for new installs we are making all tables use InnoDB by default.
The only table that requires manually converting is the xf_search_index table. For existing installations, due to differences in the full-text search implementation, you will need to run a CLI command named xf:convert-search-innodb, which will empty, convert and optionally rebuild the search index for you.
3.0 will be a breaking change, many (maybe even most) 2.X Add-ons will not be compatible.Is the Xenforo 3 compatible with add-ons that have recently been purchased from various suppliers in the forum?
This would only happen if you upgrade from 2.X on day one to 3.0 the next day.Or is it the case that these will no longer run from one day to the next?
Not to the same extend IMHO. I don't have any stats to back up my thoughts (I would have to analyse a statistically relevant number of Add-ons), but I think there are far fewer Add-ons that directly touch jQuery than those that use templates.It's my understanding that 2.3 will too in practice because of the removal of jQuery.
To a surface extent, yes. However, the fix for most would be as simple as addingIt's my understanding that 2.3 will too in practice because of the removal of jQuery.
<script src="jquery-3.7.1.min.js"></script>to the head of
PAGE_CONTAINER. Heck someone can make an addon that does just that as a temporary measure so that everyone can one click it. (If someone does make that addon, then you can download jquery and do it as self hosted again.)
My point was mostly that less popular add-ons might not get updated to support 2.3 immediately and I would need to get used to managing things without them. Nothing new for a 19-year-old community. Just some inconvenience. I mean the add-ons might still be compatible as long as jQuery is added manually or something like that!