Separate permissions for path-based and entity-bound meta tags [#1387228]

I am not sure this separation is demanded by other users of the module. With new permission, it will be necessary to decide how to deal with existing permissions

Log in or register to post comments

Comment #7

sa3er CreditAttribution: sa3er commented 28 May 2012 at 20:36

Thanks for your time,
So my project is an e-commerce website where people come and post their products. Each person has its own account. I want them to be able to change and define their own liked keywords and descirption of their products and also their profile page but I don't want them to have the access to change wide site Path-Based Metatags.

Can I at least patch the code so the "Path-Based Metatags" button won't show up for no one other than User-1 and administators rule?

Any walkaround is greatly appreciated.

btw, sorry for my sloppy english.

Log in or register to post comments

Comment #8

wxman CreditAttribution: wxman commented 9 June 2012 at 18:06

I've been trying to come up with a way as well. Our site will have writers making their own profiles, and I would like to give them the chance to write their own description tag. On the D6 version of the site we used nodewords. I set up a text field to be used for descriptions, then used tokens to insert that into the meta description. If tokens could be used in the path based meta tags, the same thing could be set up. Any chance that could be possible?

Log in or register to post comments

Comment #9

wxman CreditAttribution: wxman commented 9 June 2012 at 19:26

Just to add to what I posted before: I have found a way to make it work. It's a bit confusing though. Here's what I did to make custom meta description tags for both members that are writers, and ones that are readers.

1. Make two new meta fields in the Manage Fields tab in the meta tags quick admin. I made (Meta)Public Description and (Meta)Author Description.
2. Install the Field Permissions module.
3. Install Profiles2.
4. Make a Public Profile, and an Author Profile.
5. Add the Public and Author description the their respective profile field lists.
6. When adding the fields you will see the section on setting the custom permissions.
7. My profiles uses a panels/views setup to display, so I edited the view showing the profile, added the new description field (set formatter to 'default metatags_quick_formatter').

So far this seems to be working.

Log in or register to post comments

Comment #10

valthebald

Sofia

CreditAttribution: valthebald commented 18 June 2012 at 12:34

Nice catch, wxman!

Log in or register to post comments

Comment #11

wxman CreditAttribution: wxman commented 18 June 2012 at 19:02

Thanks. I can't wait to get the site live so I can see if it really works when people use it.

Log in or register to post comments

Comment #12

sa3er CreditAttribution: sa3er commented 30 June 2012 at 15:09

yea, great job wxman, but that's too confusing and not standard indeed. Adding two extra module to overcome a simple permission matter is quite unacceptable.

So pity the respectful module maintainer is not cooperating. I wish I had a better knowledge of D7 module programming to obtain what I truly want.

Cheers.

Log in or register to post comments

Comment #13

mexicoder CreditAttribution: mexicoder commented 18 December 2013 at 11:49

Issue summary:

View changes

File	Size
additional_permissions-1387228-13.patch	1.6 KB

Have added another permission level to differentiate between path based and entity based meta tags. However we still aren't running any checks against the content we are altering.