tag matching problems for special characters like + (Trac #1089) #1089
Comments
|
trac user marcus wrote on 39514244-12-01 Both are falling foul of the rewrite rules here. |
|
brettp wrote on 39514519-10-15 (In [svn:3392]) Refs #1089: Added [B] flag to rewrite for tags. Won't work until apache 2.2.12. Cleaned up some query code in pagehandler(). |
|
brettp wrote on 39514520-10-31 This is a problem with how apache's mod rewrite redirects. The solution is to use the [B] flag to force escaping back references during rewrites. Unfortunately this flag is broken until Apache 2.2.12. (See: https://issues.apache.org/bugzilla/show_bug.cgi?id=45529). |
|
cash wrote on 39573088-08-27 The current solution causes a 500 internal server error with some Apache versions (2.0.52 for example). |
|
brettp wrote on 39579849-11-22 (In [svn:3417]) Refs #1089: Removed [B] flag from htaccess. This flag is wildly inconsistent in functionality and support in Apache. Will have to implement a solution in PHP. |
|
Title changed from |
|
Milestone changed to |
|
brettp wrote on 40766162-05-27 Fixed as part of the new htaccess rules. |
Original ticket http://trac.elgg.org/ticket/1089 on 39489778-05-11 by cash, assigned to unknown.
Elgg version: 1.5
Problem 1: If a user enters the tag "C++", it ends up giving a 404 error when the tag is clicked.
Solution: in the view "output/tags", double urlencode the tag string that is part of the url
Problem 2: If a user enters the tag "C/C++", it gives a 404 error. If the above fixed is used, it matches to the tag "C".
Solution:
in engine/lib/entities, function search_page_handler(), add this line before calling set_input():
$page = implode("/", $page);
The text was updated successfully, but these errors were encountered: