Everything is working great with this module, but i have this problem that I can't figure out if it is something I'm doing or what. But when I click browse, it brings up the overlay window just like it should. However, it messes up the rest of my administration page by loading in some stylesheet properties that I have in the default theme of my site. I have root candy as the admin theme. I have a custom theme as my default theme. Somehow I have that style sheet from my default theme coming in and messing everything up.
I can't figure where to begin fixing this. Any thoughts would be great!
Comments
Comment #1
xpersonas CreditAttribution: xpersonas commentedMaybe I just don't understand how I'm supposed to handle the "css scope." Though I still don't see how it would grab my default theme css file - regardless of which theme I select. (My default theme isn't even an option.)
Comment #2
xpersonas CreditAttribution: xpersonas commentedHow about a little help on what options I have for CSS scope field when setting up a content type with node reference explorer?
Comment #3
xpersonas CreditAttribution: xpersonas commentedThis concerns me that my question is full of ignorance. But I still don't understand the options here.
Comment #4
gnindl CreditAttribution: gnindl commentedThe CSS Scope option corresponds to the jQuery UI Dialog option "dialogClass", have a look at http://jqueryui.com/demos/dialog "Options"" and "dialogClass". If you define a value here, the dialog div element gets tagged with an additional class. Then you can have individual dialog themes per field, i. e. you can have different and custom dialog themes.
I don't think this is the solution to your problem. Probably the "Themes" option is more helpful:
- Module: all CSS files of the "nodereference_explorer/css" subfolder are included
- jQuery UI: all CSS files of the "jquery_ui/themes/[theme_name]" are included
- Global: No custom CSS files are loaded. those of your selected theme apply
Play around with this option. Probably some module CSS files, e. g. explorer.tabs.css or explorer.form.css, are interfering with your theme CSS.
Comment #5
vuzzbox CreditAttribution: vuzzbox commentedI have the inverse of this problem and want to identify what I think is a related issue.
On my site, which also uses the Root Candy theme for admin, when I use Modal Frame API for the node reference field Dialog API setting, the Explorer works but the styles are all out of whack for the explorer. The Root Candy styles for the page and forms in the background, on the other hand, remain unchanged.
Also, the Dialog API defined on the field settings *must* be set to use Modal Frame API or the Explorer does not load at all (errors out loading additional javascript files in explorer.js).
Comment #6
gnindl CreditAttribution: gnindl commentedComments #1 - #4: If you use modalframe as you dialog API the problem shouldn't occur any more. Modalframe loads the dialog content into a separate iFrame and is therefore independent. It's recommended to use modalframe.
Comment #5: At this time jQuery 1.7 integration and theming wasn't complete. Please try out the latest version. It's true there's still some 'hard-coded' CSS loaded by default, it's explorer.tabs.css and explorer.selection.css. You can override the styles as you like.
I suppose this issue is solved meanwhile therefore I mark it as fixed.