I am trying to redirect the Taxonomy term path/url to a custom panels/page, I found several posts from around the web about that and tried to implement the instructions but they did not work and I am doing something wrong. For example I tried what I thought was the closest to my situation found here and in the following quote but it did not work and the Taxonomy views was already disabled in the first place on my end.
Disable the Taxonomy term view.
Set the path on the panels page to /taxonomy/term/%.
Clear cache.
View page at taxonomy/term/{tid}.
I verified that this also works with URL aliases.
Can someone provide clear directions for the following
Pages/Panel screenshot
What do I enter in,
Page information
Page parameters
Page access
Variants: contexts
Variants: selection criteria
I've tried all kinds of different settings ("/taxonomy/term/{tid}", "/taxonomy/term/%", "/taxonomy/term/{taxonomy_term}", "/taxonomy/term/112") and changing Home>>Administration>>Configuration>>Search and metadata>>url alias settings but every link just goes back to the default taxonmy term page.
I solved the issue. If any body needs the answer here it is.
To change the page/layout of a taxonomy term first go to page manager (Home >> Administration >> Structure ).
You might see a page called "Taxonomy Term", that's where you want to start to make changes so click on that. If not you'll have to create on page. Both can be addressed by the following steps.
This example will show you how to create and use different layout for a different term page.
Go to Structure > Pages (/admin/structure/page_manager) and click on Edit button under Taxonomy Term row. On the right side you will see Default
These are variants. The Default variant at the bottom affects all the taxonomy/term pages. All other above variants overrides the Default variant using certain conditions a.k.a "Selection criteria".
Click the Add variant button to add a new variant.
Enter Label for the variant and choose "Panels" under the Type dropdown menu.
Choose "In-place Editor" for a Builder
Choose Layout for the page.
Enter [term:name] for Page title. This token holds the name of your taxonomy term. Now click on the Finish button, you will add block later.
Click on the Selection criteria.
Choose "Request Path" for a condition and click on the "Add condition" button.
Add taxonomy term page url's you wish to override (e.g. taxonomy/term/25).
Go to one of those pages (e.g. taxonomy/term/25) and add blocks.
Note that your variant must be positioned above the variant you override to work properly. Use the Reorder variants button to reorder your variants.
You can repeat this procedure if you wish to target a different terms also or a vocabulary. You can have as many variants you want.
Related
Is there a way to change the default list page when you click on a entity form to a custom search page? Something like google ( a text box with a search button) to return the results of the list base on the search criteria?
for example,
from this:
to a search page.
Sorry you can't. This page is not customizable. But the dashboards are. You can make a custom dashbard with a single iframe and it can be your default page.
Yes you cannot modify the design of this list page. Dashboard & custom html webresource/iframe is fine.
But I recommend you to customize this list page itself to look like what you want, atleast close to similar CRM UX. First deactivate all the views for that particular entity except Active & Quick find. Rename the system view “Active Details” into “Search” & modify the filter condition to include something like createdon = tomorrow. Hence the grid will be empty, you got search box on right to start with. When user search, Quick find view resultset will be rendered in grid.
There are two different websites with drop-down menus, but only one is having the appropriate "branch-out" affect.
Picture 1 is the one not branching and picture 2 is doing what I want:
No Branch
Branch
The menu that is correct is using a tree menu widget and the other is not, only a breadcrumbs widget. As you can see I added a "Test Page" under Government, but it is simply at the bottom of the menu. If it's just a matter of inserting a Tree Menu widget to get the affect I want, I'll do that, but I wanted to see if there was another solution first. Thanks.
Looks like it could be an issue with the webpart used for the menu. So the one site showing correctly may have the levels set to the necessary depth whereas the other site may not. This doesn't seem to be the case though as the webpart is picking up the "Test Page" but not the "Tax Matters" page.
It could also be an issue with the overall design of the site's menu. Maybe the site's menu wasn't designed with 3 levels of depth on it. To check this you can go to the webparts transformation property and see if there are multiple levels setup to display that 2nd and 3rd level nested within one another.
Not knowing the configuration of your webpart or the transformation makes it a bit harder to actually troubleshoot.
Somebody pulled the most random question on me today and I realized I'd never even considered it. What they wanted was my PDF rendering of an SSRS report to come standard with navigation arrows, i.e., previous page, next page. This started me looking at all the options that are available, which are actually kind of cool, and I was able to add on a table of contents, including bookmarks for a new number (e.g., if you're printing 5 invoices with 2-5 pages each into one long document, those will have the invoice number and you can jump to the beginning of that invoice), but I couldn't see anything about navigation links. In fact, most of what I've seen says that PDF's only can have navigation maps, i.e., the table of contents tab. So if anyone has any ideas on how I can do this, that would be great. I know it can be added after-the-fact with something like Blubeam, but that's not practical in this case.
As I mentioned in comments you can create a bookmark in each page. A bookmark can be added using the component DocumentMapLabel property almost all SSRS Report Items (Tablix, Textbox, Charts, etc) have.
If you don't have a title or a textbox at the very top of each page, add an empty textbox, be sure place them at the top of the page in order to each bookmark jumps to the beginning of the corresponding page.
Select the first textbox and press F4 to see the extended properties window, look for DocumentMapLabel and type Page 1.
In each page set the textbox DocumentMapLabel property to the corresponding page number.
When the report is exported to PDF, your PDF client shows the bookmark menu, containing a bookmark for each page. If you click on a bookmark it jumps to the related page.
This is how it looks in Adobe Acrobar Reader:
Let me know if this helps.
I've (very) recently dived into Angular, but I'm struggling a bit with how to design my layout.
For my site I've created a menu containing an input field and some buttons. The idea is that the input field combined with either of the buttons should service a function. So say for viewA, the input field should only act as a search bar. If the user however clicks one of the buttons the input field value should be used to as a basis to create a new item in another viewB.
The search function works great for viewA, but I'm unable to make the buttons switch views. I'm suspecting (or know, but don't know how to address it) this is because the mentioned buttons are outside the view (ng-view) and thus don't have a controller.
I've searched around for "multiple controllers / views", where suggestions vary from using the include function or create a service. Problem is I have no idea what would best practise or if it's even necessary for my case.
The menu + input field is another view. It should have its own controller. Based on the route – $on($routeChangeSuccess, ...) – you can use ng-switch to switch between the appropriate HTML/template in that view. If your templates are large, you can use ng-include inside the ng-switch directives. Otherwise don't bother, and just in-line the HTML inside each ng-switch-when.
For an example of how so use $routeChangeSuccess (but not ng-switch), see https://stackoverflow.com/a/11910904/215945
I have a Prism/SL3 application with a tab control and each page of the tab control is a "Region" that has its own view and viewModel. when I want to validate the main page, I call dataForm.ValidateItem(), then I go to all the child views and do the same. the problem is, only the pages which user has clicked on them (on the tab page), get instantiated and the pages that are never shown, don't have their view instantiated, thus I can't validate them.
any help?
I created a psuedo work around for this. It's very hacky, but it does work. My example involved walking the visual tree (up and down) to find respective controls that are invalid and then "expanding" the selected item. I have used an accordian in my example, but have also tested this with tab:
http://thoughtjelly.wordpress.com/2009/09/24/walking-the-xaml-visualtree-to-find-a-parent-of-type-t/
HTH,
Mark
EDIT: Link updated.