As it is now possible to have multiple annotations per node should this be node_type based?

We have now the configuration admin/settings/annotate but would it be better to have it here admin/content/node-type/page?.

It sounds better :)

Please let me know.

Comments

clemens.tolboom’s picture

Assigned: Unassigned » clemens.tolboom
Status: Postponed (maintainer needs more info) » Active

I'm working on this because it makes different settings per content type more easy. After fixing this I'll start on D7 :)

clemens.tolboom’s picture

Title: Do we need a per node type configuration options? » Move configuration to content type
Status: Active » Needs work

Please review the current dev version.

The current version lacks the transformation of the current settings into the new paradigm.

We now have to check each content type. Is that bad? Please tell me.

scottrigby’s picture

Maybe a global default, which can be overridden per content-type?

This is actually similar to a request i was just thinking about... which relates more to content. It would be nice to select whether annotations are plain text or filtered to allow input format. Similar to adding a cck textarea. I'm not sure why i thought this was similar, except that this kind of configuration is what we'd expect in the content type settings area... I could add a new issue if you think it's something you'd like to see?

clemens.tolboom’s picture

Category: feature » bug
Issue tags: +6.x-1.2

User migrating from 6.x-1.1 to 6.x-1.2 needs the variables replaced.

function annotate_update_6101

is deleting the old variables without introducing the new ones which is bad.

clemens.tolboom’s picture

Status: Needs work » Fixed

Added variable transformation to function annotate_update_6101()

clemens.tolboom’s picture

Status: Fixed » Closed (fixed)