Thread

I tried dropping in that invalid php code in my button test template, and it generated no errors - the page just came up with the 3 buttons.

Would php errors be a server setup again, or in EE?

It could be a combination - first go to Admin -> Utilities -> PHP Info and look for display_errors.

If they’re not allowed there then it’s a server setup thing.

If they are enabled, then check Admin -> System Preferences -> Output and Debugging and make sure PHP Errors are set to show to superadmins.

Hi - getting the hosting company to compile openSSL into the php seems to have worked. I’m getting encrypted buttons now.

Regarding the php errors, I checked, and display_errors was set to on, and Debug Preference is set to “1” but using that bit of garbage php code from the earlier message, I still get no error of any kind when I render the template. As a matter of fact, when I view source the test page the garbage php is on, there is nothing where the php should be. Though I guess that’s a whole other topic…

Are you logged in on the front-end? Try temporarily setting errors to show to all and see if they show up.

Glad you got the initial issue working, but I’d like to see you work through this as that should have generated an error - so we could potentially avoid such baffling troubleshooting in the future by getting errors showing. =)

Hi - sorry, I got really busy with another client site and forgot about following up on this.

Setting debug preferences to “Show to All” did indeed generate an error. Setting it back to show for only SuperAdmins, I still do not see any error. I have done all of this while logged in, and rendering the test template using the “View” link in the Template Management page.

Motomasa:

If your host allows override with .htaccess, we can try to force them.  Can you add the following to a .htaccess file and upload to the public_html folder?

php_flag display_errors On
php_flag error_reporting E_ALL

Visit the page with the garbage PHP in it so we can see if that throws an error.

-greg

Motomasa,

In your site templates you are missing the closing tag for the BODY.

IE is a sensitive beast and oversights like this can cause unexpected behaviour in a lot of cases.

Please correct this and double check if it has fixed your issue with IE