sobrenome

Hi,
Just following up on this:
I noticed here:
@Stuart Silvesternotes that this community is using Open Search.
What version :D?

I haven't tested with 2.x or newer, OpenSearch & Elastic Search release updates very quickly, often (previously) with breaking changes.

Thanks for the updates :).

Is there any chance you've tested with any higher versions?
Our current test version attempt worked fine with 1.3.4, and it rebuilt all the indexes, but we can't seem to get 2.0.0 to work even though others in that topic mention that it should work just fine.

I believe we're using 1.2, which is the latest version AWS OpenSearch Service supports.

Ask your host if "mod security" (modsec) is in use.
If it is, have them check the logs to see if it intercepted/blocked some Admin Panel URL's which tried to save the Templates, then adjust the ruleset for modsec to allow the blocked URL's.
Does that help?

Ask your host if they’re using suhosin or any WAF ( web application firewall) .
 
most of the time it’s either a WAF which is blocking the request because a security rule was trigger or suhosin blocking huge requests like when editing a template.

I'm trying to edit a template in one of my custom databases for the record display. I've done this numerous times in the past without issue, but now today I am getting this error when trying to save my changes. Not sure why this is. 
I recently migrated to a new server but I don't think this would affect it, would it? 

If the site is hosted by IPS (meaning it's on the IPS cloud), Cloudfront is already setup by IPS and there is nothing you need to do.  It literally is already done.
If you're self-hosted, rather than do Cloudfront, I would suggest looking at Cloudflare.  You'll find it a MUCH MUCH easier integration.  Otherwise you're going to have to do a BUNCH of work, including potentially needing to setup SSL certificates, defending S3 buckets, configuring what content should be stored on S3, etc.  That's even before you get to the Cloudfront setup and figuring out your CORS settings and how long each type of content should be cached for.  
If you need a CDN, integration of Cloudflare will be a 1000% easier.  (Note...  anything custom you do such as adding a CDN, be it Cloudfront or Cloudflare is not officially supported by IPS.  So you might need to disable it for troubleshooting problems you might have as IPS does not troubleshoot your custom configurations.)

There are a LOT of settings that would depend on your site.  Why don't we start with what don't you understand about it?  

Scope perhaps for a new offering? I've always thought downloads was too restrictive. If it was expanded to include services then perhaps one of the many experienced pros on here could offer service and maintenance contracts, which might incorporate initial setup of Cloudfront, Cloudflare, Caching, S3 etc. I appreciate these services can be requested elsewhere, but nothing quite like seeing them as a confidence inspiring, formal, client rated, offering.
edit: added confidence inspiring.

There must a guide out there for ipb and cloudfront.

Are there any guides on how to setup cloudfront?
I found the s3 setup guide and everything worked out fine, but I can't find a guide for cloudfront. 
Thank you.

Would it not be setup like any other CDN?

System > Files > Storage Settings > Configuration

Cloudfront is a CDN (meaning serving content from multiple locations around the world to have static content such as images and stylesheets closer to the end user).  S3 is actual file storage.  
Regarding Cloudfront, if you're using IPS hosting...  it's already using Cloudfront.  If you are self-hosted, it's more involved.  You need to setup an S3 bucket to store those static files, and get it configured...  then configure Cloudfront to use that S3 bucket as the origin.  
Even once you have CF setup, you need to evaluate your caching settings to figure out what should be cached and for how long, especially if you're going to use the CDN to serve theme files which get regenerated frequently.  (You don't want Cloudfront serving an old version of the JS files for example from cache when your board is expecting a different/changed version.)

🤓

Yeah, if a spammer gets through and somehow posts a spammy link and then it sends out a "there's been a post in this thread" update to a bunch of people, it will set off alarm bells at SendGrid and the other competitors. 
But its even good because admin e-mails saying "A guest has posted something that needs approval" still get routed through SendGrid and if there is a spammy link in that, SendGrid will still flag you. Imagine if you have 5 admins that all get the same e-mail. 
That's why I like your plug-in and wished to keep it. 

Is this notification a new feature in 4.7?

Sorry Matt but that's simply just not possible with CIC clients. 👀
 
And as Adriano mentioned just above, sometimes they don't even provide FTP access. So yeah, it might be a "dangerous" feature, but it really helped when debugging things without having to waste time getting the proper FTP/phpMyAdmin access.
I would very much prefer you guys slap a big fat error message (or something similar) above it so normal users are scared of using it rather than removing it altogether...

We removed it because it's a really dangerous feature that really doesn't belong in a modern community platform. If you want a light weight SQL tool (which is way more comprehensive and feature-rich than our simple tool) then definitely check out Adminer. It's a single PHP file.

I use this when working with self hosted clients. It takes seconds to upload and log into. Just remember to remove it when you're done.
No need, just upload the single 450kb Adminer file and log in using the conf_global details. It's what I do. 🙂 

I completely failed to notice that line about the SQL Toolbox. I use it a lot on clients' sites to check data. They often give me no phpMyAdmin (or similar) access, either because they don't want to or simple because they don't know how.
Do I have to make my own custom SQL Toolbox app so I can temporarily install it and get things done now...? 🙄

Ya I had no problems, ran like that for months. I wasn’t using CRON entries though, just the default with user activity. But I switched back to 8.0 weeks ago. I did not run any addons (if that makes a difference). When they announce official  support I will switch back to 8.1.

Note - This caught me out. I had left my nginx configurations to php7.4, but forgot to force php-cli to be on 7.4, you can do so easily by doing:
update-alternatives --set php /usr/bin/php7.4 @nodle are you sure your background tasks are working on php8.1?

There are portions of the codebase that doesn't get utilized by the average site owner. There could be certain settings that get enabled that utilize a section of code that might not play well with new PHP releases. It's in the realm of possibility that one site might not encounter any compatibility issues. 
One site claiming that all is well in the world doesn't necessarily mean that everyone's world will be peachy.  It's quite possible that there might be problems yet to be discovered.
Although some folks step us to beta test each build its pretty much a free for all. People will randomly test things likely leaving portions of the suite untested.  
With "some" structure thrown around client beta testing a larger amount of the code could be tested minimizing the amount of follow up releases needed to be fully compatible with each new PHP release. 
Helping marketplace developers better address future PHP releases would be a worthy conversation to have between IPS and the community.
 
 
 
 
 

The other thing to remember is that while Invision may support 8.0/8.1.x, this isn't necessarily true for third-party developers, who are of varying aptitude.  I just installed PHP 8.0.x on my development site, which dies with an error 500 unless I disable my third-party customizations (which means that one of them isn't coding properly somewhere for PHP 8.x).  And I don't currently have time to troubleshoot.  So there's support, and then there's support.