Currently we're hiding access to specific metatags in the form by comparing to a 'context' parameter in hook_metatag_info() when we should probably be using a hook instead (that could fallback to the context).

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Issue tags: +D7 stable release blocker

.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Version: » 7.x-1.x-dev
Assigned: dave reid » Unassigned
damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Marked #1497402: Expand permissions range as a duplicate.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Assigned: Unassigned » dave reid
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Assigned: dave reid » Unassigned
Status: Active » Closed (duplicate)

Lets move this over to #1961354: Optionally control meta tag permissions individually which has some working code that needs review.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Add a hook_metatag_access() for controlling access for viewing and editing metatags. » Add a hook_metatag_access() for controlling access for viewing and editing metatags
Status: Closed (duplicate) » Postponed
Issue tags: -D7 stable release blocker

On second thoughts, lets leave this as a postponed issue and remove it from the stable release blockers, as I don't believe it'll be important once we have extensive permissions available.

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented
Issue summary: View changes

Can this be closed now, since metatag has the ability to specify permissions per metatag now?