Closed (cannot reproduce)
Project:
Revisioning
Version:
6.x-3.12
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Aug 2011 at 11:24 UTC
Updated:
17 Dec 2011 at 04:25 UTC
Jump to comment: Most recent file
Comments
Comment #1
rdeboerAbsolutely!
All patches welcome.
Rik
Comment #2
progga commentedHi,
I have attached the patch. This patch adds a checkbox in the settings page (i.e. admin/settings/revisioning). When this checkbox is NOT checked, _revisioning_edit() and revisioning_edit_revision() will NOT attempt to change any themes. By default, the checkbox is checked. So the behavior for existing sites will remain the same.
If you want me to setup some kind of test site for this then do let me know.
The patch is against 6.x-3.x instead of 6.x-3.12.
Thanks,
Adnan
Comment #3
rdeboerThanks progga!
Patch looks good.
Will apply for next version.
Rik
Comment #4
mkalkbrennerI don't understand the problem exactly because I don't know Revisioning module yet.
But getting a path like "node/%/revisions/%/edit" into ThemeKey itself is very easy. We did the same for other modules, p.e print:
That's all we had to do to integrate both modules.
From revisioning.module I assume these paths will do:
If agree, it will take me just a few minutes to get this into ThemeKey itself.
Comment #5
mkalkbrennerIntegration / support of Revisioning module committed to ThemeKey. It would be nice if someone tests it.
Comment #6
rdeboerEven better, Markus!
Comment #7
progga commentedActually, the problem is not with any specific paths. _revisioning_edit() and _revisioning_edit_revision() overwrites the "$custom_theme" global variable when a node edit page or node revision page is opened respectively. So any value assigned to "$custom_theme" earlier from themekey_init() gets lost when any of these functions are called :-(
I have tried to test Markus' latest update in the following way:
Thanks,
Adnan
Comment #8
rdeboerNot sure. Nobody has cared for nearly 4 months.... closing.