[
https://issues.apache.org/jira/browse/JSPWIKI-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621600#action_12621600
]
Dirk Frederickx commented on JSPWIKI-327:
-----------------------------------------
When the USER would use the Find! button on the search screen, the URL gets
refreshed. Such that the back function works again properly. However, this is
very user-unfriendly way. (only for nerds)
A possible solution could be to use the hash of the url/location to 'store'
intermediate ajaxed queries.
EG
Search.jsp?query=original-query#latest-ajax-query
When the #hash is present in the url, the search page could make the correct
query.
Note that also for the text-hihghlight function, the ajax-search-query is
needed. In that case the last search query is temporary stored in a cookie. The
hash-approach could of course here also be used.
= = = =
BTW, when ajax search is considered to heavy for the server, we'd better build
in some admin property (does it not exist yet ?) to block ajax requests. Do we
have some stats on jspwiki.org -- it seems to me that is reacts pretty snappy
on ajax-searches, either in find or in the navigation box.
> Going back to Search always returns to the page with results 1-20
> -----------------------------------------------------------------
>
> Key: JSPWIKI-327
> URL: https://issues.apache.org/jira/browse/JSPWIKI-327
> Project: JSPWiki
> Issue Type: Bug
> Components: Core & storage
> Affects Versions: 2.6.1
> Reporter: Bert Koorengevel
> Priority: Minor
> Fix For: 2.8
>
>
> I'm currently using v2.4.102 and am considering upgrading to v2.6.3 as used
> by www.jspwiki.org, but found a rather annoying issue with the improved
> search engine.
> Search for a keyword with a lot of hits. Go to any but the first page with
> results. View any page, then do "back" in your browser. In v2.4.x you'd go
> back to where you were in the search results, because that was in the url.
> Now the url doesn't hold that info, so you're thrown back to page 1 of the
> results.
> Known workaround: always open pages in a new tab.
> NB: I'm using FF 2.0.0.12 if that makes any difference.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
