Bug-Clicking on category with space returns empty

This bug was mentioned some time back.  I am current with the SVN to 17418.  When you click on a category with a space (or space & space) in the name that has entries, say Our cars (4); which shows there are four posts in that category, it returns empty.  It returns empty on photos, and videos, and even third party modules.  I thought this bug had been addressed and fixed, yet I am seeing it.  Is there a solution to fixing this "space" bug.  For category Eggs & Cheese the URL shows this: /category/Eggs+%5Band%5D+Cheese (%5B; %5D; are brackets). and for a category Our Cars it shows /category/Our+cars; why isn't that %20 for a space?

I am impatient on this one.

do you get the same results on demo.boonex

Sometimes; let me capture some screens.  Maybe it is related to privacy.

I am not seeing the space problem on Boonex demo.  So then, let's say it is only me.  The URL is formed the same as on Boonex; so it is not the URL being formed incorrectly.  I checked every category listed under photos on the site; all the ones with spaces in the name return empty.  The rest do not.  So what should I be looking for?

I found this but I should have the fix; I need to check that ticket.

http://www.boonex.com/forums/topic/Blogs-category-Error.htm

OK, I just checked blog categories and the problem does not exist there.  I also noticed that the URL does not have the +; it is just a space.  Perhaps the fix was only for blogs.

And this could be related as well:

http://www.boonex.com/forums/topic/photo-Category-empty-.htm

I decided to see what would happen if I manually enter the link to the browse category replacing the + with %20 and it worked, the browse category page came up.

/m/photos/browse/category/Profile%20photos  loaded without a snap.

/m/photos/browse/category/Profile+photos returns empty.

Now, the URL on Boonex Demo site does have the +.  I am running Nginx and it does not use the .htaccess file, I am using the rewrite config file for Nginx as outlined by Boonex.  Perhaps I need to examine that file and see what the rewrite rules are.

is your forum working on nginx?

Also, replacing just the +  with %20 and leaving the [and] worked for /category/Eggs+%5Band%5D+Cheese . My problem is those pesky +

I don't see anything in dolphin rewrite rules.  I guess I could add a rule to change the %2B to %20 in urls.

Edit: why is it encoded this way in the first place?  Is it to create pretty URLs?  Where are pretty URLs created?  I am just as happy with %20 and %26 in the URL. Can I change this somewhere?  What good are pretty URLs if they don't work?

Yes, working fine; except for that problem when someone creates a title with an apostrophe.  I added the Dolphin rewrite rules; as outline by the Boonex tutorial.

I have a test site up on Arivxe running under Apache and the + works; the address resolves without issues as well as when I use the %20.  This might be due to me running Nginx.  Since I am seeing this problem in third party modules; is this + handled by the system?  If so, where?  I have looked in some of the more obvious places and did not see anything.  I need to form the URLs with %20 instead of + and my problem is solved.

At times; it is enough to make you want to kick the dog and cuss the cat.

Wait; I need to look at categories with this; I think that is the only place where I am having issues with the URL.

The problem is in some old standards when space symbols was encoded as plus sign, php urlencode function follows this standard:

http://php.net/manual/en/function.urlencode.php

Usually browsers/web-servers are backward compatible and handle it without any problems, it looks like some modern soft just ignore those old standards (which is good in some way, or we never get rid of this legacy).

Most probably all you need is to replace urlencode with rawurlencode in templates/base/scripts/BxBaseCategories.php.

Please let me know how it goes.

Thanks Alex.  I tried seaching on this on the web but did not find the reference you gave; did not think to search related to php; my education is very lacking.  Yes, changing to rawurlencode() solves the problem.  This may be related to using Nginx; so if anyone else is using Nginx and sees this problem; they will have the solution.

urlencode() is used in some 84 places in Dolphin.  Then there are the third party modules that uses it as well.  I will just look for issues related to this as they arrive.

Once again, thanks for your help, it is appreciated.

http://www.boonex.com/trac/dolphin/ticket/3133