Search function isn't working anymore

[Amoxil44]

weird issue:
(no custom urls and we rebuilded already search index. )

 

if I try to search "apex legends"

this pops up:

url: search/?do=quicksearch

 

If I set this to default as landing page, the search is working "apex legends"

search/?q=apex%20legends&quick=1

 

 

Any idea?

 

Edited November 22, 2023 by Amoxil44

[Marc]

Do you have an friendly URL changes? If so, please try reverting those and testing again

[Amoxil44]

36 minutes ago, Marc Stridgen said:

Do you have an friendly URL changes? If so, please try reverting those and testing again

no as I wrote. No URL changes AND it's working when set to default. But thats obv no solution, landing page would be  search then ^^

[Randy Calvert]

I had this happen on a custom theme. Have you tried this with a default/stock theme?  Have you also tried disabling any third party resources (applications or plugins) to rule them out as a problem area?  

I tried this on a few different IPB powered sites and can’t replicate it. Seems to be isolated to your specific instance. 

[Amoxil44]

1 minute ago, Randy Calvert said:

I had this happen on a custom theme. Have you tried this with a default/stock theme?  Have you also tried disabling any third party resources (applications or plugins) to rule them out as a problem area?  

I tried this on a few different IPB powered sites and can’t replicate it. Seems to be isolated to your specific instance. 

yes I tried it. Disabled everything, and yes on default theme the same.

[Randy Calvert]

I'm not an IPS staff person, but based on all the above, my guess is one of them would need to login to your instance and look.  To save some time, I would suggest making sure your info in the client area is entered and up to date just to save some time waiting.  

Edited November 22, 2023 by Randy Calvert

[Jim M]

Would check your .htaccess for any custom URL rewrites or redirects. Otherwise, we would require access to your community:

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. 

 

[Daniel F]

What's the error code you're seeing?

[Amoxil44]

2 hours ago, Daniel F said:

What's the error code you're seeing?

Error code: 2S100/1

[Amoxil44]

it's very strange that it's 100% properly working if set to default 

[Jim M]

23 minutes ago, Amoxil44 said:

it's very strange that it's 100% properly working if set to default 

What are you setting as your default application?

Please also see my comments below:

4 hours ago, Jim M said:

Would check your .htaccess for any custom URL rewrites or redirects. Otherwise, we would require access to your community:

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. 

 

[Amoxil44]

41 minutes ago, Jim M said:

What are you setting as your default application?

If I set "System" and "search" (screenshot) both to default, the search is working as usual.

6 hours ago, Amoxil44 said:

weird issue:
(no custom urls and we rebuilded already search index. )

 

if I try to search "apex legends"

this pops up:

url: search/?do=quicksearch

 

If I set this to default as landing page, the search is working "apex legends"

search/?q=apex%20legends&quick=1

 

 

Any idea?

 

somehow it removes the search as you see in the url

if I try to search "apex legends"
the URL I get is url: search/?do=quicksearch

BUT

if I set System and search to default as mentioned above. 

I try to search for "apex legends"
search/?q=apex%20legends&quick=1

 

[Marc]

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.

 

[Amoxil44]

On 11/23/2023 at 12:26 PM, Marc Stridgen said:

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.

 

Any eta or dirty fix in the meantime?

[Marc]

22 minutes ago, Amoxil44 said:

Any eta or dirty fix in the meantime?

We are unable to give ETAs on bug items unfortunately. At present this is an open bug, so there isnt a fix to give.

[Daniel F]

I can't reproduce this on my environment, so I had to create a ticket to investigate this further on your community.