Jim M

On iOS, use Safari and click the share button -> add to home screen. On Android, use Chrome, click the menu -> add to home screen. There is no popup message for PWA.

Can use the following guide as a base, just need to grab the contents of the file Google gave you and name the page the same as the file theyve provided you. https://invisioncommunity.com/4guides/suite-applications/pages/tips-tricks_361/creating-a-robotstxt-or-adstxt-file-r318/

There are 3 options for CAPTCHA for you to choose from in ACP -> Members -> Spam Prevention -> CAPTCHA tab. Whichever is selected there is used throughout your community where CAPTCHA is necessary. Additionally, reCAPTCHA v1 by Google was deprecated (the one with the letters/numbers you had to type) so was removed quite some time ago.

There is not a separate mobile view in our software as a responsive architecture is used (aka we adapt the view based on screen-size). CSS loads for a whole page regardless of what screen-size is used. You would need to use media queries to specify what parts of your custom CSS should render for certain screen-sizes: https://www.w3schools.com/Css/css_rwd_mediaqueries.asp

Font sizes, left/middle/right justifying text, etc... can all be done with the editor toolbar. Realistically, there is no need to allow members access to HTML as virtually all editor functions can be had in the toolbar similarly to MS Word. HTML should only be given to administrators or trusted individuals who in an extremely rare case need to do something elaborate with HTML. Editing in source HTML removes some validation which is done so it is only recommended to allow this for trusted individuals in rare circumstances. It is worth noting that BBCode (if you allow it in 4.5) will still be processed in Invision Community but upon submitted it will be transcribed in the database just like every other post. Meaning if you go back to edit that post in source, it will not be in BBCode but HTML.

I would suggest checking out their website, likely answer your basic questions. As we've installed everything for you in the base software, you just basically use the HTML wherever HTML is accepted in our software. FA example: https://fontawesome.com/v4.7.0/examples/ FA Icon list: https://fontawesome.com/v4.7.0/icons/

Other issue is that the number can change with other moderator functions too like split/merge/delete/etc... Not really ideal to statically number things in a dynamic world. Most older posts in a topic might not change but this is a good example where numbering can get confusing. If they are referencing those posts in a separate topic, I would recommend using the permalink as @Morgin mentioned. This is the way to reference an individual post outside of a topic. If a user is commenting on a post in the same topic, the "quote" feature should be used to reference it. If a member is just wanting to save a post for their own future reading/reference, a bookmark tool like in your browser or the app you mentioned are a good way to revisit.

Couple things to mention (note: I am not an expert at SEO. If you need exact answers or help reaching out to an SEO agency/specialist may be your best bet) : Changing your software will more than likely itself cause a URL change as most software have some varying URL configurations/naming conventions. In addition, you changed the location of the software on your domain so this will also cause a URL change. During this period, your organic traffic may dip but should recover as the search engine re-indexes these new URLs. 301 means a permanent redirect and instructs the search engine the old URL should not be indexed anymore. A 301 passes all the link value a discarded URL has accumulated over the years over to the new URL, so it causes the new URL to gain or retain value. Thus, it is OK and recommended to leave these in place. More on redirects: https://yoast.com/which-redirect/ Meta keywords are no longer part of Google's and other search engine's algorithm. Google in May did a huge algorithm change: https://medium.com/better-marketing/google-may-2020-algorithm-update-4-key-changes-and-how-to-adjust-9fdd6294b83c

Correct. Only the block (widget) would display this information.

Are, at minimum, 5 of those 10 posts in a single topic and within 60 minutes of each other?

Are you using Google AdSense's auto ads? If so, this is likely what is happening. You will need to disable this in Google AdSense.

There are no limits other than what is displayed on the upload UI and controlled by your member group settings. Keep in mind, if the gif animated, this can impact the server resource consumption as well. You may wish to switch to GD if you’re running Imagemagick and do a lot of animated gifs. You’re welcome to submit a ticket to see if we can find something to help you go back to your hosting provider with.

If you were uploading a large gif, this likely hit some resource limits on your server when attempting to process it. Smaller images are not hitting this error due to it is not using the same resource consumption by your server. Your hosting provider would need to confirm by looking in your logs. That error coming back is a processing issue on the server (not software), I'm afraid.

The billing address is before any credit card or payment information so this would not happen.

Through shipping rates, you can set which countries you want to ship to. It does not remove any selection from our address selection but will not allow the user to complete purchase and warns them of this. Example: I'm in the US and don't want to ship large products to the UK.

We're in the process of updating guides reflect UI changes but this process is the same: https://invisioncommunity.com/4guides/staff-and-moderation/creating-administrators-and-moderators-r31/

That's an error when uploading a file to your server and the server is failing to process it. If you use our Cloud, please submit a ticket. Otherwise, you'll want to check: All folders have proper permissions. (take into consideration if you are or are not running suPHP or suexec) The size of the image you're uploading. Is this above your PHP upload_max_filesize? If you're not seeing any thing wrong with the above, you'll want to contact your hosting provider to check the Apache Error log to see if anything is standing out as an error processing the request.

In 4.5, the block that Daniel is referring to is an easy way to do text and then can also do some extra styling via some built-in settings or CSS. It's pretty cool but may not be what you need here. In 4.4/4.5, there is the WYSIWYG block in Pages which gives you the standard editor you see creating content throughout our software. This you can do an easy title and normal text using the editor buttons.

This warning in your ACP is a strong recommendation as these functions can be dangerous but our software can run without issue with them enabled. This is merely a recommendation to strengthen the security of your server as our software (and others) does not utilize these dangerous functions (as mentioned in the warning). If you are on a shared server, you may not have complete control over the server as indicated by your hosting provider. This would be something you would want to research if you want the capability to better secure your server or stick with your provider.

Just need to click the dot.

Correct. It is group based.

Ideas don't make it into our software because of the size of the community who requested but the merit of the idea and the usefulness of the idea to other clients 😉 . Screenshots are indeed not required. This a is a per category setting.

Think this would be a case to allow screenshots in the Downloads application to be re-used across downloads like we do for many other attachments, rather than storing some images in 1 directory. I'm not sure how popular this would be though as I don't imagine many people re-using screenshots in Downloads. However, you may wish to make this suggestion in the Feedback forum if this is something you desire.

The og prefix is for open graph, this is mainly for when your website is shared to Facebook and other websites. Little information on that: https://ahrefs.com/blog/open-graph-meta-tags/ That would only be if they are using Forums as their default application is at their community index. As mentioned, it would be better for them to assess the situation and use the information provided in my post if they are unsure:

That will place the "og:site_name" tag on all pages as you've inserted it there. Testing that myself, that is what I'm receiving. As you've left the Title tag empty, it won't replace anything for Title.