I am new to drupal so forgive me. I made a menu and it was automatically created as a DHTML menu. I wanted to style the menu myself and just simply want the 'ul.menu' tree to be printed. Instead, it's doing some javascript and unnecessary CSS. can i disable DHTML menu for this particular menu?
thanks!
If you are using DHTML Menus module, and are asking how to disable it for certain menus, then it should be possible via the configuration in Administrator > Site Configuration > DHTML Menus (as suggested by this and this discussion). Looks like they had this feature in v2.2, then lost after switch to 3.x, and re-included around 3.2 or so.
But you didn't specify whether you use this module or not, so my answer may be completely off due to lack of information.
Related
I have a page with a few modules on it. On one, the QuickE menu is not useful and actually gets in the way of other functionality (DNN's action menus AND 2sxc Edit toolbar). I found the docs and was able to turn it off for the whole page, but that is not what I want. I do want it on for all the other modules, just not this one. This one is a 2sxc custom app and I was hoping to be able to disable QuickE from the View code. Is that possible or supported?
This is pretty straight-forward, you can disable QuickE for a certain section of the theme, and that section can of course be your module. Technically QuickE scans for the html attribute quick-edit-config and respects that for everything inside that html-node. See https://github.com/2sic/2sxc/wiki/Html-Js-%24quickE
I'm having a hard time getting to grips with menus when using the Internationalisation (i18n) suite for Drupal 7.
I have two languages set up for the site I'm working on - English and Welsh.
In the Multilingual Options for Main Menu, I've set it to Translate and Localise.
This appears to be fine, but creating the Welsh versions of pages creates nodes that themselves are not linked to the menu, so when they're displayed on the front-end, the menu structure is lost.
However if you do create a menu link for the translated page, you create a new menu item that essentially doubles up the menu size.
Which method is one meant to use? Do you have one menu structure per language and therefore try and work the code displaying the menus to only show the current language or can you somehow let Drupal know that English page N and Welsh page Y both attach to the same menu item?
As ever, any and all assistance given is greatly appreciated.
~Matt
Your best help will come from the drupal docs.
There are a few ways to setup multilingual websites and it wouldn't be possible to cover it all here.
https://drupal.org/node/275705
Follow the above tutorial as you will need to install quite a few modules. My guess is you may have to revisit your Drupal structure before being able to solve your issue.
I've had to work on a lot of French/English websites and the best thing I find is having separate menus for each language. Then use blocks to show your menus using the Language visibility settings. One better is to use the Menu Block module.
With this method you can end up having a lot of menus (as each menu needs to be duplicated per language). However I find content editors can much better grasp this separation, over the confusion of mixing menu items from different languages in the same menu.
I am making a top menu, and it looks like this:
http://i.stack.imgur.com/5O5G5.png
The contact tab will remain in its place and the home tab has to be first.
IF the user wants to add another tab, they can in the cms editior (DNN) they would just create the link and wrap the div tag about the link etc..
im stuck to how i can get the css to add the menu tab and push the home tab to the left as the menu grows?
If sounds like you are trying to manually build the menu using HTML. What you need to do is ensure that you have the DNN navigation control as part of your skin and it will handle adding the menu items for you. You'll be able to modify the menu to look however you like using CSS.
The best way to learn DNN skinning is to look at one of the existing skins (found in /Portals/_default/skins/) and then copy one of the skins and start making changes to change it to your desired look.
The DNN skinning architecture is very well done and easy to pick up for anyone who knows ASP.NET (though it is different from Master Pages). The hardest part is picking and learning to work with the various navigation providers. Most people work with DNNMenu which is more complicated than it needs to be on the CSS Side. The DDR Menu which will be the default provider for DNN 6+ should be easier to work with. But the documentation for it isn't complete yet so it takes some learning to get started with it.
I am creating a website with Drupal 6.x that will have several content editors and several menus. I would like to somehow lock down their ability to add a piece of content as a top level navigation item. Is there a way to accomplish this?
Additionally, are there any modules that make the menu drop down in the content creation page a bit more user friendly?
The menu settings per content type module allows you to determine which content types may be added to each of your menus.
Are you sure you want to use the menu system? It's possible that you can use the views module to get something more flexible.
I have found several modules which look helpful for enhancing the menu system:
http://drupal.org/project/menu_editor
http://drupalmodules.com/module/menu-weight-assist
http://drupalmodules.com/module/ez-menu
http://drupalmodules.com/module/better-menu
I am working on a Drupal site here: http://selkirk.treethink.net
I have a couple modules that are firing out an insane amount of span classes, which you can see in the source code there.
Nice menus is one of these and is causing 60% of them. I need to prevent these modules from doing this but I can't seem to find the code that's doing this in the module source.
Do I have to write something to cancel it out or override the module theming? I'm not sure how to do this though as this is my first Drupal project.
Here is the nice menus page: http://drupal.org/project/nice_menus
Thanks,
Wade
I'd agree with googletorp's comment. It sounds like the source of the spans is the Devel module's "Theme Developer". It's a very handy module, but it adds a span around every theme call in order to do its work.
The Devel module provides a block titled "Development". Go to Administer > Site building > Blocks and place that somewhere handy in one of your regions. It has a link for quickly toggling the Theme Developer module. I'd only enable it to check on something, and then immediately disable it again.
If it is actually Views layout that you need to override, you can edit your view and click on "Theme: Information" for a list of views templates you can override for that view/display.