Having a way to extend panel_node_access() would be useful.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | panels-n609654.patch | 941 bytes | damienmckenna |
Having a way to extend panel_node_access() would be useful.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | panels-n609654.patch | 941 bytes | damienmckenna |
Comments
Comment #1
damienmckennaHere's a patch that adds hook_panel_node_access() to let this be extended.
Comment #2
damienmckennaThis is another patch from Datacaliber.
Comment #3
merlinofchaos commentedI'm not sure I like this. The problem, of course, is Drupal's node access system itself. It doesn't really allow node access to be changed. Having one node type with a special hook doesn't seem like a proper solution.
The panel node module isn't too complicated. I'm thinking maybe the answer is to try and distill as much of it down to an API as possible to make it so that people who need more control over the nodes can create their own panels node modules. (This would allow multiple node types that can be used with Panels, anyway).
Comment #4
Letharion commentedIn an effort to clean up the Panels issue queue, I'm closing a number of old issues that have not recieved attention or work for quite some time. This doesn't mean there's something wrong with the issue itself, only that we need to focus the limit resources we have on the more active or recent issues.
If you are either still the problem mentioned, or you are interested in the functionality of a closed issue, just re-open it with a patch, reproducible error description, or other relevant information.