Is there anyway you would consider using the metatags api for this module? This way the module could be used in addition to the metatag module? There are many benefits of adopting this approach including the fact that I belive many many users will want to adopt your way of adding/editing metatag data but will also want to use some of the other features the module offers (screenshot metatag-mods.png).

Currently metatag has 65101 downloads and is establishing itself as the standard drupal meta mod, but doesn't have you're approach. I've made a request in http://drupal.org/node/1859290 for someone to adopt this approach within metatag, however it would be polite if I asked you first if you would re-consider doing this with beanstag? I know i've asked something similar before but thought i'd try one last time :)

Many thanks

CommentFileSizeAuthor
metatag-sub-mods.png19.83 KBkingfisher64

Comments

ykyuen’s picture

ykyuen commented
Assigned: Unassigned » ykyuen

Hi Kingfisher64,

Thanks for your suggestion again. As the author of the BeansTag module, i am very happy that you appreciate my work. =)

I understand that merging maybe a solution to push the BeansTag module to a official release. But personally, i still think BeansTag is different from the Meta tag approach and should deserve to be a standalone module.

The motivation of writing and path base meta tag module is because i want to provide a simple and centralized user interface so the user doesn't need to take care about node, view, site languages when setting the meta data. Think about a simple website with just a few pages, as a user, i do believe BeansTag is a good alternative to site admin users especially for those non-developers.

Thanks again for your suggestion and hope you understand my decision.

Regards,
Kit

kingfisher64’s picture

kingfisher64 commented
Status: Active » Closed (works as designed)

Ok Kit no problem. I understand you're logic.

Thanks for replying. :)