My scenario is that I have a db of user-submitted content. Before displaying _any_ of this content, the visitor must check off on a Disclaimer. I installed the node_agreement module and found it perfect-- until I realized that (in my case) I would need to individually protect every node submitted by users.

In my case, would it be better to a) alter the node creation form to auto-fill Agreement tab values, b) alter module code, or c) look elsewhere? I'm not totally positive where to begin on either of these options :)

Thanks
-Bronius

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented
Category: support » feature

I think the best option would be to modify the module to support per-content type agreements. For example, adding a section on the content type admin page where we can choose the agreement. This is a feature request and I doubt I can work on it soon, but I can help anyone who would like to undertake it.

texas-bronius’s picture

texas-bronius commented

Ok, that is what I was hoping to hear: sounds doable on the outset.

For this particular project I'm working on, I have opted to protect a node with a php input filter and a views_embed_view(). Then, on the each node itself, rather than protecting them individually, I'll just copy the Disclaimer text in a block.

Wish I had the time and the chops to tackle what you've described-- not yet :(

infojunkie’s picture

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

I am officially stopping work on this module.