[SOLVED] Display XSLT errors in frontend
This is an open discussion with 12 replies, filed under Troubleshooting.
Search
Well, what are the differences in setup between the two servers? Between PHP on each server.
Dunno. Probably a lot. I didn't really want to compare each phpinfo()
item :)
Maybe display_errors?
I've set these in my .htaccess:
php_flag display_startup_errors on php_flag display_errors on php_flag html_errors on php_flag log_errors on
Not all servers allow php flags in the htaccess. Do you have access to php.ini?
I can confirm errors are shown because if I have a PHP error it appears. XSLT errors don't appear.
You're logged in right? =)
(this has happened to me many times before)
Yes, I am. It's very frustrating. It can happen that one XSL file isn't corectly uploaded to server (only partial) and it throws an XSLT error that I am unable to see.
@ anybody Is there an other place where XSLT errors are logged?
Have you tried to increase the memory limit? I remember that I once had problems with blank pages when it was too low.
It's 256MB. No luck here.
Thank you all for your input. If you will ever have any other ideas, please post here.
Wooooaaahaaa ... Found it !
It's from Page Headers extension. If there was an XSLT error, Page Headers would wrongly parse the output thus rendering crap. It seems this bug is fixed in latest version.
Thank you all for your help.
This thread can be closed.
Ah whoops, that's even my extension :( glad you figured it out. I probably should have mentioned that issue in the change notes.
Create an account or sign in to comment.
On local dev XSLT errors are rendered and displayed by Symphony.
On remote server, these aren't displayed, just a blank page.
Any ideas why? Thanks!