What would be the best way of creating my own custom view?
I want to have my page do some specific stuff. For example, I am creating a search directory for different names. But, there will be 3 different types of search functions and I would like to toggle between them with 3 different tabs (each tab goes to a different search function). Would this be all in one view with then 3 blocks or multiple views selected by different tabs? What would be the best way of doing this?
One of the search functions will list all of the names alphabetically and there will be an alphabetical directory at the top that will bring the user to the corresponding letter that they select on the page. I believe that this will have to be a custom view that I will need to create, but I have never done anything like this before.
Does anyone have any good advice as to how I would go about doing this? Do I have to create my own module first? Are there any good tutorials out there that would help?
Thanks!
I'd recommend giving https://drupal.org/project/quicktabs a try. I haven't used it myself, but I know of others that have.
The project page sidebar has links to docu and a demo with some screenshots of config.
If you're going to be reusing almost all of the settings between blocks you'd want to create different blocks displays within the same view and override what you need to.
Related
I am new to Silverstripe so am still learning the best way to achieve certain results.
I have the following website: http://i.imgur.com/HHHIlwA.jpg - that I have converted into a silverstripe theme etc. I have setup the front page as a HomePage.ss.
Now I want to be able to edit most parts of the page from the CMS. I have followed this tutorial on this website: http://www.silverstripe.org/learn/lessons/working-with-data-relationships-has-many - and have created a region under the "Articles" heading in the pic which comes up as a tab on the CMS in the admin panel. http://i.imgur.com/Gi7kZmq.png
My question is, is the best way to make parts editable to make them regions like what the video has shown etc? E.g if I wanted to edit the section in the pic that has the picture of the big ring and the text next to it, am I best to make this another region? What about for things like headings etc?
Thanks in advance :)
There are several possibilities to solve this problem:
either use several $has_many for each group if you have a fixed structure
if you need flexibile structure you can use one of the several 'block' modules like https://github.com/bummzack/page-blocks or https://github.com/NobrainerWeb/Silverstripe-Content-Blocks.
There are some more modules like this around, each have pros and cons, depending if you need reusable blocks, translatable blocks, want to save the relations with Versioned etc... #lerni made an overview about those modules.
Am I able to add the following field to a content type, so that each piece of content I create can be conditioned to a page?
Or is there a module to extend Publishing Options, where by it adds all the pages I have created (just like 'Promote to Front Page')?
If not, why is no one doing this? As a new user to Drupal this seems like it would be a handy operation. (I have already tried this module but it doesn't achieve the results I'm after).
If none of these solutions are available, what would be the best alternative way of doing this?
I've posted this question on Stack Exchange for Drupal but I need a quick answer and there seems to be a bigger community here :D
You should use Context. With Context, you'll be able to manage contextual conditions and reactions for your drupal like Regions.
Have you used Views? it is one of the most common used drupal modules. It doesn't extend publishing options directly but it does replace it in a way. You can say by example put a list of al content-types: your_own_Content_type that have the publishing options of promoted to front-page. then sort them by title, date, what ever you like.
you could also create only one view and create multiple blocks out of it. you have to understand the logic of drupal: if you want different blocks on different pages, you have to create the different pages AND different blocks
create the view for one type of content-type and make one block out of it. put this block on the desired page. All your other blocks are made with the same view, just adjust a condition in your view and create a new block out of it. You should also put all your blocks in the same region, and set the to the right pages
here you can find a lot of documentation if you run into any problems... drupal.org/project/views
Views is the best at creating a slideshow of images or any type of data on your site.
Used in combination with nodequeue it might offer near or the full functionality you are trying to achieve (check this out ... and this too) - but I don't understand your question entirely.
By my opinion Views is too complicated task for much simple request.
There is a few ideas for solution:
Easy way - You can create a specific template file or add some if statments to the node.tpl.php(specific tpl better)
For minor changes - Create a new context with "path" filter and "theme html" reaction, than hide the field by the css
Best but complicated(large usages) - create a new "view mode" and implement the display by new "hook_menu".
~ Almog
I would like to have a user land on a page and see on view that depends on her role. When I tried to create two views with the same path, Views did not object. But I'm wondering if it's not meant to work this way.
Is it two views or two displays on the same view? According to the maintainer of the Views module, two displays on the same view are meant to be able to have the same path, but two different views should not be able to have the same path.
If the results of the view are based on the user's role then I would recommend using one view/display but use the user's role(s) as an argument.
If you have a small number of roles that don't change very often you could create individual displays and adjust the display's 'Access' settings in the view for each one. I would not consider this a best practice but there might be certain situations where this is fits the bill.
I have some nodes I am displaying in a view. They are displayed as nodes, unformatted. I would like the user to be able to choose from some predefined sort criteria ( via drop down list or similar).
So they could pick recently active, most commented, newest, etc., and re-query for new results.
Its easy with tables because you can make the labels clickable, but I do not know how to have similar functionality with a raw node preview display.
Just a thought, from me to me, and for anyone else who may be trying to do this.
An easy, sleezy option would be to just add another page view for each of the required sorts, and provide a link to these other views in the header of each of the pages.
This could also allow for (easier) linking to the individual sorts, so say if you have a sidebar block displaying recently commented nodes, you could adjust the .tpl.php of the block to have the title link to the view displaying the full set of recently commented nodes.
also im pretty sure there should be a way to do this with arguments, but i dont know how
Views 3 supports exposing sort order (just like you can expose filters)
Select the sort order (e.g. add sort by node creation date, then click on the settings for that), you should be able to expose the sort order to the end user. This is just like clicking on the settings for a filter and then choosing to expose it.
Standard views isn't going to support this, so IMO you're best off implementing a custom solution using just a plain old view and this jQuery plugin. You can either do this at the theme layer (the same way as any other JS in a theme) or a custom module (via drupal_add_js() to add the plugin and your bit of custom code). Either way will work, although the custom module has the obvious benefit of being theme independent (and thus more portable).
If you go the custom module route, please consider releasing it as a contrib module on http://drupal.org.
Can any one help me out on how to theme a view.
For each view created i want to have different templates.
Theming views can be somewhat tricky, depending on the kind of views you have created and the changes you need to make. Check out this introduction for Views 2, and make sure to install the Advanced Help module to get at the views2 documentation from the views module itself (there will be a link to the documentation on your views overview and edit pages, once you activated the Advanced Help module).
You can also find some questions/answers here on SO (e.g. Drupal 6: How to quickly theme a view?), if you search a bit.
I actually did this the other day. Ill give you a brief overview and expand a little later.
Set up your view; by going to Views -> Add View
Once, your view is completely set up, at the bottom of the view (left column in D6, right-most "Advanced" column in D7), you will see a link called "Theme: Information", click on it.
What you will be presented with is a list of templates (.tpl.php) files that the views uses to theme your data. Basically the file names that are bolded are the files views is using to theme the data.
To Customize Your Views
Select the page you need to theme. For Example, if you created a "Block" view, and I wanted to customize the basic html layout, I would pick a name (other than the one that is currently bolded) that is being displayed to me and create the file in my themes directory (sites/all/zen/custom-file-view-fields-views.tpl.php) - this is if views told me that I could use the filename custom-file-view-fields-views.tpl.php
The next step is knowing what code you need to put in there. The quickest way, is to go back to the theming information in views, click on the link of the file your replacing and grab the code that is presented to you. Paste that code in the file you created.
From here on out, you can now successfully customize that view.
Keep in mind that the theming information presented to you is presented from basic to complex (up to down). So choose which file you need to edit carefully. Ill put up some images in this answer a little later.
Hope this helps! Cheers!
Is there something specific you're trying to accomplish? There's a lot of ways to "theme" a view, unless you mean "theme" in the strict Drupal sense.
Personally I just give the fields classes and use those, rewriting the output to include variables as classes if need be. This tends to be easier and more manageable than modifying TPL files directly.