Serendipity Forums

I encountered a strange problem when I try to enable spartacus.

If I enable it, I first can change the settings. I leave
everything to the defaults.

Then, going to plugin admin page and trying to install a new plugin,
spartacus is apparrently correctly fetching the XML file:

[..]
Sidebar Plugins

Trying to open URL package_sidebar_en.xml...
Fetched 63084 bytes from the URL above. Saving file as /home/langd/.html-data/blog/templates_c/package_sidebar_en.xml...
Data successfully fetched.
[..]

but thats it. I do not see any list of plugins to install.
If I reload the page, I get a slightly different message:

[..]
Trying to open URL package_sidebar_en.xml...
Fetched 63084 bytes from already existing file on your server. Saving file as /home/langd/.html-data/blog/templates_c/package_sidebar_en.xml...
[..]


same for event plugins:

Event Plugins

Trying to open URL package_event_en.xml...
Fetched 156571 bytes from the URL above. Saving file as /home/langd/.html-data/blog/templates_c/package_event_en.xml...
Data successfully fetched.

and

Trying to open URL package_event_en.xml...
Fetched 156571 bytes from already existing file on your server. Saving file as /home/langd/.html-data/blog/templates_c/package_event_en.xml...

If I save the settings of spartacus again, it deletes the two files,
but then the first message appears again.

Now, the worst thing of all, if I just try to view the blog, it is gone.
I only get an empty page. I can still access the admin-menu, but
the blog itself is gone.

If I remove the spartacus plugin, everything seems to work again.

I am using s9y v 0.9.1 with postgresql.

Cheers,
Daniel

Please try to enable your PHP's "display_error" directive and/or look inside your PHP error log.

It seems that some component is causing either a segfault or a fatal error.

Which PHP version are you running?

Regards,
Garvin

That did the trick, I should have checked right away. In the error log I found, that I exceeded the default memory limit of 8MB with PHP. I extended the limit for s9y to 32MB and now it is working. I have also noticed, that this problem was found by another user and there is a thread about this. Apparently some plugin seem to consume lot of memory. However until now I only used standard plugins, none that are not distributed along with s9y.

Anyway extending the limit resolved the issue.

Thanks,
Daniel

Hm, okay. Actually s9y 0.9 should've been able to make memory problems go away, but aparantly there's still something interfering. I'll try to spot this out somehow...

Regards,
Garvin