I was excited to try the new CKEditor integration, but after having tried this with two separate node types (one with PHP filter and one with Filtered HTML controlled by CKEditor), I am getting the same results either way, as soon as I try to save a node with two other nodes (of a different type and not referencing back to the first) freshly embedded, Apache crashes. I don't see any further messages to explain why (memory exhaustion or otherwise).

Comments

glottus’s picture

glottus commented

For further clarification, I was trying to embed nodes created by the Filebrowser module, and as that is the only need I have for embedding nodes, I haven't yet tried it with other (CCK) content types.

emackn’s picture

emackn commented
Assigned: Unassigned » emackn

Can you try with other types to see if the error is isolated to the file browser types?

Which version of the file browser module are you using?

Can you check your apache log and watchdog tables for the error being thrown and post it here?

glottus’s picture

glottus commented

First off, I'm using Windows and a XAMPP installation (version 1.7.1) for development.

I've done a little poking around, and it seems to work just fine with standard Page nodes and other CCK types.

When I attempt to embed nodes of the Filebrowser type (upon creation or updating the container node), I immediately get an "Apache HTTP Server has stopped working" message, and closing that, I am redirected back to the node edit form (apparent because of new warnings at the top of the form relating to the node-locking module - and yes, I have tried it with that module disabled with similar results). I notice that I don't actually have to restart Apache myself, it does it automatically, I guess.

The first line in the Apache logs at the time of the crash is:
[Tue Jul 27 16:11:57 2010] [notice] Parent: child process exited with status 3221225725 -- Restarting.

The Watchdog table does not seem to capture any event relating to this.

I also notice, if I ignore the above node-locking warnings and such by navigating to /admin/content/node, that my node HAS in fact been created, and clicking on it, I see that the node in question (with embedded Filebrowser nodes) actually does work after all, browsing widget and all. I also discovered, by accident, that if the embedded Filebrowser node doesn't actually have a path with files in it (therefore NOT rendering the usual filebrowser widget), this crash does not occur.

On that note, I think I will try to post this over there as well.

I'm using an older version of Filebrowser because of issues that module has recently with sorting. The filebrowser.info file says its version 6.x-2.x-rc12 of that module, but the Drupal packing script says 6.x-2.x-dev.

strategictech’s picture

strategictech commented

You can fix this by setting the
pcre.backtrack_limit and pcre.recursion_limit lower!

you can do this in settings.php I opted to set it in my .htaccess like so:

php_value pcre.backtrack_limit 100
php_value pcre.recursion_limit 100

mrharolda’s picture

mrharolda commented
Issue summary: View changes
Status: Active » Closed (won't fix)

As of 22 September 2014, we no longer support the Drupal 6 version of Node Embed due to the small install base (< 15%) and more importantly: general lack of time.

If you would like to help and maintain the 6.x branch until Drupal 8 is released, please apply for co-maintainership!