Nathan Explosion

For reference to others who might read this topic...the code that uploads the zip in the ACP doesn't do any kind of "is this compatible with this version?" checks. If you get the error above, check the contents of the zip - the plugin.js file should always be in the first folder witin the zip. If it's any deeper than that, then you get the error above. If it's not compatible/supported, and definitely doesn't work in the version of CKEditor used by IPS, then your Editor will most likely just break.

The actual cause is not that the plugin isn't compatible, it's that the zip file as downloaded from CKEditor is really badly structured. footnotes_1.1.0_0.zip, contains a folder called footnotes_1.1.0, which then contains another folder called CKEditorFootnotes-1.2.0, which then contains another folder called footnotes, which then contains the actual plugin code. Do the following: Drag the 'footnotes' folder out of the zip file Then zip the footnotes folder (just dragged out) into a ZIP fil of its own Upload away!!

Well, it appears I didn't actually upload v1.6.0 last time, so here it is again as v1.6.1 (currently pending approval) NEW Added ability to perform an email address check against neutrionapi.com (v1.6.0) Tested & compatible with IPS 4.7 FIXES Fixed issue with validation of settings related to netrionapi.com CHANGES None

v2.1.1 is currently pending approval. FIXES Fixed PHP 8 issue in template, which would cause the mention list to not appear correctly CHANGES Removed 'Include banned accounts in list' setting as 'Banned' accounts are no longer included in the list by default by IPS (intention of this setting was to allow you remove 'Banned' accounts from the listing - feature no longer required) NEW Tested & compatible with IPS 4.7

Thanks for providing that access - allowed me to check the response being sent back by the server when you type a name, reveals a HTTP 500 error. Testing locally, and on my live site, and I don't see that - but then I introduced PHP 8.0.19 into the mix, and there it is. I'll get working on a fix and release as soon as I can.

Not seeing any issues in my testing on my live site, will do some further testing later tonight. Via PM, can you send me a link to your site along with a username/password to login as a user? Thanks

Thank you.

I'll test it out - what are your settings currently configured as?

Thanks @Matt - working a treat now with Beta 3

https://invisioncommunity.com/forums/topic/466965-live-view/?do=getNewComment

Official support, by IPS: https://invisioncommunity.com/forums/forum/497-help-support/ Yep, but above link is where they really should be guiding people to.

That's a goer, as long as you don't expect it to be an 'exact' representation of the actual content.

This would be for the Club's 'homepage', using 'Manual HTML' for the Content Editor: {{if \IPS\Request::i()->id == '5'}} Unique content for Club with ID 5 {{elseif \IPS\Request::i()->id == '6'}} Unique content for Club with ID 6 {{endif}} This would be for the Club's topic listing, using 'Manual HTML' for the Content Editor: {{$forum = \IPS\forums\Forum::load(\IPS\Request::i()->id);}} {{$clubId = $forum->club()->id;}} {{if $clubId == '5'}} Unique content for Club with ID 5 {{elseif $clubId == '6'}} Unique content for Club with ID 6 {{endif}} This would be for the Club's topic view, using 'Manual HTML' for the Content Editor: {{$topic = \IPS\forums\Topic::load(\IPS\Request::i()->id);}} {{$clubId = $topic->container()->club()->id;}} {{if $clubId == '5'}} Unique content for Club with ID 5 {{elseif $clubId == '6'}} Unique content for Club with ID 6 {{endif}} Do not enable the 'Cache this block' setting

I'll have a think about it.

Do you have the 'Pages' app? If so, create a custom block (with a custom template) which detects the Club ID and then presents your unique content. Then drag the block in place in Clubs.

Got Pages?

Most likely an update to imagemagick/PHP - have the same myself on my site, just started happening a week ago. Prior to that, no issues - and zero changes from an Invision point of view.

v4.0.1 is currently pending approval This is a big rewrite of the application - since it began life in November 2016 as my first attempt at a plugin, it has turned into a bit of a beast. And this beast needed taming to change how the content was inspected, to simplify adding in additional items to be hidden should it need to be done and also to remove some kludges that were in place to achieve certain things requested over the years. v4.0.1 also includes the following: NEW added ability for audio attachments to be hidden added ability to hide content in Pages database reviews (was already possible with comments) added ability to limit number of Pages database reviews shown when using the 'Hide all content' functionality (was already possible with comments) added ability to hide content in Calendar events/comments/reviews added ability to limit number of Calendar event reviews & comments shown when using the 'Hide all content' functionality content loaded via inline notifications is now processed, and content hidden as configured (see https://invisioncommunity.com/forums/topic/434067-ne-hide-replies-from-guests/?do=findComment&comment=2869307) added ability to suppress the inline 'New replies' notification in topics (if hiding all content & limiting number of replies displayed) added ability to enclose 'Hide all content' message in an "ipsMessage" box CHANGES settings controller name changed to provide uniqueness (note: if administrator restriction has previously been used to restrict access to settings, please revisit to apply restriction again) some minor language string updates removed several redundant language strings FIXES fixed issue with 'Spoiler' account settings impacting ability to hide videos if both spoilers & videos are chosen to be hidden in the content.

Checking my notes from way back when... MariaDB 10.1 was the sweet spot between 3.4.9 & 4.5.x - meaning both versions could run on the SQL server.

Yes.

Spotted the following in the system logs after upgrading my test site: Just run through the same on localhost and this is core_statistics before the upgrade: Post-upgrade, same errors in the system logs:

Yep, it will be added in. Some other stuff came up that I needed to get done but this one is next on my list. Hold off until I release the new version.

Try dropping down to a supported version of PHP - 8.0.x

Oh, interesting - I don't recall the hiding of the groups being tied to the 'default...' setting, so I see the confusion. I'll have a think...