Jim M

Could you please provide an example where you're seeing this on an unmodified language pack?

You would need to remove the cards on file and pay manually if separate payment methods want to be used. If you have billing questions, you can also submit a contact us form to the accounts department here: https://invisioncommunity.com/contact-us

A ticket has been created. Please check your email to provide further information.

As a Cloud customer, you can submit a ticket if you do not want public facing items or ask for it to be brought to a ticket.

What page specifically are you seeing this? Unfortunately, picking a category at random, I am seeing that the albums in it are counted:

Sometimes the no tech solution of telling your users things they may not know than reproducing functionality is better, especially for cases like this that they can learn something to better their lives that is applicable elsewhere too 🙂

Most our customers simply use a sub-domain to access their communities. They have a main website on the root domain, say example.com, and then the community at community.example.com (or similar). It really isn't recommended to embed our community software in an iframe. If you want it to look like your main site, you can simply use a theme designed/styled like your main site so that it looks like your visitors never left wherever your main site is located.

You already got free code outside of an update 😉

There are browser extensions (and some native OS functionalities) which perform this functionality. Is there a reason not to use that? A lot of what we try to aim to do is avoid duplicating efforts where possible and focus on the things which make communities great.

Theme template modifications are not core software file modifications so would not count for what you're seeing as a part of this warning. You would need to download the latest from the Client Area as there were modifications on our end. Typically, we release these via the patch system but this was not done in this case and we apologize for the inconvenience.

It doesn't look like you're using a location service, like Google Maps so the country would not be able to auto populate based on that. However, it does seem odd if it doesn't populate to country if it doesn't know or can judge based off of your browser locale. I have tagged a developer for more info.

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.

If they are clearing cookies at any point, the device tracking would reset so each time they login, they would get a new alert.

The alert you're seeing there is not for patching. We have a separate system for patching. What you're seeing there is for alerting you that the files there are out of date, modified, or for some reason do not match what they should. It is rightfully a big issue so should be attended to, especially, in cases that you are encountering an issue.

Believe there may be confusion. The URL there is running WordPress, not our software. We would not be able to assist with WordPress setup.

Excellent. Glad to hear it worked. I apologize, I spoke too soon, our team had 1 more thing to complete and they just did it.

You would want to ensure you're saving as UTF8 and uploading as such via FTP. If you're still having an issue you would want to confirm with your hosting provider.

There should only be 3 lines. You will want to check what else you may have in that file. Additionally, the MD5 checker should be working now so I would try again without the constants.php

This is what you would want: <?php \define('UPGRADE_MD5_CHECK', false);

It just needs to be readable so whatever that is required on your server. Typically, it is 644.

Not everyone will have a constants.php. You will need to create it if you do not have one. You can reference this for assistance:

There is a ticket in with this question and as we've done the migration, we'll need to review it. Please watch your email for an answer to your ticket.

Thank you for your feedback. We alert on things which are required elements for our software to run (i.e. PHP, MySQL, file permissions, etc..). However, actually supporting them is a whole other matter and depending on the server configuring can vary drastically. Our support is limited to stating "your server administrator needs to assist you with requirement x" or "this may be an issue with your server configuration due to y" as our alerts do and maintaining the server is up to a qualified server administrator to take that knowledge and move forward. This is common of software and pretty much everything in our world. I had an issue with my dryer last week, called out a repair man and after some troubleshooting, it turned out that my house wasn't providing it enough voltage to the socket so I had to call out an electrician. I didn't expect the dryer repair man to fix or tell me how to exactly fix my electricity issues 🙂 . The dryer repair man is an expert in driers, just as we are experts in our software. The underlying items have their own expert(s) which need to attend to those. mod_security is not a required part of our software and it is on the decline for many hosting providers to be using it. While, we strive to provide the best experience to our users, it isn't possible to provide a warning for all possible modules out there. However, I will bring this up internally.

The sitemap includes everything which is being able to be seen by guests. It could be as simple as Google hasn't crawled all available pages in your sitemap yet. Without an exact example of stating this blog post is not available in your sitemap, it is hard for us to say otherwise.

Posts aren't pages. They are a part of a topic which is 1 page.