Konuyu Açan
#1
Hi team,
Before describing the issue. I have a live XF site, located let's say at
The thing is as for example, if I look for certain option in the Search Options input in the admin area and pick one (let's say add forum/category)

It redirects to
I thought it was only in this search options area but I got the same if I switch styles (
Which makes me thing the async content load or update part is missing the board URL when fetching the content as full submissions works well.
I tested with browsers, mobiles, using the default RaxBoard style and one of the last ones (Modernius) and got the same result. So maybe it's something in the UX/UI part of the core.
These are 3 cases where I found this. I suspect it is affecting everywhere an async update exists.
Best Regards
Before describing the issue. I have a live XF site, located let's say at
http://mysite.com. I installed RaxBoard on a devrxb/ folder in my hosting so the RaxBoard board URL is pointing to http://mysite.com/devrxbThe thing is as for example, if I look for certain option in the Search Options input in the admin area and pick one (let's say add forum/category)
It redirects to
http://mysite.com/admin/nodes/create with a 404 response (not putting the screenshot, but is the typical not found page) But the thing is that is the XF site which is rightly giving me that response as you can see the devrxb/ part is missing.I thought it was only in this search options area but I got the same if I switch styles (
http://mysite.com/style/switch?style=11) or language (http://mysite.com/language/switch?lang=2) on the forum area. If I try to set the style or the language in the account preferences it's all good.Which makes me thing the async content load or update part is missing the board URL when fetching the content as full submissions works well.
I tested with browsers, mobiles, using the default RaxBoard style and one of the last ones (Modernius) and got the same result. So maybe it's something in the UX/UI part of the core.
These are 3 cases where I found this. I suspect it is affecting everywhere an async update exists.
Best Regards