1 users online. Create an account or sign in to join them.Users

Search

After uploading 700 entries (using importcsv extension), i get this fatal error when entering ?debug;
Anybody knows what's happening here?

Cheers

Attachments:
Schermafbeelding 2011-08-18 om 14.10.25.png

You can try deselecting some elements in your data sources for that particular page, that might help. You could also use pagination.

You're getting that error because you are running out of resources, memory. It's because of the way Symphony creates XML, it's rather resource intensive.

I already used pagination, limiting the results to 10 instead of 40 had no effect.
After removing another heavy datasource from the page it works again, but still takes some time to load... So i guess there's just to much data.
Normal site preformance is exelent though...!
So whenever i need the devkit, temporarely removing one datasource will do fine.
Is there no way to boost the devkit performance?

Thanks

The last time this happened to the debug devkit, it was a problem with parsing include/import elements in the XSLT — the devkit provides, in the right column, a list of utilities used in your code. It does this by parsing the XSLT, and previously it would get into a circular loop and die. Which version of the Debug Devkit extension are you using?

If you put a return false just inside the buildJump method, this should prevent the sidebar being built. That would eliminate one possibility.

The only link that is not working is /?debug=xml
All other direct links to utilities and parameters in the sidebar, work fine...
(e.g ?debug=params, ?debug=result, ?debug=/workspace/utilities/master.xsl) I added the return false but that didn't seem to do anything.
I can live with this inconvenience for this project, guess the xml just contains to much data?

Thanks again

-edit: I'm using symphony 2.2.3 and included (=latest?) devkit

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.2 or above
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.0 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details