I have a View where i would like to expose filters to permit the user to customize the view output.
I know i can use exposed filters but, instead of a drop down (or checkbox/radiobutton of exposed filters) i want to put a list of DIV or LI that, when clicked, can update the view output through ajax. In which way is it possible using Views 3 and Drupal 7?
You can use Better exposed filters module to change output of your filter items to links. And Use AJAX option in Advanced settings of a view to make filtering ajaxifyed.
Related
In InfoPath 2010 there was a trivial manner to set the view called for an item based on the function desired, e.g. a separate view could be made for create, edit, and display and set as the default.
See here:
http://chanakyajayabalan.wordpress.com/2013/06/20/individual-newedit-and-display-forms-for-sharepoint-using-infopath-forms/
I cannot however find the equivalent for InfoPath 2013, nor am I able to locate the corresponding element via SharePoint Designer.
It also would appear that you cannot append the view to the URL in order to directly call a view.
Creating a rule for Form Load that detects some attribute of the call, and sets the view accordingly seems like another option, but I'm just not certain how to access the appropriate identifier.
Final resort would be to do away with the InfoPath form, and create/modify pages via Designer, but would rather avoid this if possible.
Found the way around this is edit the page in SharePoint. You can't do it in SharePoint designer anymore.
Create your views in Infopath then publish. After for the form you want to change the view on, IE create new item or edit item. Once there choose edit page from the settings menu, then modify the Infopath web part to use the the view you want.
This will work for additional forms as well if you want to add custom actions to the list.
I'm following collective.examples.userdata to add some custom fields on the register form.
I want to add two fields, one for state and another for city, where the second load content based on the previously selected state.
My question is how it is possible, can do this only with the schema, using dynamic vocabularies or is need to edit registration form? How can I do it?
Another issue is how to load the registration form in a portlet. Is Possible fill the ##register viewlet?
Thanks!
Use javascript to do the dynamic part of the secondary field. To render the form inside a portlet, there are a couple of ways to do it but again, using javascript might be the easiest. You have place a register button that opens a registration overlay.
Take a look at http://plone.org/products/plone.app.jquerytools for how to wire it up.
Does anyone know the easiest way to have two form fields in a Drupal Webform display side by side. I am using the Webform module to create a form, but obviously as you create it, all the fields list one right after the other. I have two fields that I would like to have displayed side by side. Is this possible? Oh and I'm using Drupal 6 in case that matters.
You could use the Arrange Fields module. This will let you drag and drop and fields anywhere, and should be more than enough to handle what you need.
I am looking for a general, reusable UI pattern I can use for editing the content of dropdown lists in my MVC3 app. That is, some of the Id-Name pairs used to populate dropdowns for edit views exist only for this purpose, and have no dedicated controller-view setup themselves. E.g. Industry and Sector for course modules. Each list is only an Id-Name structure, but Sector has an IndustryId value as well.
Now I really don't want to use the standard scaffolded views for these, i.e. create,edit, and list with links, but I can't help wondering how best to improve on these. Should I bind each list to an editor that just renders a an EditorFor textbox for each item in the list, with jQuery to add a new item or delete an item? is there some established way of doing this?
NOTE: This is not about loading a dropdown list. It's about loading the values for a dropdown list into a view for editing them, to control what appears in the dropdown list when it loads by whatever means.
I don't know if there's a pattern per se, but we deal with this sort of thing as well (dozens of lookup tables with the same structure) and we use simple pages with a jqGrid. The editing is live in the sense that changing a row causes an Ajax call to the controller to modify the lookup value itself. Works fairly well. We ended up having a dedicated view for each of the editable lookup tables (not all of them are) but it would have been simple enough to use the same view, controller and client-side script for all of them.
You can use jQuery, and jQuery UI to customise your dropDown lists
I need to render a few DropDownLists on my page, allowing the user to select different Categories & Locations so as to return different result sets based on their selection.
However, I want each of the resulting selections to be crawlable. I know I could just render every possible Category, Location etc as standard HTML links on the page, which perform a GET request to the specified URL, but if possible I'd like to contain all these options within a DropDownList to keep things less cluttered.
If I were using MVC I would consider wrapping that small section of the page in a GET form, with each ListItem value being the destination URL (though I wonder if even this approach would be properly crawlable?).
I am using Web Forms though and am just having trouble trying to come up with a solution.
Some ideas to consider...render unordered lists of links, and then use a CSS / jQuery / JavaScript approach to style them as menus, using approaches such as http://javascript-array.com/scripts/jquery_simple_drop_down_menu/? That will ensure that they are still crawlable links, and will be presented to users in a drop down list style fashion.
Or another idea, possibly more lightweight would be to just use jQuery to dynamically render drop down list from your unordered lists. Then when a user selected a drop down list item, you would direct the user to their selected link on the client side.
No law says you need that old <form runat="server" /> at all.
Could also use some creative CSS to put the GET enabled form outside the content HTML-flow-wise but pull it to where you want for the users.