sudo

🤦‍♂️
Sorted, thanks, I knew it would be something simple.

Have you set up any tags in the Customization page of the Radical Tags application yet?
You'll need to add some there, and then you can define which prefixes can be used in a specific forum if you need to.

Typically when this happens, it is a security module or permission error on the server causing the redirect. However, if you have any custom redirects in place, I would not rule those out either. At the end of the day though, this generally is a server error, I'm afraid.

Just as a note to future readers of this topic, the issue looks to be by the Elastisearch provider not allowing access to the task and update by query APIs.
If you get any odd issues with multiple entries where there shouldn't be in streams, it's almost always update by query not working or being blocked by the host.

PHP can override this.

So it should never be cached at all? that's what those settings are.

Please try this again. Its likely its simply timed out. If you get the same issue again however, please let us know.

This resource will always require the password to link the account. You can use the standard login as in the ACP and it won’t require the password. 
Yes.

Do you have an example we can take a look at here? I can then have it investigated further.

Glad to hear it 🙂 

Thanks that has got the Rebuild Profile Photos task going.

Please try the file I have just sent you, which is in the next release. That should resolve your issue

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.
 

Automated search monitoring so a user can configure a stream with certain forums and search term and if any posts are created they get emailed out as a digest to help draw them in, or at least a search term AS with rss feed.

Multimoderation from search results.

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.
 

Hi
Just downloaded the patched files to go from 4.6.5.1 to 4.6.8 using the admincp and I opened the zip to find a folder called .github with a file called changelog-4.6.md inside that mentions 4.6.9
Is this folder normal as I normally do it via a full download (as server doesnt use ftp) via the customer area but it seemed strange to have a stub of .github inside the zip and a file mentioning 4.6.9.
Thanks

Just a quick update to let you know a patch was just released for 4.6.8, and is available within the support area of your admin CP. No need to wait for the next release 🙂 

If any of staff groups have access to can post anonymously, and would like to edit a member's reply or topic, it will change the author of the edited post or reply to the staff member who edited the post or comment. 

 

Yes, it is safe. We don't normally update changelog if we're patching but something was patched that had a changelog entry so created a new entry there. Our developers our working to resolve it.

As Ballmer would say:

It is one of the reason several of your competitors were not options for us, they are so so valuable to a platform even if a customer doesnt buy an addon, its the perception that they can and there is a diverse ecosystem of addons as options.
Nearly all big platforms over the last decade have been powered by very strong developers adding value. iOS, Android, forum competitors all have got where they are because of developers. Windows Phone died because of the lack of developers. Keeping them onboard and happy is a huge deal, it wont necessarily affect huge enterprise customers but it has a big effect on your long tail customers.

I dont think devs need a free license as such, they should pay the initial fee for the licenses but I do think you can work some magic for renewals.
I know you wont be able to move fast on this as it will require thought but I did suggest a few approaches earlier in this thread.
You could get dev's apply for reduced renewals based on the agreement the install wont be used to run a non-related purpose. They can have a public site but its for marketing/demo the addons, testing and direct support, that would mean even though they are selling lots of addons its adding value to your platform and allowing them to continue.
In addition (or as a different approach) to this you could tier the commission for sales, they get a big discount on renewals but they have a higher tier of sales commissions for addons sold. Then if they hit a certain sales point they can pony up full renewal but reduce the commission they are charged by yourselves. This approach would allow people who make a lot of free addons to continue and feel hopefully more valued and it would make the whole product stronger.
I dont expect a big in depth reply to this, I am more throwing suggestions to you so that it can be discussed behind the scenes as losing developers is one of the huge concerns I have and is a major issue for us. Its very conerning when some of the best devs on here have voiced concerns and also said they will be removing ipb addons from their package removing the ability for them to develop and expand those addons.
I am considering releasing a few addons I have made privately but they would be free and our license would be used for a full separate site so I would not be eligible for the discount above which I would have no issue with.
Man this is sad to read, I love your work and to see you doing math about its future.
IPB try harder to help developers, they may not be your bread and butter with commission profits but they are so so important to the platform. They should get a very generous discount to continue to make addons
 
Also I still think you could have done the price increase, kept everyone's next period 6 months (aka yearly switch happens 7 months from this date, 7 months to allow people to find out) and kept email support while steering people to the forum more. The price increase + losing direct email support is a big deal.

I am not sure where to start with all this. I cant believe you guys did all this along with a site redesign at the same time and no notice period, I am speechless!
I cant believe I will be losing email support while you increase the price at the same time. I paid for priority support and now that's an insane price per year for what is email support. It takes serious cahoonas to both increase the price and cripple email support at the same time. Email support pricing should be far far more reasonable, I honestly thought $1250 was a mistake when I saw the screenshot above, I could understand having an email support pricing tier and then a $1250 priority support tier but also renewals shouldnt be going up while we lose proper email support.
Then if we dont pay for support we cant use the market place and cant even save our prior purchases so if we need to reinstall an addon we are out of luck.
We are lucky, we can afford the support increase price wise but one of the HUGE reasons I liked IPB was the email support, it can be very curt at times but I valued it and if you had only increased the price and not removed email support I would have dealt with it as it has been a decade.
I am strongly considering renewing our Xenforo license to have a play and test viability after this.
Initial feedback:
Build the knowledge base publicly first before removing support
I understand the desire to have self support with a knowledge base, its a good thing for everyone if it gets populated but you should have been doing this months ago building the knowledge base publicly before doing any changes, that way you can point to the option and say its there and useful. Get a common ticket theme in, create a KB article then have the subject field for support request do a search as you type pointing you to articles that sounds similar before submitting the email request.
We need a reported/acknowledged bugs area
This needs to be along with the knowledge base really, a bug tracker would have cut your support requests because people would be able to see if it has been reported before, I know the support forum kinda does that but its not a bug tracker and its not clear if its an active bug with a fix pending or release or even workaround.
When I hit an issue on other software I always check to see if it has been reported first on bug trackers but because of the strange mantra of open a ticket you guys have we are blind to upcoming fixes usually until release, Jordon has at least been mentioning them but its still not a proper solution.
Both things above should have been done before these policy changes with support
That way your customers would have become familiar with them and you could have iterated through any issues with them before removing email support and you could actually see if this type of support works well before causing big issues for your customers, it seems so rushed.
You guys made the whole "tickets are similar" problem yourselves with the submit a ticket mantra that is here, you should have been correcting that before making sweeping changes to support. You have entered self support mantra with none of the real tools used by others to help aid people do this. You may have plans for these tools but you literally have not shown them to us which is crazy if they exist. Right now we have a sole forum for support, I have no idea why you have rushed this through.
I have more to say but I thought I would shoot out first.
Please get the knowledge base live and a bug tracker live asap to at least help and to be honest delay the email support changes past the renewal/January deadline until this mess is sorted and people are comfortable, this should be a much much slower transition.
 
Also contributors/devs need a discount/special license to prevent the massive bleed that will happen.
Its crazy you dont have a way of reducing their burden and its a major issue to the viability of the market place and IPB. Their are fewer addons here than other competitors and it will only get worse with dev's having to pay large amounts to renew AND customers of devs having to pay to even buy their addons or even install them. This is crazy crazy crazy and so hostile to developers. Its one of the main reasons no one wants a certain v5 of software out there, regularly people complain about the lack of addons.
You could get them to apply with the proviso the license isnt used to sell addons not on the marketplace and not run a full site on. Aka they can have a public site showcasing with the options etc and even getting support there but it cant be a way for a serious site that has nothing to do with the developer to get a cheap license. Hell they could apply after they have published an addon and the large discount applies to the renewals side of it.
I am really disappointed some of the best developers here are now looking at possibly removing addons to reduce their burden rather than developing for those addons and being able to test on those addons, its so opposite and harmful because of the increased costs.
 
And there was me thinking things had improved a lot when @Jordan Miller with communications and community activity, I actually could see things improving a lot with better engagement with end customers then this whole chaos happens.

I do miss flexible width.

As Ballmer would say:

It is one of the reason several of your competitors were not options for us, they are so so valuable to a platform even if a customer doesnt buy an addon, its the perception that they can and there is a diverse ecosystem of addons as options.
Nearly all big platforms over the last decade have been powered by very strong developers adding value. iOS, Android, forum competitors all have got where they are because of developers. Windows Phone died because of the lack of developers. Keeping them onboard and happy is a huge deal, it wont necessarily affect huge enterprise customers but it has a big effect on your long tail customers.