rsobj.php // version 2.11 Causing Issues

When using echo eval('?>' . $Recordset1->getColumnVal("example") . '<?php '); it breaks in version 2.11.
However, it works perfectly in rsobj.php // version 2.8 which was the last copy I had when it was working without issue.
What changed?

I'm confused by the code you are using? What is the purpose or context?

I feel like it should just be:

echo($Recordset1->getColumnVal("example"));

Using eval to show some php coding and html that is stored in a database which is being used for a template. It worked great and then something changed with the update and stopped working. So there is a conflict with eval() and rsobj.php in version 2.11

I don't think you can eval "<?php" or "?>". I don't think it has anything to do with the version of the rsobj.php file.

Forget eval(), next issue is it breaks HTML code stored in the database. So if you use an HTML WYSIWYG Editor to store content in your database it displays html code as text. If includes are used and contain any html in the code it displays as text. The other version displayed html as html. There is something definitely wrong with rsobj.php and worth reviewing. Even if used as <?php echo($Recordset1->getColumnVal("example")); ?>

Yes, this version has built in Cross Site Scripting protection that will automatically encode html included.

You can turn off the encryption by passing an extra "true" parameter to the method like:

<?php echo($Recordset1->getColumnVal("example",false)); ?>

Can this be turned off in rsobj.php instead of passing an extra parameter?

Parse error: syntax error, unexpected ',' when used <?php echo($Recordset1->getColumnVal("example"),true); ?>

Here is a version 2.12 of rsobj.php. It allows you to set the default for cross site protection in the object on line 11 site wide. You can still override it for individual recordsets or getColumnVal() calls.

I've updated the syntax above to reflect the new v2.12 syntax, but you can also just change the global setting.

Now that made things a lot easier. Thanks a million.