I went ahead and uninstalled the current Admin module in the OpenPublish 1.7 distribution. I deleted it from the server. They have recent development releases of the Rubik theme that works with the Admin module 2.x. I deleted the admin module after I disabled it in the modules page. I put the Tao theme in the themes directory and the Rubik theme inside of the Tao themes folder. Then I upload the 2.x version of Admin module into the modules directory. Under adminstration themes I changed the default to Rubik and in the modules page enabled the Admin modules. Works great except for some minor broken CSS styling and the pop-up edit window has the sidebar menu which breaks it's theme (try adding an author under create content article.)
It's a lot of work getting this theme styled and correct for OpenPublish 1.7. It does immediately solve the problem of the errors in the Admin module 1.x version.
Here is the first little bit I solved. I added this in /sites/all/themes/tao/rubik/style.css using the Custom CSS comment to keep everything clean.
/* Custom CSS */
div.column-side {
width: 27.99%
}I'll post more as I find or solve other problems. I hope I'm not going down the wrong path doing this. If so, let me know, so I can remain consistent with the what the developers of OpenPublish are doing.
Comments
I'm gettin ahead of myself, once again.
The new Admin module has a wicked cool UI with a tab for the Devel module. I turned on the Theme Developer module with rendered the Admin module useless. I guess that it still has quite a few bugs to work out. Better go check their issue queue. It's still awesome, though.
Marine job board with Drupal 7 at http://windwardjobs.com
Hacking OpenPublish Core Code
I was getting this error:
Fatal error: Call to undefined function _admin_init_theme() in /var/aegir/platforms/openpublish/sites/all/modules/openpublish_core/openpublish_administration/openpublish_administration.module on line 13I'm not sure what is does so I got rid of it.
function openpublish_administration_init() {
$admin_theme = variable_get('admin_theme', 'rubik');
/** // Initialize the slate theme. Bypass the theme system entirely so we can load our own theme into place.
if (variable_get('node_admin_theme', 0) && (arg(0) == 'node' && is_numeric(arg(1)) && arg(2) != NULL)) {
_admin_init_theme();
}*/
Could somebody explain what happened here and why it's seems to be working.
Marine job board with Drupal 7 at http://windwardjobs.com
I updated as well to admin
I updated as well to admin 2.x beta1
Removed slate and added Rubik etc etc.
All seems to be working fine!
Just trying to tweak it now ;)
I'm having only one problem
I'm having only one problem so far which is with the Theme Developer module braking the .js code in the Admin sidebar to the point I can't disable it. I have to do the old fashioned /admin/build/modules . I read the issue queue for the Admin module and they the bug has been patched so I don't know what's going on. Since OpenPublish has had some patches and esoteric configuration I'm not sure how to handle the situation. I wish the developers had a little more time to be more involved on the discussion board. And, I would guess they would want some more developers participating in the project.
Marine job board with Drupal 7 at http://windwardjobs.com
I want to add the other
I want to add the other problem I'm having. In the modal frame popup with node reference in the create article CCK form, the Admin sidebar is showing. How do I disable it?
Marine job board with Drupal 7 at http://windwardjobs.com
We will be switching to
We will be switching to Rubik/Admin 2.0 in 1.8 probably (still waiting Admin 2.0 to mature a little more) so you guys are ahead of the curve.
Thanks for sharing your experience with the change.
.............................................
http://twitter.com/inadarei
That's great....... wait,
That's great....... wait, what? 1.8? ..... what about 1.6 and 1.7?
Marine job board with Drupal 7 at http://windwardjobs.com
I'dd guess the 1.7 is so far
I'dd guess the 1.7 is so far ready that they won't integrate it, as it involves some work.
Any timeline on 1.8?
Actually, we ended up
Actually, we ended up integrating Admin 2 and Rubik in the upcoming 1.7. Even though admin2 is still beta, and we wanted to wait, admin1 is so buggy (due to the arm-twisting with forcing in-the-module theme on drupal) that despite our many efforts we could not stop it from throwing bogus error messages and doing other horrible things.
.............................................
http://twitter.com/inadarei