Editing Breadcrumbs layout problem

[RixStix]

zc156 or zc156a


Somehow breadcrumbs got fouled up and I tried to reset them to the default

If I copy/paste what is shown as "default"

 :: 

and click UPDATE

This

 :: 

is shown in the "value" column and

that is what is displayed.  :: 

IF I copy the breadcrumbs code from my current, live site

&nbsp;<i class="fa fa-angle-right"></i>&nbsp;

This is what appears

Home&nbsp;<i class="fa fa-angle-right"></i>&nbsp; MyCategory

instead of something pretty.

zc156a install with demo data
drop tables
import 154 database
run zcinstall
install bootstrap template but after getting things looking nice found out is not ready for 156 with the debug files generated
change to classic responsive

[mc12345678]

Result of the admin sanitizer. Thought I had seen something like that happen with other configuration menu entries, but forgot to put out some sort of bug report. At moment not sure which sanitizer in which to place the field, but will take a look unless someone else jumps in.

[RixStix]

TNX for confirming is isnt some dumb mistake on my part.

[mc12345678]

TNX for confirming is isnt some dumb mistake on my part.

So the sanitization is that the configuration_value is strictly sanitized which is like the complete encoding of anything you could think of, admin/includes/init_includes/init_sanitize.php refers.

Thing is, I'm not entirely sure what the thought was behind doing so, which makes it difficult to suggest anything that is not strict or some way on the store front to "undo" what was done... I recall seeing it have some effect to something else I was doing, but as I said I had moved on to the then main issue for me.

The other "difficulty" is determining which other sanitization would be suggested based on the possibility/likelihood of what could be included in setting a configuration value. I also haven't looked into the new configuration field to see what it's purpose is to perhaps see if it has any factor in this process.

Anyways, maybe moving it to the grouping including PRODUCT_NAME_DEEP_REGEX?

My thought behind that is that I thought that the product description regex would support scripts being in the content, which perhaps generally speaking may not be in the "standard" configuration value, and the words and symbols regex seems like it may clean too much out yet still... hopefully though some further guidance/correction of my recommendation will soon come. :/

[RixStix]

so the sanitizer is sanitizing the recommended default setting?

[mc12345678]

so the sanitizer is sanitizing the recommended default setting?

When trying to store the recommended default setting, yes it then sanitizes that. Technically to get the "desired" result of the default, I think one would have to type in a space, two colons and then another space.

But then, if it were to be edited again, the same text would again have to be added...

Now, for some reason I thought I remembered something like this in ZC 1.5.5, but I can't recall and am away from my "tools".

[RixStix]

If that is all that is needed, then I would suggest putting that in the default text so that it can be copied/pasted right above there in the field. sorta like what I did in the first effort to fix things, or not allow things to be edited if it requires knowledge not readily available to the average user.

The expectation was that copy/paste would work but I do understand catching every teeny glitch is next to impossible.

FYI: adding spaces has no effect other than add spaces into the breadcrumbs

[RixStix]

BTW: preceeding space gets removed. trailing space stays. I misunderstood what you said. I thought you meant 'insert' a space instead of remove the code and just use a space.

[mc12345678]

BTW: preceeding space gets removed. trailing space stays. I misunderstood what you said. I thought you meant 'insert' a space instead of remove the code and just use a space.

No, you understood correctly. I just tried it myself and it appeared actually to remove both spaces. At least when I went back in to review the change.

After I posted that suggestion I also got to thinking about the "conversion" process, but typically

 

is presented/needed when there is an existing space before the character as multiple spaces in html are treated as a single space, but each

 

is treated as its own space.

So, the "work around" to this at the moment without modifying the sanitizer script is to execute the following sql in tools->Install SQL Patches:

UPDATE configuration SET configuration_value = ' :: ' WHERE configuration_key = 'BREAD_CRUMBS_SEPARATOR';

This would allow you to also use your "pretty" divider by substituting the applicable code for

' :: '

leaving/using the single quotes as applicable.

As said though, without modification of the sanitizer file admin/includes/init_includes/init_sanitize.php adding anything within the configuration options that includes characters such as: &, <, >, ', or " (those items encoded by the function htmlspecialchars) will get modified (double encoded essentially) and cause the display that you described above.

[RixStix]

No, you understood correctly. I just tried it myself and it appeared actually to remove both spaces. At least when I went back in to review the change.

After I posted that suggestion I also got to thinking about the "conversion" process, but typically

 

is presented/needed when there is an existing space before the character as multiple spaces in html are treated as a single space, but each

 

is treated as its own space.

So, the "work around" to this at the moment without modifying the sanitizer script is to execute the following sql in tools->Install SQL Patches:

UPDATE configuration SET configuration_value = ' :: ' WHERE configuration_key = 'BREAD_CRUMBS_SEPARATOR';

This would allow you to also use your "pretty" divider by substituting the applicable code for

' :: '

leaving/using the single quotes as applicable.

As said though, without modification of the sanitizer file admin/includes/init_includes/init_sanitize.php adding anything within the configuration options that includes characters such as: &, <, >, ', or " (those items encoded by the function htmlspecialchars) will get modified (double encoded essentially) and cause the display that you described above.

TNX MC12345678

I really avoid adding custom code or performing one-off commands as much as possible, so I will just live with the current default which prevents leading spaces. That's only a minor cosmetic issue which no one will know but me.