Webhelp Responsive search breaking
Posted: Wed Nov 14, 2018 2:57 pm
Hello,
I have been customising my own templates, including using a custom CSS, and more recently, editing the wt_index.html (and related) files. This has all been going well and I'm impressed with how powerful oXygen is for this.
However, I made the discovery that the search function has broken somewhere along the way. Instead of getting results, it only appears to search in one topic, and return one result (as long as the topic contains the search term - otherwise it returns nothing) The single result is labelled as "null" with a link to the topic, but no other context. Clicking on the topic link takes me to the page with the search term highlighted as per a regular search.
Before I started editing the template's html files, I was getting this issue so I don't think it is related to that. One thing I have found, which makes no sense, is that if the footer is really basic or the default, then it works fine. However, if I put in a slightly more complex footer - which renders fine - the search breaks. By complex, I mean anything other than plain text. Even a <BR> tag breaks it. To clarify - this includes fragments in the text box parameter itself, as well as custom footer files - I have tried both.
I would have probably settled for having to have a really basic footer, however, I've been editing the template's html files now. And now, even when I completely delete the footer (unsetting the parameter), the search remains broken. I have put a lot of work into the template and don't want to start over, and given how bizarre the behaviour is, I have no idea where to begin looking in my changes to try and fix this.
Have you come across this before, or do you have any suggestions on the sort of areas I should be looking at? Given the unrelated nature of the search functionality, and the footer, it does sound like there is a bug somewhere.. but a workaround in the meantime would be fine.
Thank you very much!
I have been customising my own templates, including using a custom CSS, and more recently, editing the wt_index.html (and related) files. This has all been going well and I'm impressed with how powerful oXygen is for this.
However, I made the discovery that the search function has broken somewhere along the way. Instead of getting results, it only appears to search in one topic, and return one result (as long as the topic contains the search term - otherwise it returns nothing) The single result is labelled as "null" with a link to the topic, but no other context. Clicking on the topic link takes me to the page with the search term highlighted as per a regular search.
Before I started editing the template's html files, I was getting this issue so I don't think it is related to that. One thing I have found, which makes no sense, is that if the footer is really basic or the default, then it works fine. However, if I put in a slightly more complex footer - which renders fine - the search breaks. By complex, I mean anything other than plain text. Even a <BR> tag breaks it. To clarify - this includes fragments in the text box parameter itself, as well as custom footer files - I have tried both.
I would have probably settled for having to have a really basic footer, however, I've been editing the template's html files now. And now, even when I completely delete the footer (unsetting the parameter), the search remains broken. I have put a lot of work into the template and don't want to start over, and given how bizarre the behaviour is, I have no idea where to begin looking in my changes to try and fix this.
Have you come across this before, or do you have any suggestions on the sort of areas I should be looking at? Given the unrelated nature of the search functionality, and the footer, it does sound like there is a bug somewhere.. but a workaround in the meantime would be fine.
Thank you very much!