Marc

We can take a look to block these from google entirely, but Im pointing out here that there is not an issue as such here. Google would not penalize you for blocking items you dont wish to be indexed. It will simply not index them, which is exactly what we want it to do. 

As I said, we will look at it. 

Quote

But then... for what absurd reason does this stuff have to exist???

As I mentioned above, csrf is a security element of URLs relating to the identification of users. 

It is a problem only if those items are supposed to be indexed. They are not, and blocked by robots.txt, which Im assuming is what is being told to you on the page there. Unfortunately, I dont speak the language shown there, so indeed, its quite hard to understand. It happening after your update is purely coincidental. Nothing has happened in that area on the upgrade.

Without having tested doing this, there is no way I am able to say if it will cause any issues unfortunately. Simpy as its not something we have tested doing. All I can advise is testing this with a copy of your site, or at least being in a position to restore back if you test it on your live site

Yes, it would indeed send them a password reset. There is nothing built in that would achieve what you are looking to do here, as they are not intended to be removed

No problem. Glad to hear you found the issue

Glad to hear you have that resolved

Please could you advise on where you have found the indexing of real pages is being blocked here? There is no indication in any way that this is happening from what you have said there. Only the blocking (intentionally) of links that shouldnt be indexed

Please upload a fresh set of files from your client area, and then try visiting the upgrader again, in the first instance. If you then still have issues, please let us know

Im not seeing this happening on my end, no matter how many times I attempt this, unfortunately. You can see this here. Please ensure you disable all 3rd party items and if you have any caching methods on your server being used, I would advise testing with those disabled too. 

Has that user just logged in at all?

You cannot remove that without modification. IF they have set  a password within the invision platform, they would need to enter it to get to the security and privacy section.

There is no need to bump these items. If they are added, they will indeed be read and would be considered. Not all feedback items will make it into the final product.

^ exactly this 🙂

If you are unsure after looking at that user, we would need to know the users name so we can take a look for you

Pages is an application in which you can create pages or databases of pages in. Those pages could be named anything you like, and the databases and records could also be named anything you like. 

When you are looking at articles, that is just a pages database which has been called articles. Databases contain records that can be given a name. In this case, articles. 

So you have articles, which are stored in a database also named articles, which are within the pages application on our software. Of course you can create any number of things with the pages application, rather that articles. In an example here, we have created a database named recipes

There isnt a 'currency' application that Im aware of. Note the person who mentioned a currency plugin was yourself, rather than us. As far as we are concerned its part of commerce. crfkey is something added to perameters as a security measure by the software to identify a user.

You are chasing things here that, as far as we can see, are not an issue. Google is trying to index those pages, and the software is telling it not to do so, and therefore its not. There is no issue here from our perspective, hence why I asked what issue its causing you.

Glad to hear it. 🙂 Hope things are working better for you

Have you just added a currency at all?

Edit: On taking a closer look at this, it doesnt actually appear to be an issue here, as they are not being indexed. 

Im not sure what it is you are trying to delete. What happens when that member tried to log in?

You could bypass this by adding a constant.php file with the following in there. This will then at least allow you to get to the latest release, as it may be you have a bug in the release you are on ( it seems pretty old). Ensure you remove it once you are done

<?php
define('BYPASS_UPGRADER_LOGIN', TRUE);

Please feel free to post that up within our feedback section if you would like to see changes in this area

You have another method set up there also named standard, that is disabled. 

This is correct. Expired items would never usually dissapear from the client area. Are these causing you an issue?

This should now be resolved

In terms of status updates, its worth pointing out these are deprecated items which will not exist in version 5. So if you are starting a new site, its probably advisable not to enable those at all.

In terms of feeds, you can create feeds of these things using the block manager. Please take a look at the following guide on this