-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Site Search not taking into account Path Mapping #1358
Comments
/go link is an expected behavior to log a click action. |
I will take a look, but the Location Response Header shouldn't affect the Path Mapping. At least for admin and Fess search page, this works. But doesn't work for the Site Search Javascript. |
The response of /go returns url replaced by Path Mapping at Location response header. |
What is Process Type of Path Mapping? |
Displaying. |
Will this require a rebuild of fess, or is there something I can quickly change? |
This needs to modify FSS JS, not Fess.
|
docker doesn't install on my machine for some reason, or it is just taking too long. Any idea when this can be done in your timeline of things? |
I noticed the issue has been closed, but FSS Generator doesn't seem to have the fix yet. Can this section of the js be changed without changing anything else, and what would it need to be changed to?
|
Not released yet... |
Released. |
I am using FileSystem Index. Path Mapping works when searching from admin and Fess Search Page, but Path Mapping doesn't seem to work from Site Search. Are there any configurations that need to be setup to allow this?
This is what works from admin:
Regexp.
file:/E:/Websites/test.site.gov/Attachments/orders
Replacement
https://test.site.gov/Attachments/Order
EDIT:
Also, when clicking a link on Fess Search Page it should be a url to this path:
but the link takes me to
As mentioned in another post, this link should include /fts/go instead. When I manually add this to the url, it takes me to the http url, which isn't open to the public. If I add https, then it takes me to the correct location. It looks like the correct url is changed to the /go/ url after clicking the url.
The text was updated successfully, but these errors were encountered: