Hi,
I have written two access plugins: page_403 and page_404. These plugins have been helpful to me while creating 403 and 404 pages with Panels Everywhere module.
Sorry for my English.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | 1968802-access_plugin_response_code.patch | 1.81 KB | zestagio |
| #10 | 1968802-access_plugin_response_code.patch | 1.81 KB | zestagio |
| #8 | 1968802-access_plugin_response_code.patch | 1.89 KB | zestagio |
| #5 | 1968802-access_plugins_403_404.patch | 2.63 KB | zestagio |
| #3 | 1968802-access_plugins_403_404.patch | 4.27 KB | zestagio |
Comments
Comment #1
zestagio commentedComment #3
zestagio commentedComment #5
zestagio commentedComment #6
andypostAwesome idea! I think this should be implemented as 1 plugin to allow choose a response type a-la page_manager has
And use this setting in summary and access check
You need to implement settings_form()
Comment #7
zestagio commentedandypost, thanks for review. In the near future I will put a new version
Sorry for my English.
Comment #8
zestagio commentedComment #9
andypostJust small nitpicks
403 => t(),
404 => t(),
is enough here, no reason to use string for key
return $conf['code'] == drupal_get_http_header('status');Seems cleaner
Comment #10
zestagio commentedI used string for keys, because keys are http headers for easily compare. In the new patch, I added a description of why to use a string keys.
Sorry for my English.
Comment #11
zestagio commentedComment #12
andypostAwesome!
Comment #13
japerryHmm needs more review... If I remember correctly, I think D8 has a plugin like this, we'd probably want to backport.
Comment #15
japerryDrupal 7 is no longer supported, closing.