Marc

Ah, have you tried translating them from the stream itself in System->Content Discovery->Streams? I believe thats what the difference is between what Im doing here, and what you are attempting on your end

I have tagged our developers to see if someone can confirm that for you. Im not a developer myself on the platform

If there is an issue on the server, your users will of course also see this. When I refer to caching, I mean caching on your server itself. Please check with your hosting company if you are unsure on this

Do you have any caching running on your server at all? Im not able to replicate this in any way.

Please ensure you are on the latest release of the platform, with all 3rd party items disabled. I have been unable to replicate this unfortunately.

We do indeed support opensearch 2.1 so if you are having issues with that, please let us know and ensure access is up to date

You would need to contact your host in order to obtain this information. If you are using elasticsearch, really you should have a password set for it

Im not following what you mean here. Could you expain further the logic there? Im not sure how moderation would have anything to do with this to be honest. Not unless you have changed the no permission message at all?

If it happens again, please log the detail so we can take a look.

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.

Not without the username and the IP being used at the time, no.

Managing items is no different in v5 than in v4 at present. I would suggest awaiting its beta release and then having a play with it. If you then wish to make suggestions, of course those are always welcomed. However they would need to be specific in nature

Please could you provide more information on what exactly you are deleting? (which member and content)

I would suggest taking a look at our guides on this, and then if you have any specific questions, we can of course answer them. The questions you have currently are quite broad. Start here, which shows how to do subscriptions

Very sorry to hear you arent happen with the currently implementation here. Not all items suggested will be implemented, and while we would like to change every item wished for on version 5, unfortunately this is not really viable to do. So even some items that are planned to be changed, will not nessesarily appear in version 5.0.0. It is worth noting, what you are asking for is actually a new feature, not a change to an existing feature. 'Block' and 'Ignore' arent one and the same. We have an 'ignore' feature, which hides content you may not wish to see from another user. That is very much a functional item, and is well used by our customer. The block feature you are looking for us to implement, simply isnt a feature at present, and I feel the 2 are being confused. They are not the same thing at all. Ignore - I walk into a room, and ignore what a person is saying Block - I walk into a room, and I dont know a person exists, and they dont know I exist.

There will be betas available at some point, but we arent there quite yet 🙂

As mentioned above, there is no way in which to do this currently

This is still an open bug report at present. I will see if we can get an update for you

CKEditor no longer exists in 5, so that will not make it to core 🙂

We're getting there, and glad to hear you are excited to get testing! 🙂 Us too. At present its in public alpha, as mentioned by Randy above. Once we are ready with a downloadable beta, we'll get it out to people.

All I can suggest at this point is to let us know if you see this happening again, along with the user its happening with. As it seems to have resolved itself currently, there would be nothing for us to check. We would need to know the user in question and the IP at the time they are attempting to log in. (of course feel free to pm this)

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.

We would not generally respond to all suggestions. We do read all of them however, and there would be consideration of these of course. At present, as shown in the admin CP when setting up, you must be running elastic search at least version 7.2.0, but less than version 8.0.0.

In reality, if you are asking these questions, I would highly suggest getting someone who is familiar with converting to the platform to assist you. Otherwise its very likely you are going to end up hitting issues