In some use cases you don't necessarily want all nodes to be part of the blog. I think a checkbox option for whether or not the post is in the blog would make sense.

Comments

Flying Drupalist’s picture

Flying Drupalist commented

Thanks for this very necessary module, looking forward to taxonomy_blog :)

jcfiala’s picture

jcfiala commented

Hmm. I hadn't considered that. That's a cool idea.

Taxonomy_blog has been slowed down by the need to get some paying work in, but I hope to finish it soon.

Flying Drupalist’s picture

Flying Drupalist commented

Thanks for the update, looking forward to it!

Flying Drupalist’s picture

Flying Drupalist commented

Hi, I'm curious about the functionality of taxonomy blog, can you describe what new features it adds please?

Thanks.

Flying Drupalist’s picture

Flying Drupalist commented

Is there any news on this?

coltrane’s picture

coltrane
he/him
commented

I don't think there's any news. During initial development ownterm was designed to not focus on blogs, though that was the first use case. Later, however, it received some specifics that narrowed it down to what we have now. Ideally I'd like to get back to a place where ownterm can be used on any content type (never using the name "blogs" etc). I don't think a checkbox is the best approach but may do for the short term if a rewrite is required to generalize functionality.

Flying Drupalist’s picture

Flying Drupalist commented

I can't comment on generalized functionality, my use case is only for blogs. I think having a checkbox would be the ideal situation... though my imagination is not necessarily the broadest.

Another idea I had though:

Remove the automatic adding of the own term in every node a user creates, while still hiding the vocab field.

Then create rules integration for adding and removing own term.

That way, I can create a cck checkbox, and use rules to add the checked nodes to the term.

It's a little more generalized, but the same idea.

Any help on this matter would be terrific awesome.

Thanks.