To add a bit more to what @MeMaBlue said: after she upgraded the plugin from ACP to version 2.0.6 (that's the version that shows up in ACP at least) she was unable to login on both admin and frontend sides.
The error I received when trying myself was this:
Table parentsorgips.dp4custombadwords_settings doesn't exist
For now I disabled the plugin and the forum works again. But I double-checked the database and there is indeed no such table. Not sure what went wrong or where though. 🙄
Depending on what you're trying to do there might be some kind of possible workaround using plugins. 🤔
I can't be sure without knowing what exactly you're trying to accomplish doing those edits though.
@Gary The database checker usually detects that kind of thing but it looks like there's some specific code in place to specifically skip INT/MEDIUMINT columns that should be BIGINT. Other people will surely run into the same issue at some point. Maybe you could bring it up with the developers?
See file /system/Application/Application.php on line 2846:
/* If the only difference is MEDIUMIT or INT should be BIGINT UNSIGNED - that's where we changed the member ID column. We don't need to flag it */
[...]
The feature doesn't work by giving the user a choice. It shows an empty text field and the user has to enter the answer manually.
The answers you're setting up in that screenshot will ALL be considered correct.
Guide link:
Most likely you've reached the MAXIMUM VALUE of the data type used for the member_id column in the ipb__core_pfields_content table.
The current default value is BIGINT(20) but in the past it had a lower limit. The column was not updated properly in one of the upgrade steps probably.
@Salvatore Torsi That's indeed a hosting issue on their side instead. I encountered it myself once during an upgrade, it was caused by the folder not being properly created when PHP 8 was installed. And on another server I had a similar issue but it was caused by the folder not having the correct write permissions.
Definitely something your host needs to fix though.
You can use the Converter application to merge 2 Invision Community sites: https://invisioncommunity.com/services/convert/
It will merge everything though, not just select members and their topics. A workaround would be to make a copy of the site you want to merge, delete all the members/content you don't want to port over, and then do the merge with only the data left.
I was thinking of an interface similar to the one in ACP with the same option, but simply limited to our files. So yeah, ideally we'd be able to also setup start/end date, number of uses (even per-person), etc.
Is this happening also for other posts? And if you try to quote again the original post does it work?
The image url in the original (working) post is:
https://audiophilestyle.com/uploads/monthly_2022_12/112211978_Screenshot2022-12-10at9_08_46PM.thumb.png.23f5ccfef0ab0ecca75c04acf0aef636.png
The quote instead has a SPAN element (instead of IMG) with a broken image url that contains a strange "cdn-cgi" part:
<span>/cdn-cgi/mirage/00ce431b9027971e05da91937cb72d5b93aaf04ec1a19da6ad7098b83f26925d/1280/https://audiophilestyle.com/uploads/monthly_2022_12/112211978_Screenshot2022-12-10at9_08_46PM.thumb.png.23f5ccfef0ab0ecca75c04acf0aef636.png</span>
Are you using a CDN that caches page and alters the forum output perhaps?
ACP > Community > FORUMS > Settings > Forum Settings TAB > Topic Summary Settings
There are 4 settings in that area where you can change how that summary in the sidebar is generated. By default it shows only after the topic reaches X pages, but there is a checkbox to make it always show which I believe is what you want.
Here's a link to the guide:
The upgrade process shouldn't have any step that asks you to move the uploaded files. What instructions did you follow and where did you find them exactly?
In case you have recently upgraded to PHP 8 double-check that your cronjob is also updated and using the correct PHP version.
Before it wasn't an issue but in the last 4.7.5 update IPS made some changes to the code and some tasks won't run anymore with PHP 7.x cronjobs.
By "old items" Jim meant only the posts made after the last upgrade and before you applied the patch that solved the issue.
Word expansion is executed only when the post is submitted, so only the new (or edited) posts in that short amount of time were affected. That's why it was mentioned that old posts are not affected by the patch.
You can manually edit the affected posts (by removing and re-adding the wrongly expanded words) so word expansion is re-executed on edit.