On our current project, we have a lot of content types (around 70+) with many many complex CCK fields and lots of modules that affect node types (comments, fivestar, node type, uploads, locale etc.). We also have a ton of nodes and revisions.

The module doesn't really seem to work. I bulk-changed some comment, fivestar and upload settings and after running for 10 minutes for each change, the overview page indicated that things were changed. But none of the comment, fivestar or upload changes actually changed when I go to edit the content types the old-fashioned way. Changes to identifying info and submission for settings seem to work but that's about it. And with many content types and about 50k+ nodes, the page actually never completes for more complex changes (it gives an error after about an hour, even though PHP for Apache is set to 750M and a 2 hour script timeout).

I am not sure if this is just something particular to us, but it seems like the module doesn't work in a setting with lots of content types and options - exactly the use case where it would be most helpful.

Comments

kerberos’s picture

kerberos commented

Shame on me for not reading the module readme, where it states that only comments and automatic node titles are supported (although comments still didn't work for me).

It's a bit odd though to show all these edit fields when the module cannot handle them. Why not just show what it can handle?

wulff’s picture

wulff commented
Version: 6.x-1.3 » 6.x-1.x-dev
Assigned: Unassigned » wulff

The speed of the module should not be affected by the number of nodes on the site. Updating the content type info is handled by node_type_save(), which only touches the node_type table.

The form arrays can get big when working on many content types at the same time, but a runtime of an hour does seems a bit high. What happens if you try editing the content types in batches of ten?

I have just tested the module locally with comment (core) and upload (core) enabled, and that seems to work as intended.

I'll test how the module works with fivestar, and add support if it doesn't work out of the box.

kerberos’s picture

kerberos commented

Let me install the newest version this weekend and try some tests and I'll get back to you.

Thanks!

kerberos’s picture

kerberos commented

I didn't have a chance to try the newest version but on 1.3 it took about 2 hours for the save to finish. I turned off comments for 3 of about 75 content types. They showed correctly on the overview page but when I went to:

/admin/content/node-type/[type-name]

comments were still enabled. :(

choy’s picture

choy commented

I have similar problems and can confirm as well some unwanted configuration changes after timeout crash :-(