Marc

Another patch has been released for this, so if you are still having problems, please see the new patch

Think it was just missed there. All good. 2 helpful replies are better than none 🙂

You create one exactly like you have just done. Support is done here 🙂 In the first instance, please could you disable all 3rd party items and test this on a default theme? The most common cause of these are 3rd party themes unforunately.

Its actually not related to the change in support. It's the item in question and what is involved to deal with it on this one unfortunately. I have however tagged someone to take a look to see if we can get this sorted for you, and thank you for your patience on this one.

Glad you have what you need there 🙂

I have tagged developers to see if there is anything they can add here, however I do need to point out the common denominator doesnt appear to be the site. It appears to be yourself. If you take a look here, you can see I am seeing no issues on my end

There is no way in which to tag them, but you can indeed create folders. While in the conversation system, click Inbox, and you will notice you can create new folders there. You can then move any conversation to that folder using the options menu

Thanks Nathan. Have reported that internally as a bug

If this is only for some users, it is very likely that its cache on their own machines. Please get the users to hard clear their cache on the browser and try again

All I can really suggest at this point, is to let us know if you see this happen again. We can then take it a look at that point in time

Is there a reason you are not simply using the upgrade option for this?

It will run only so many at a time, so it wouldnt update all of them instantly. Are you seeing any errors being returned from your cron?

Please could you provide a link to that message and let us know the user you are logged in as?

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.

I have created a ticket for you on this, so we can take a closer look for you

You would simply restore the archive database to the same database as your live database, then you would need to ensure your archive database setting point to your main database

That is correct, yes. Of course it wont distinguish between true guests and bots, but it would certainly ensure no bots are viweing them

Just an update on this one. We have taken a look at the issue, and the fix is quite involved, and probably not worth updating. The reason for this is that the profile area in general is something we are looking to take a look at as a whole, at some point in the not too distant future

Having looked into this, it would require substantial changes in order to implement this unfortunately. At present, if an admin is editing manually, they would need to make any changes to groups needed at that point in time. While this may be revisited in the future, this is not something likely to see change in the immediate future

Just a quick update on this one. Having looked into this, it's going to be quite an involved fix, which will not be changed until a major release due to the level of change needed to accommodate this. Wanted to make sure you were updated so you can find workarounds if needed.

Just a quick update on this one. This is a bug with ckeditor itself, in which we will get a bug report posted up with them. Of course this does mean there isnt really any timeline we can give on a fix for this one

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.

There is no way in which to automatically cancel an item after it expires unfortunately

Thank you for letting us know. Please ensure you report the issue to the author of that product.

Very sorry to hear that you feel this way. However I must admit to being very confused about your post there. The issue was reported by yourself on 23rd august, which is a little under 2 months ago. It did also take a couple of week to get to a point we could replicate unfortunately, which led to a ticket being created on your behalf. This was then investigated by a senior member of our team and confirmed to be a bug. It can take some time to resolve some issues on the system. While we would certainly like to fix every bug overnight, unfortunately, this will not always be the case. We have had quite a large release, which (as with every release) will result in some bugs that need to be resolved, and these do have to be prioritise. Some may make the first release afterwards, and others may take a couple of releases to be resolved. As we release once per month, the amount of time you are looking at there is not something that is unusual in nature. This said, the bug in question has been assigned to a developer, and is being looked at. Some, unfortunately, simply take longer than others to resolve.