Nathan Explosion

Turn off "Post before registering"

@LiamH - just checked your site as a guest; there are several forums open to allow guests to post new topics. I suggest you look at the permissions that the Guest group has for forums: You also have "Post before registering" enabled:

Apply the patch...

OK. But it's likely to be that has happened All registrations go through the spam prevention settings, and depending on your configuration then an admin may need to validate the account.

Probably because your spam prevention settings dictate that a certain level requires admin involvement...

Did you download and install it?

GBoard is the default keyboard of the Google Android OS (it's on Pixel devices, it's on most OnePlus devices, plus others that don't massively deviate from the stock OS) 'Samsung Keyboard' is the native keyboard on the Samsung version of the Google Android OS, but can be overridden by the manual installation of GBoard from Google Play, just like SwiftKey is available for all Android devices.

Scroll down to the footer...it's available by default.

Apply the patch that was released to fix this:

First mention of filtering there, so wasn't aware it was a requirement. If it is then crack on with a Pages DB - you then have to figure out how to keep that data up to date, and when to do it. Alternatively, look at IPS\Helpers\Table\Custom to allow you to create an table based on an array datasource instead of a DB table. With all this in mind, I'd now advise you to look into developing an application to do all this instead... You can design your own table to store the data You can create a module/controller that will display that data, and add filtering on there easily. You can create a task that runs on a schedule to retrieve/store/update the data. Not much more to add really - if I knew what this mysterious API was, and where it was getting the data from, and what the data looked like then I might even get bored and throw together a POC of it.

The count, yes. The user's choice, no.

Deleted - can't be bothered with potential further engagement

Zero knowledge of what API it is that you are referring to wanting to use so can't look at the data structure, and have no idea about how you want it to be displayed but here is what I would be doing on the page/block... Check if the data exists in \IPS\Data\Store If not, retrieve the data via the API and then store the data in \IPS\Data\Store::i()->whateveryourkeyisgoingtobe, adding something to the data to provide a timestamp for it being added. Display the data however it is you wish it to be done. On subsequent loads, step 1 should also be checking if that timestamp should be considered 'out of date' - if it is, get the data again. I don't think you should think about storing the data in a Page DB - I can envision that become overly complex for what it appears that you are trying to do. And if the data store gets cleared, your code would just pull in the data again into the store anyway.

PHYSICAL products are being deprecated.

Reproduced as follows; Create a brand new theme Download the theme using the option in the console Edit the theme, populate the header and footer bits via the available tab. Review site on front-end, verify items are there. Use the "Upload a new version" option on the theme, and use the XML file that was downloaded in step 2 Edit the theme - the previously added header/footer content is gone Review site on front-end, the previously added header/footer content may still be there in the theme. If so... Run support tool to clear caches Review site on front-end, the previously added header/footer content are now gone.

They will not be able to use tags/prefixes.

Disable others ability to use tags then. Group level permissions... Set them to Off for all groups except your own, then you're the only one that can create tags in your open system.

Nope. https://www.sosinvision.com.br/index.php?/file/38-copy-topic/

That isn't obfuscation. That is an ipV6 address

specific email addresses? Understood...you've probably created a number of SQL queries then (1 per email address) and not just using one catch-all query. But for the benefit of those reading at a later point - if wanting to do this for a specific email domain then can be done via the above method:

What are the criteria that you are using at the query level to select those members? Note: I'm more interested in here in showing someone that the query above isn't needed, just in case someone arrives at this topic at a later point.

If that provided SQL query definitely is meeting your needs then you could have just done the following on the members listing in the ACP... On the resulting dialog, change "Group" from '-Any Group-' to the name of the group that people are in - then click the 'Search' button. Then click the link... Thus saving you many hours...

Got Pages? In the ACP, do the following (specifics included only...if it's not specifically mentioned, it's up to you what you set things as) Go to Pages -> (Page Management) Blocks Click "Create New Block" Change "Plugin" to "Upcoming Events" Click 'Next' Name it & add a description Go to the 'Content' tab Change "Use this tempate as-is" to "Use as a base for a custom template" Find the following: {{foreach $events as $event}} Add this below it: {{if $event->online}} Scroll down to find: {{endforeach}} Add this above it: {{endif}} Save Go to Pages -> (Page Management) Pages Click "Add Page" Click "Next" Name it, give it a filename Click "Save" Give permissions On the resulting listing of Pages, click the "Open page builder" Use the block manager to drag your new block into place on the page. There's your online events page.