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
Related
I have a strange question but I don't find any hint about that (if it's possible), for a drupal 7 website I have to modify some content of a page in the backoffice, but I really don't know from where some content of this page is created (a table, similar to a view table but not a view table).
I just want to know if there is any way to show which php function the page use to finally be showed. I know there is something like that for the theme (drupal theme debug) but I don't find something for my case.
Any idea ?
You need PHP profiler to check all functions called on page, there's a module for Drupal7 for XHProf integration. But I would suggest you to use your browsers inspector as mentioned by 2pha before. For example if there's a form on the page just use the form ID to find it. Custom classes are very useful in these cases, parts of the html codes etc. In your case search for table headers...
The code you are looking for is most probably in custom modules and the
general suggestion is to keep you custom modules in separated folder from contributed ones.
I'm building a drupal site right now where I'd prefer to use views_bulk_operations to administer the standard content overview (admin/content) and user overview pages (admin/people). My trouble is that I also want to use the toolbar module (or something like it) to give my site admins the ability to easily browse to the pages generated by views_bulk_operations (admin/content2 and admin/people2). It doesn't seem possible right now. The toolbar module automatically adds pre-defined links based on a users permissions, and there doesn't appear to be a way to make any changes to those links.
Any ideas? Or, perhaps, any alternatives to the core toolbar module? Thanks!
(I asked the same question here, but thought I'd have a better chance here on stackoverflow.)
I just figured out that I can use the quickbar module to accomplish what I want.
I'm fairly new to using Aptana, but I'm wondering if it supports a feature that I used to use a lot in Dreamweaver, where you could create a page template, i.e. the header and footer of a page that would stay the same for each page on a website, leaving only the content to be coded.
I found this feature really useful as you only needed to change code once for it to propagate to all pages.
I've searched for this feature in Aptana, but I'm not sure on the exact terminology.
Not currently. There have been requests for it, but it has not yet been implemented:
https://aptana.lighthouseapp.com/projects/35272/tickets/2140-allow-for-dreamweaver-like-templates
I'm new to Drupal. I want to create a contact page, so I copied page.tpl.php and renamed it to page-contact.tpl.php. I created some new elements in the page, so I can see that if I click on the "contact" link, I'll know that I went to the correct page.
Right now I don't see any change. Was there something I missed? Do I need to do something in the admin settings so Drupal knows which file I need to open?
I also tried clearing my cache.
In theory, this is a valid approach. Problem is, you'll be able to create a new layout for your contact page this way, but not necessarily change the contact form. If you wish to alter the form as well, I'd recommend using the webform module. It's pretty flexible when it comes to creating contact forms, plus, it creates a node, so you can style it with ease (either in you standard node.tpl.php or - even better - in node-webform.tpl.php). This is what I usually do.
There might be other solutions too, but it would help if you made it clear what kind of alterations you wish to introduce in your contact page.
When you say cleared my cache do you mean the browser cache or drupal's cache? Ensure drupal's theme registry has been cleared by going to /admin/build/themes, or logging out and back in.
I also recommend trying the webform module as mingos suggests.
Drupal core's built in contact module does not use any templates, so you'll have to use something like Webform if you want a per-contact template.
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.