Thread

Some of our entry titles have an “&” in them. When on the edit screen in the CP, depending on how I search and include the “&”, I get unexpected behavior. Here are some scenarios of searches performed on the edit screen. Let’s assume I have a number of entries that have titles that start with the phrase “About Team & Company”.

Searches performed and results:

“About Team &”
If I stop entering in characters directly following the “&” then results get returned and I can click through each entry to edit them.

“About Team & Company”
No results are returned. Basically as soon as I add characters past the “&”, the results go away.

“About Team & amp; Company” (space after ampersand intentionally added for forum post)
If I encode the ampersand in my search, then all results get returned. However if I click to edit any of the returned entries it takes me to an error page with this error: “You are not authorized to access this page”. In looking at the URL of those generated edit links, none of them contain the right entry_id within the URL.

Can anyone else duplicate this behavior?

Hi, Casey.

I tested this in my EE 2.1.5 beta install, and it works just fine for me.. had two entries with About Team & - one with About Team & Stuff

searched for About Team & Stuff, it returned one entry and I was able to edit it.

That’s not to say it might not be an issue in the version you’re using, but I can’t replicate it here.

Can you tell us which version/build of EE2.x you’re using? See EEWiki:// HowTo Determine My EE Version

Ah, sorry I forgot to mention the build. This is on EE 2.1.3 build 20101220. Are you able to test on that build? Also in our case we have multiple entries that start with the same phrase, although it may not matter. i.e. About Team & Stuff One, About Team & Stuff Two, About Team & Stuff Three.

Hi Casey,

However if I click to edit any of the returned entries it takes me to an error page with this error: “You are not authorized to access this page”. In looking at the URL of those generated edit links, none of them contain the right entry_id within the URL.

This in particular is a bug and you can apply a fix mentioned here

In terms of the search I tested on EE2.1.3 and latest build 20110411 and it worked as intended.
Maybe try to upgrade to latest build so we can rule that out.