It is common when using things like CCK to end up with node type names like content_development_log_note.

However, a content-type subscription with the subscriptions module prepends "type" and then truncates the string to 25 chars. so subscribing to the example content type above would yield "nodecontent_development_l", which of course doesn't match. This can be frustrating when you try to subscribe to a content type, hit submit, and then are presented with the page again with an empty checkbox that you just checked.

the simple short-term fix is just to widen the field and ask users to resubscribe to any content type they may have tried before that wasn't working:

ALTER TABLE subscriptions CHANGE COLUMN stype stype varchar(50);

This isn't a very principled fix, though. perhaps the test function could pre-truncate the string it looks for before checking for its presence in the subscriptions table?

Comments

dkg’s picture

gah. of course "nodecontent_development_l" above should have been "typecontent_development_l". sorry for the goof.

geodaniel’s picture

Version: 4.7.x-1.2 » 5.x-1.x-dev

+1 for fixing this, presumably also relevant to the latest version of the module?

jenlampton’s picture

Version: 5.x-1.x-dev » 4.7.x-1.4

I'm having a similar, but perhaps unrelated problem. When a logged-in user creates a new node of any content type they are supposed to be automatically subscribed to that node. Unfortunately, when a user creates a CCK node and clicks "submit" they get the white-screen-of-death. Creating new core nodes does not present this same problem. I tried your DB column widening trick but it didn't solve my problem. I think my CCK type names aren't more than 21 characters long... yet.

Leeteq’s picture

Subscribing.

bdragon’s picture

Status: Active » Closed (fixed)

5.x-2.0 version is a complete rewrite, any bugs in it are new, all prior versions becoming unsupported, closing for that reason. This is fixed under the new table format. See subscriptions_update_3() for more information.