Daniel F

It sounds like a doorway technique, called cloaking. You will be penalized by search engines if you try it.

Either 1 by one by viewing the content or via a 3rd party app.
I’m using https://www.ic-essentials.com/files/file/7-tags-manager/ to mass manage the tags via the ACP. 

SEO Essentials by @Daniel F offers an option to disable indexing.

Hi,
this could help https://invisioncommunity.com/files/file/10199-tags-manager/ 🙂
 

To your custom.css and you wouldn't need to remove it, but I would strongly suggest to remove it from the custom.css once we release our next maintenance release containing this fix.

I was able to reproduce this with Chrome.
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Either 1 by one by viewing the content or via a 3rd party app.
I’m using https://www.ic-essentials.com/files/file/7-tags-manager/ to mass manage the tags via the ACP. 

Either 1 by one by viewing the content or via a 3rd party app.
I’m using https://www.ic-essentials.com/files/file/7-tags-manager/ to mass manage the tags via the ACP. 

Ok next to my previous finding, there's also another issue => The original topic was merged into another one, so if you open the link in a new window, it's going to run the proper check and it redirects you to the new topic, but the embed logic is missing this.

If anybody else runs into this issue => It's happening when the embed links to a deleted comment/review, so the error is "correct", but I have to admit that it's not really user-friendly, so we improved this by replacing the error with a more meaningful error message and we'll also output the link to the content item the comment/review belonged to.

If anybody else runs into this issue => It's happening when the embed links to a deleted comment/review, so the error is "correct", but I have to admit that it's not really user-friendly, so we improved this by replacing the error with a more meaningful error message and we'll also output the link to the content item the comment/review belonged to.

If anybody else runs into this issue => It's happening when the embed links to a deleted comment/review, so the error is "correct", but I have to admit that it's not really user-friendly, so we improved this by replacing the error with a more meaningful error message and we'll also output the link to the content item the comment/review belonged to.

If anybody else runs into this issue => It's happening when the embed links to a deleted comment/review, so the error is "correct", but I have to admit that it's not really user-friendly, so we improved this by replacing the error with a more meaningful error message and we'll also output the link to the content item the comment/review belonged to.

Have you applied the latest patch? The promotion works via background tasks and it’s possible that due to a bug the tasks stopped working. Applying the patch via the support page in your ACP will probably  resolve it. 

Im interested to hear what part of these you believe you cant already do in some way, other than the leaderboard?
Points  - This is the bases of the current achievements system
Score - Every user has an amount of points, so that would be your score
Virtual Gift - Essentially, if they are virtual in nature, you could use badges for this
Points are of course already awarded based on rules as you have suggested there.
 
 

Daniel started to help me in the customer support email, and he stated something about the promotions appears to not be local. But I knew I only promote local, so his comment lead me to one thing after another and I tried to promote without the local promote box text, I'd delete the text but keep the box, thinking I could just have the image and caption displayed without introductory text, but it would not go through.
So, I added text, just a few words, and the promotion went through, it displays.
I did not delete the local promotion box, I just deleted the text from the box, and that was enough for it not to schedule and promote. Don't know if that's a bug or not.

We have already fixed this for an upcoming release.

Got Pages? In the ACP, do the following (specifics included only...if it's not specifically mentioned, it's up to you what you set things as)
Go to Pages -> (Page Management) Blocks Click "Create New Block" Change "Plugin" to "Upcoming Events" Click 'Next' Name it & add a description Go to the 'Content' tab Change "Use this tempate as-is" to "Use as a base for a custom template" Find the following: {{foreach $events as $event}} Add this below it: {{if $event->online}} Scroll down to find: {{endforeach}} Add this above it: {{endif}} Save Go to Pages -> (Page Management) Pages Click "Add Page" Click "Next" Name it, give it a filename Click "Save" Give permissions On the resulting listing of Pages, click the "Open page builder" Use the block manager to drag your new block into place on the page. There's your online events page.  

It says “See the JavaScript console for technical details”. That’s where you need to look. 

Even if you were able to optimize the data in one way or another, you are only pushing the problem away some months into the future, when the space is used up again. A 2GB limit is just too small for a successful Invision Community installation. 

Are notifications working for your other members?
Have you applied the latest patch ( ACP => System => Support ) If not, it's possible that your background tasks stopped working.

Are notifications working for your other members?
Have you applied the latest patch ( ACP => System => Support ) If not, it's possible that your background tasks stopped working.

Thanks for the note.
I tested it on a dev instance too. Let's see if I can reproduce it on production.
Edit:
Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Sounds like the database wasn’t imported or that the connection details weren’t updated in your conf_global.php file