Search

Hi all,

I've been working on our 404 page today, and whenever I hit an error it's near impossible to debug via the error itself, as it's so generic and ALWAYS seems to relate back to class.frontendpage.php.

Basically irelivant of what's wrong this line fails and throws the error, rather than giving me the actual error that led to it:

throw new SymphonyErrorPage(trim($errstr), NULL, 'xslt', array('proc' => clone $this->Proc));

At first I thought this was a 2.3.1 thing but it seems to be specifically related to the 404 page.

Worth issuing a bug report?

Yep ;o)

Will do - I've had a bad weekend with code and so half expect every bug I encounter to be something stupid I've done :p Which isn't entirely rare anyway…

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.3-5.6 or 7.0-7.3
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.5 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details