Charles

Please contact support. We support our betas 🙂

The preview site at https://invisionalpha.com/ has been updated with latest fixes.

We have not yet released a downloadable alpha. We could but will wait until January. Not the best time to do it now 🙂

https://invisionalpha.com

Matt knows me.

I'm always wary to add core-code for things that have only ever happened once in 15+ years 🙂

We won’t quite make it this year but will have a public alpha and/or it installed here on our site in the next few days.

You're right it should not be a thing 🙂 if it is on your site please contact support as we have logic built-in to prevent it.

To answer those concerns: put simply we are replying. The OP has one ticket in support which is the first ticket opened under their account since 2013. The reply history is: September 4 - opened ticket September 4 & 5 - various emails between OP and our staff September 14 - OP reply back to the email we sent on 5th September 17 - various emails between OP and our staff As of this moment we are simply awaiting for OP to reply back to us. It's not really appropriate to do this on the community (which is why your other posts were removed) but I wanted to be sure the record was accurate for those concerned as we pride ourselves on responsive support. The OP is asking for a refund for a purchase from 2012 - it's so outside the bounds of normal I cannot recall anyone ever asking that before.

By default, there is no personal data on a user's profile page. The only way anything "personal" could show up there is if the admin added custom fields to prompt the user for more information and then had those fields show on the profile page. So if the admin were to ask the user for their favorite color and checked the box to show on the profile page then that might be a personal bit of information. Otherwise, there's nothing personal on the profile page by default.

Actually the query string is there because it's a cache-buster. It changes when you reload a theme or JS change or something like that. If you configure your CDN to recognize the query strings on those resources it will work properly.

That error means our firewall is blocking your IP. It's a temporary block and can be caused by connection floods or high error rates from your IP.

I guess the way I look at it is: If you are having a problem, you run support tool. There may be a patch for the problem, great you apply and it's fixed. There may not be a patch so you submit a support ticket. Either way you get your problem addressed. If you are not experience a problem then you do not do any of that as you do not need a patch nor do you need a support ticket. Everything is fine. You don't need to worry. You are happy. Patches are irrelevant to you.

The support tool is the only way to get changed files only as it’s how the system knows what you need. Why would you not want to run support tool?