By: Edward Caissie
Great tip! This is something well worth looking at to make sure my themes (and also those being reviewed by the WPTRT) catch this issue. Thanks.
View ArticleBy: Otto
The explanation is a tad confusing. It’s not the printf or the sprintf or WordPress doing anything weird here. It’s the fact that $s was in double quotes. For example, this won’t work: $s = 123;...
View ArticleBy: Philip Arthur Moore
To avoid having to use a backlash in your translatable text, use this instead with single quotes: 'isn’t' Cheers.
View ArticleBy: Philip Arthur Moore
Doesn’t seem to be working. That should have read: rsquo; A & should come before it. Cheers.
View ArticleBy: Mike Little
Hi, you said instead, it was being parsed by WordPress., To be accurate, it is being parsed by PHP not WordPress. I always make a habit of using single quotes around strings unless I explicitly want it...
View ArticleBy: Mel
I always make a habit of using single quotes around strings As do I – 999 times out of 1000. It’s just that the one time I didn’t, I ran straight into the the fact that $s has a special meaning in WP –...
View ArticleBy: Mel
Escaping the single quote using \' seems far safer than introducing special characters into a string – especially one that is meant to easily translatable.
View ArticleBy: Mel
So why can’t WP 3.4 or a later version move toward using something like $wp_s with backwards compatibility for &s? That would seem a lot safer. From a coding quality perspective, it’s pretty dire...
View Article
