David..

I was sent an email today (the email did land in spam folder) from this person stating they found some vulnerabilities and after asking what they were, they replied back with a list.
I'm unsure if it's an automated email, or if it's a scammer, but it may be worth it for someone from IPS to look into? Who do I contact for this?

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

I’m sure they do; but that’s when IPS can simply have an automated reply at the ready or even a tutorial link to resolve. So really it shouldn’t strain support at all and increase overall user satisfaction even though it is a trivial issue.
Designer mode is recommended to use on a test install. While that may work, it is an extra step which realistically feels like only expert theme designers use.
4.7.0 did introduce an easier way of adding CSS which is great for newbies, but again, I don’t see why there was a need to remove the intermediate option.
It was a very convenient way of playing around with (a copy of) your theme.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

Page speed aside, there was really no need to remove the core CSS from the templates. I agree that most users do not need it so they would of course simply ignore it; but the ones that do need it had the option to view, understand, learn and modify if they wanted to.
CSS is basically harmless and any issue that may come up we could just restore the file to the original version so this shouldn't strain IPS support.
Basically: us self-hosters are already getting hammered with the cloud only features. There's no need to remove features too now.

For my part, I would be happy if all CSS were readable, as before, for reference even if not editable. The latest patch shows modified CSS and allows reverts of existing changes but unchanged CSS are still hidden and therefore, you can't use search.
It was so useful being able to search for something (even something as simple as a colour) and then quickly locate the code, copy it and then paste a modded version into custom CSS.

So, this is for cloud only.
This will be available to the hi end people who probably spend many hundreds / thousands a month and never post here.
How many hobby sites can afford 149 dollars a month?
Not sure how many self-hosted customers you have, but I suspect that is who read these posts, and yet, it will not be available to us.  Not sure why I would be excited by this.
Kinda feels like a poke in the eye to be honest.

The issue: when someone let’s a subscription (product subscription or regular subscription) expire, they will later not be able to buy it again, because the invoice on file prevents a new subscription. But the existing subscription also cannot be renewed because the invoice has expired. This can only be solved by intervention from an admin (manually finding and deleting these invoices), but there might be hundreds of those and it would require a constant monitoring of expired invoices. 
The solution: The check that prevents a new subscription with an invoice on file should be removed or adjusted. Someone who doesn’t have a subscription anymore, because subscription and invoice have expired, must be treated like anyone who never had a subscription. Both groups should see exactly the same offers because their status in relation to these subscriptions is the same. 
Why it matters: People run into this problem all the time and it’s not just an inconvenience, it it costing them money, because people who would want to pay cannot pay and probably just give up. Here are just a few examples from the recent days (and I have observed this and commented on it for years): 
Subscription buttons don't show up. (yesterday)
Subscriptions Bug (yesterday)
invoice has expired but member cannot renew (7 days ago)
The development time to fix this is probably much cheaper than having IPS support deal with this issue for years, constantly identifying the issue and guiding people through the process of the possible work-arounds. So it would be a win-win situation to finally fix this. 😉 

Invoiced for payment subscriptions seem incredibly outdated in 2022.  So throwing my support in to get this fixed as it is absolutely not how the average user would expect the feature to work.

Just wanted to say that I’m quite happy with your apps. Hope one butthole surfer doesn’t ruin it for the rest of us.
Good luck!

Just wanted to say that I’m quite happy with your apps. Hope one butthole surfer doesn’t ruin it for the rest of us.
Good luck!

Thank you for the 4.6 update! 
But it would have been much better if the option was placed inside the post options rather than next to the quote buttons.
@InvisionHQ

Then yes, indeed that would be expected. The only items that would work would be logging in internally with users who can see  the site when the site is offline. There would be no way in which to use the oauth web service if the site is offline

+1

+1

What is IndexNow?
IndexNow is an easy way for websites owners to instantly inform search engines about latest content changes on their website. In its simplest form, IndexNow is a simple ping so that search engines know that a URL and its content has been added, updated, or deleted, allowing search engines to quickly reflect this change in their search results.
Without IndexNow, it can take days to weeks for search engines to discover that the content has changed, as search engines don’t crawl every URL often. With IndexNow, search engines know immediately the "URLs that have changed, helping them prioritize crawl for these URLs and thereby limiting organic crawling to discover new content."
IndexNow is offered under the terms of the Attribution-ShareAlike Creative Commons License and has support from Microsoft Bing, Yandex.
Documentation FAQ

Mine is showing anonymous users logged in but I have that function disabled!

- Added a Limit of 1 to the First Comment query to improve performance.

- Added a Limit of 1 to the First Comment query to improve performance.

- Added a Limit of 1 to the First Comment query to improve performance.

Will you put it up in the marketplace?