Jim M

Make sure your uploads directory (and all sub-directories) is writable and owned by the correct user/group.

Glad things are working for you now.

The constant is in the constants.php file on your server. Once you remove that constant, you can simply rename the admin folder or re-upload from the Client Area.

You may wish to ensure the user’s device is up to date. The device controls what emojis are represented visually so it would be up to the device display it.

Glad to hear you were able to resolve it.

Please try to clear your browser's cache, I do not appear to be having issues with these items on your community.

For any new features, please make a topic in the Feedback forum. Currently, this is behaving as it should.

You will want to check the message above for Cloud customers:

Embeds will not work in Emails. This is due to how emails function.

Hello, Sorry for the inconvenience. We are in the middle of a maintenance window. Some communities will have brief issues but some communities may last longer. Once we are beyond the maintenance window, if you're still having issues, please let us know. You can find our status page at: https://status.invisioncommunity.com/

Yes, this is part of the maintenance. It should be quick but some individual communities, it may last longer. Once the maintenance window closes, if you're still having issues, please let us know. https://status.invisioncommunity.com/

You should always relate your email campaigns to users who are on-topic (segmenting your list as much as possible is advised. i.e. we wouldn't send an email campaign about Cloud features to our self-hosted clients 🙂 ), who are recently active with your campaigns, and obviously, those who know who you are still. From a technical perspective, yes, there are huge risks sending a bulk email of that size in one go. If you're sending to email addresses from users who haven't been on the community for a while, your email sending provider will likely block you once you get a lot of bounce backs if those addresses don't exist or otherwise. If they your provider doesn't, the recipients' email provider could also blacklist your domain or sending IP address. If the receiving individual doesn't recognize who you are either, they could more than likely report you as spam too. Which will also hurt you. Due to this, I would suggest reviewing your list criteria and make sure you're communicating with individuals who are relevant to your topic, who are active-ish on your community, and obviously, would want to receive such an email. Another example is if you are sending an email out to advertise maybe an event which only has 30 seats, you don't want to send an email to 100k individuals in one go. People will get mad if it fills up right away. Best to send out in batches or get your criteria as specific as possible to those who would most likely benefit most from the event and then move on from there.

Some things will be mentioned as simply information unless it states "you are using."

You would want to direct them to the system checker. (Where you're actually seeing the blank white page that is an issue) The error there in your screenshot can be found by going to your admin directory, however. The second line should show the actual error our code is seeing.

You’ll want to contact your hosting provider or hire a server administrator

Votes are different that upVotes where I believe you're thinking to them as reactions. Votes are in QA where an answer is voted upon, this is separate from reactions. I have marked this to a developer to ensure that the vote should not be 1 for marked as solution replies.

Are you referring to:

Only if you were having issues would these have impacted yourself. This should be resolved, however.

You would need to upgrade your license to Classic in the Client Area to download version 5 under your selfhosted license.

Did the System Requirement checker state you were missing anything?

Would not be concerned then with this change as you already deploy more secure methods than this could offer.

Our Cloud team is currently reviewing and investigating an issue. Please bear with us

I have replied to the topic, please try replying to my email.

We would recommend removing the constant and ensuring the admin folder is uploaded. Other than that, no modification is needed. Security through obscurity isn't the best method of security. Now with such advancements with Multi-Factor Authentication, it's not really necessary and is just bulk in our codebase.