single quote parse error ?
Development and Programming
hm, I am passing a custom field to php variable like this:
<?php
$body = '{body}';
?>Problem: when the body has single quotes (‘) in it, it cannot be parsed (eval() parsing error in core.functions.php)
I already tried this one, but it doesn’t solve the problem:
<?php
$myVar = <<< EOD
{my_ee_var}
EOD;
?>anyone got an idea?
TIA!
avroo, is there a reason why you don’t use double quotes instead?
nope, I tried both single and double…both result in a parse error…
Yes, nesting quotes is going to cause you problems; you’ll need to do some sanitization on the data so that you don’t run into this. You might consider moving this into a plugin so that you can work with it more comprehensively.
In any case, this is beyond what we can offer as technical support - did you want me to move it to the Plugins forum (if you’re going to go that route) or How To?
ok, clear. Then I am going to try to build a plugin, thanks!
Awesome, avroo. I’ve moved this for you. =)
I’ve used the heredoc with quotes successfully before without issue. That “should” work…
What happens if you put the closing PHP tag on the next line, after the EOD; (there should be nothing else except “EOD;” on that line, not even extra whitespace)?
-Matt
And again, too much time wasted of my life caused by some damn ENTER.
Matt, that did it. Thanks!
You could also use output buffering instead of HEREDOC, which will prevent PHP from attempting to parse variables. Consider the content:
I made $15 selling peanuts!If you put that into a HEREDOC without escaping the dollar sign, you’ll get an unexpected $end syntax error. Output buffering, however, doesn’t parse anything.
<?php ob_start(); ?>
{example_variable}
<?php
$str = ob_get_contents();
ob_end_clean();
?>Great tip! Makes sense now why the plugin docs use that. Thanks Derek.