The subscription option shows for my blog type, but not for a custom node type. That type does include flexinodes. I don't think having flexinodes is relevant. A custom node type issue?
Thanks
The subscription option shows for my blog type, but not for a custom node type. That type does include flexinodes. I don't think having flexinodes is relevant. A custom node type issue?
Thanks
Comments
Comment #1
carl ditzler commentedI'm also using clean URLs and perhaps that's the issue?
When viewing an article with a URL like /article/title, subscription is not an option.
But, if I edit the same article which has a URL like /node/1/edit then subscription is an option.
Comment #2
carl ditzler commentedUpdated title, this looks like a clean URL issue.
I would be interested if someone has the same issue or can duplicate.
Comment #3
Rick Cogley commentedMine is working for nodes with clean URLs. The subscribe post link registers in the browser status bar as being the link to node/number and not the alias, however, and the name in the Address box is the alias.
Comment #4
carl ditzler commentedok, perhaps this is an issue with flexinodes. I do not understand how a flexinode could be an issue because it is just a node and subscriptions apply to "node." I can subscribe if I enter the correct URL, but subscription (subscribe or unsubscribe) does not appear with the node. Subscription options do display on blogs.
Comment #5
dziemecki commentedThe action performed when a node action occurs depends upon the node "type". Type "blog", for instance, has a slightly different handling than type "forum". I don't know much about flexinodes, but I suspect that it's simply passing an unhandled node type.
Anyone care to shed some light on this module?
dz
Comment #6
dziemecki commentedThis doesn't seem to be particularly important to anyone, right now. I'm not using flexinodes, but if they are that similar to regular nodes, anyone who want subscriptions to work with them should just add a "case 'flexinode': // pass thru" over all the node cases and add a few "&& $stype == 'flexinode'" to see if that works for them.
I'm going to retire this bug unless someone else chimes in with an interest. Afterall, the module can't be all things to all people.