Thread

I filed this as a bug, but the tester said it worked fine in his build, so thought I’d raise it here…

EE v2.1.3 build 20101220

I create an entry with the title:
“My title with + and . in”

url_title generated:
my-title-with-and-.-in

In the template I output {url_title} as:
my-title-with-and-.-in

Also in the template I output the segment variable {segment_2}:
my-title-with-and-_-in

The 2 variables parse the full stop differently, the browser url had the “.” so this should be allowed in the segment variable.

It’s easily avoided as I’ve told the client to edit any fullstops out of the url_title, but I’m just trying to identify if it’s a bug due to specific EE parameters/setup?  Or what’s causing it under my build.

Extensions wise, I’ve got Low Seg2Cat and Last Segment installed, I haven’t yet had a chance to try disabling these to see if that could be the problem (the segment variables getting manipulated by an add-on).

Hi Twobelowzero,

I’m not able to replicate the problem on a 2.1.3 installation myself, although I will say that there is a difference between our builds. You’re running 20101220 and I’m running 20110411. Either way, I would always recommend upgrading to the latest version for security and maintenance.

Short of that, I wonder if this may have something to do with your config. Could you open up your config.php file and let me know what value you have here?

$config['permitted_uri_chars']

Value is:
a-z 0-9~%.:_\-

I’ll suggest it to the team, but so close to launch it may not be an option.

Many thanks.

I hate to admit that I also can’t reproduce, but I’m on 2.2.1

I think upgrading may make the most sense in this case, to rule out any issues there.