Thread

EE v2.5.2

Hi,

I have configured a site to use my own table prefix. I am now trying to enter content with information about the cookies the site uses, but I have kept the cookie prefix as ‘exp_’.

As a result when the entry is submitted via the control panel it is changing the ‘exp_’ in my content to the table prefix.

Eg:
New table prefix = ‘abc_’

I enter some content using the control panel ‘...the cookie exp_allow_cookies steals all your credit card details….’.

Now when I load the page, or go back and edit the entry it reads ‘...the cookie abc_allow_cookies steals all your credit card details….’.

In the short term I can fix it by going direct to the data in the database and changing it. But obviously I’m going to need to do this every time someone changes the content. (Fortunately this isn’t a page that will change often.)

I just wondered if there was a setting somewhere I can use to tell ExpressionEngine not to parse out the exp_ in the content.

Thanks.

Hi fcb66,

Interesting for sure! What happens if you change the cookie prefix to something other than exp_?

Would you mind describing your experience in a Bug Report?

I just wondered if there was a setting somewhere I can use to tell ExpressionEngine not to parse out the exp_ in the content.

No setting to change, something like this is being borked up in the Core, which is where the bug report will come in handy!

Thanks for bringing this to our attention!

Cheers,

Hi Dan,

I’ve just tried this out on a completely fresh install of 2.5.2, (locally on MAMP), to make sure it’s nothing to do with my setup and it is still behaving the same.

I installed it with the table prefix ‘abc_’ and the cookie prefix ‘xyz_’

If I enter content with ‘exp_’ in the text it is changed to the table prefix.

It works fine if the content contains ‘abc_’ and ‘xyz_’ also the code that is making the replacement is case sensitive, ‘Exp_’ is not changed on submitting the content.

Bug report raised:
https://support.ellislab.com/bugs/detail/18186

Thanks for your help.

fcb66,

Bug report raised:

Excellent! Thank you for taking the time to replicate and report. I can tell you, the Engineers were talking about this report just this morning, so it got there attention!

Is there anything else I can assist you with?

~

Hi Dan,

I think that covers it for now, I can get away with using the capitalisation until a fix is available.

Thanks

Fantastic!

If anything else crops up, just let us know.

Cheers!