Can someone point me out a module for creating tabs in node?
I already try the QuickTabs but it uses the same tabs in all nodes i want to create different tabs in every node.
I found out that there has been Multigroup module which supported grouping CCK fields and repeating them but there isnt any version for drupal 7
I tried Node reference module but it only shows Links of referenced module not the whole content.
Can someone point me ideas on how to accomplish this maybe views can help some how but i dont know how to reference view with node.
Quicktabs will work fine, just override the look of the tabs with css and or tpl.php theme override files.
Or set up lots of different quicktabs and give them each a different display style, there are quite a few built in, and you can specify your own.
Or you could look at jQuery UI Tabs and use built in theme settings...
Related
I am working on my own Mediawiki installation and developed a skin based on Bootstrap 3 (MediaWikiBootstrap). There are a few issues which are taking time to resolve and few cases i am not sure how to resolve.
I used ContactPage extension and could not find an easy way to use bootstrap form css classes. there are options to use 'MediaWiki UI' for that contact form but i am facing the same problem with the other pages, like the All articles, search page and so on.
so is there any way to use 'MediaWiki UI' in all the form and can i create my own form style using Bootstrap3 css classes?
There is a configuration variable ($wgUseMediaWikiUIEverywhere) which, if set to true, should activate mediawiki ui on every form element (that is build with the Html or Xml MediaWiki class) in MediaWiki (excluding forms build with string operations).
For the long term it is planned to remove this variable an activate mediawiki ui by default.
If i understand Bootstrap correctly, there is no easy way to add/remove classes to elements generated by MediaWiki.
Btw: There is already a bootstrap skin, maybe you can reuse this? https://www.mediawiki.org/wiki/Skin:BootStrapSkin
I'm working on an upgrade for our current application (asp.net mvc). Here my problem is, I have a existing css file name "styles.css". Now this file has lots of css classes and they are used in different pages.
Now as a part of the upgrade process, this css file will not be used anymore. But I still want certain css classes from this file, so that I can copy them to a new file and include it in my pages.
Any ideas on how to extract these styles which are used in my new pages. And yes the styles which I want to pick are already set to the controls in the page. Please help.
Finding ones that are used in single page should be easy with multiple tools. One good tool is called UnCSS.
The trick is checking an entire site where CSS file is shared accross pages.
This approach was popular in social networks recently with some high profile guys sharing it like Google's Addy Osmani and some Google Chrome guys:
http://addyosmani.com/blog/removing-unused-css/
Use Chrometools Audits
In Chrome Press: F12 -> Audits -> Run
It will let you know what is and is not used.
There are a lot of ways, for example:
Firefox plugin, this will extract the used css
https://addons.mozilla.org/en-US/firefox/addon/dust-me-selectors/
for chrome
https://chrome.google.com/webstore/detail/css-remove-and-combine/cdfmaaeapjmacolkojefhfollmphonoh?hl=en-GB
Manually: another way in the chrome (or other browsers), right click and select inspect element, this will show you the hierarchis which is working on specific element, by that you can take your used css
You can find the unsed css from the following tool, so that you can clean your css to have pure one
http://unused-css.com/
or
http://www.pontikis.net/blog/remove-unused-css
Use a Browser Debugger, click on the elements on site and see on the right corner which classes are machtes and copy them.
According to design specification I have to add two different menu lists with own Titles on AsideFirst zone in Orchard CMS.
As far as I'm concerned there is no need to create your own zones, it could be done via your own Content Definition and creating your own View for Menu widget. It that correct, can you please share some info about it?
BTW: How do I add my custom View for replacing some widgets? Should I simply add .cshtml file with proper naming?
Download the shape tracing tool, found here: gallery.orchardproject.net/List/Modules/… and use it to inspect your menus to find the correct names for alternate shapes to use. These will be created in your enabled theme.
I believe you can copy the view generated by Shape Tracing into one of your modules and place it in the Views folder, not Views/Parts/.
I have installed mediawiki 1.21. I am wondering how you can add navlinks (meaning the path to the page. Not sure if I am using the right work to describe it) at the top similar to the way it is in wikihow website? Below is an image so you know what I am referring to.. I find this to be very useful so users can understand where they are when reading an article.
I have created a custom skin and I have a Navlink DIV at the top where I would to show the path to that page there like: wiki -> xyz Category -> Article Name. I have semantic extension installed. Can this be achieved with that? Or is there another way to do it? How can I add the code directly in my skin.php file so this navlink is generated and listed depending on what page the user is on?
Terminology
This kind of feature is called a breadcrumb.
Has MediaWiki already this kind of feature?
Yes, for subpages.
A subpage is a page intitulated Quux/Foo/Bar in a namespace with the subpage feature enabled. By default, this is the User namespace for example, but not the main one (For example, on Wikipedia projects, we want to be able to use titles like AC/DC).
In this situation, a breadcrumb Quux > Foo will be printed.
This doesn't solve your issue, as you want to use categories, but it allows you if you write your custom code to know there already is some code somewhere doing that :)
Breadcrumbs extensions
Some extensions have been developed to solve this particular issue:
BreadCrumbs2
CategoryBreadcrumb
The first is more exhaustive and gives you more flexibility, the second simpler and so a good starting point to write a custom stuff.
I am relatively new to Web Development, and I am messing with a Joomla template installation.
I managed to get firebug to make changes and Firediff to save them as a new CSS, and replaced the CSS file on the server.
What I would now like to do is edit the template elements, (mostly deleting unused template elements), on screen using firebug, and then save the changes to a new HTML document.
My trouble is that I cannot work out where the correct html is to replace on the server.
Only by using Dreamweaver I can ascertain that the file name is index.html, but there are many files called this on the server.
With the CSS file I was able to identify the server path and filename from the blue text in the right panel of firebug, in order to replace the CSS changes with the output from firediff.
Can I identify the location, (and ideally filename), of hte HTML document in the same sort of way from firebug?
You might want to read the template tutorials before removing anything from the template index.php. In general, you want the template to have provisions for every possibility that you might want. A well designed template will have the ability to display multiple columns in multiple positions as well as other positions to place banners, login boxes, weather widgets, or anything else you can think of. Then you simply code the template so that any position that is not being used does not get added to the final code of the page being displayed.
Official documentation - http://docs.joomla.org/Joomla!_1.5_Template_Tutorial
Once you have a good handle on how the template is supposed to work, the file you will be editing is in JOOMLA/templates/YOUR TEMPLATE/index.php
Be sure you get the whole module positions and collapsible module position thing before stripping anything out. A well thought out template will very rarely need any code editing, virtually everything should be done in the admin and with CSS page class and module class suffixes.