In Content Server mobile view, 'Next' URL is not formed correctly when search query contains user tag

Bug #1519606 reported by deviantcrash on 2015-11-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Undecided
Unassigned

Bug Description

Calibre v2.44.0, Windows 7

Create a custom user tag field named User1 which is set to either: read or unread. Then initiate a search query for User1=unread:
http://192.168.2.126:8080/mobile?num=25&search=%23User1%3A%3Dunread&sort=date&order=descending

Search result content is correct, but the Navigation links for 'Next' and 'Last' are incorrectly formatted:
<a href="/mobile?search=#User1:=unread;order=descending;sort=date;num=25;start=26">Next</a>

If I replace the '#' with '%23', then link works correctly:
<a href="/mobile?search=%23User1:=unread;order=descending;sort=date;num=25;start=26">Next</a>

Fixed in branch master. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased

Changed in calibre:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers