Chris027

I will test it in a couple of hours just in case. Will reply back. 👍

This user still has the same issue when the plug-in is disabled. 

I would love to be able to dismiss the "important issues" on the support page because they aren't important to me. For example, I've been using Cloudflare for years and I absolutely love it. But, IPS flags this use an an "important issue." I understand Cloudflare may cause issues for some people, but flagging it for everyone, without the ability to dismiss it, is problematic. The more we see issues flagged that aren't issues, we end to ignore what may be a real issue. 

Thanks for reporting this! We will investigate the issue and if a fix is required, one will be made in a future maintenance release. Thanks again!

This app is holding up my upgrade to 4.6. I'd love to upgrade but I can't risk losing everyone's bookmarks. 

I have uploaded the new version to the MP.

 
Took way longer than expected, but almost every line of the code was changed to improve the quality and to follow the new MP guidelines.
 

4.6 is pending approval. 

@Fosters - any news on when the 4.6 compatible version is going to be released please?

Is it possible to block messages with URLs submitted through the Contact Us form? 
 
We get tons of spam this way and it all has links. Almost none of our legitimate messages from the Contact Us form have links. 

We’ll mention the IP address in the support request once it gets necessary:) 

The problem with "ad serving software" is that they are easily defeated by adblockers because you have to inject their .js in the code.

Amazing. Purchased and installed. 

Why is this still not a thing?
Ignore is pretty much useless in it's current state.  I hate that we've been fighting for this feature for this long.

Please consider bringing this back. People are frustrated that ignored folks still show up in the stream and drown out other content. 

Please don't deprecate this. Hide in the docs, put up big warnings if you must, warn people that there is no additional security by doing this by itself, but please leave the option intact. Security through obscurity is the reliance of hiding things on security and is bad news bears. However, having the admin control panel in a non-standard place is one of many layers of protection, upon which moving it is not relied upon for security.
Consider Magento: https://docs.magento.com/user-guide/stores/store-urls-custom-admin.html
Capturing and mitigating against attempts to access the default URL serves a honeypot of sorts (we identify and isolate attempts to hit /admin which would be coming from no one up to any good), helps protect against scripted attacks, and layered with other protections, serves as a multi-layered approach to security. We secure administrative things on multiple fronts, including moving the ACP address, protecting access behind zero trust authentication, and having separate accounts for elevated administrative functions. We monitor and block traffic attempting to access known paths that no legitimate user would have any business accessing (i.e. example.com/wp-admin/, /admin, etc.), but we protect the actual administrative things as if the URLs were known to all.
The option to change the ACP path absolutely should come with a big "do not tamper with unless you know what you're doing" sticker. But please don't take it away.

No. It’s specifically meant to be an image-centered design. 

They are widely used because they are cheap, not because the company has good service. 

I think we all need to keep in mind that the view from the top is always best. I’m willing to bet there are good reasons SES hasn’t been implemented via API. 

I used Sendgrid based on the recommendation of the IPS staff and because support is built into IPS. Unfortunately the price of Sendgrid is 10x that of Amazon's SES simple email service. 
I just switched over to Amazon SES and am stuck using the SMTP route rather than via the API because there isn't native support via IPS like there is for Sendgrid. 
I'd like to ask for or vote for IPS adding support for Amazon SES, just like it supports Sendgrid.

I wonder why image extensions are hardcoded instead of option in ACP? It would be great to have this as an option, so everyone who cares about modern image formats could add them there without any code.

Sounds like it's a webp image that has been renamed to ".jpg". If that is the case, our backend won't be able to process it properly and that would explain the error.

PHP 8.0.0 has been released. Some bugs that I've found in a couple of minutes of testing:
There are a bunch of deprecation warnings for required parameters following optional parameters - from my search with the regex function\s*\w+\s*\([^=)]*=[^)]*,\s*\$[^,)=]*[,)] there are 47 instances of this in the suite. It should be safe to remove all of the offending default parameters, since they can never be utilised. The cms lang key can_edit_item_message_record is invalid - it contains %S rather than %s, which causes the page to (randomly?) 500. Fatal error: Cannot make static method XMLReader::open() non static in class IPS\Xml\_XMLReader in .../system/Xml/XMLReader.php on line 34 (this might be a fun one to fix - it's a PHP 8 change that isn't compatible in either direction - https://www.php.net/manual/en/xmlreader.open.php#refsect1-xmlreader.open-changelog - you probably have to make a new method that delegates instead) TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given from statusContainer.phtml:133 (when viewing a feed containing status updates) PHP Fatal error:  Unparenthesized `a ? b : c ? d : e` is not supported. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in .../applications/calendar/widgets/upcomingEvents.php on line 153 If I come across any more issues, I'll add them in this topic, and encourage others to do the same.

Thanks for the reply. yes, I agree on all accounts. 
The biggest reason why I want to edit the schema.org stuff is that IPS is using the Article tag that isn't valid for this and I want to add more tags related to product reviews. I figure I could add these then run the validator to make sure they are correct. 

Just finished the day-long event at Google. Very informative.
I have tons of questions now about how to implement stuff through IPS.
For example, I'm using the Google Structured Data Testing Tool and see they like the Schema.org syntax whereas it looks like IPS uses Open Graph tags. When I test a URL on my site I see an error "Article is not a known valid target type for the itemReviewed property." I want to try to use the structured data like Google recommends here - https://developers.google.com/search/docs/data-types/review-snippet
and validates here 
- https://search.google.com/structured-data/testing-tool?utm_campaign=devsite&utm_medium=jsonld&utm_source=review-snippet
 
If I manually edit the metadata for a front page article that reviews a product, it looks like I can only use OG tags.
Question: Is there a way to use the schema.org structure within IPS?