I am trying to implement Wayfinder to display on a select few resources.
I have it set up as such:
[[Wayfinder? &startId=`0` &level=`3` &includeDocs=`1,9,4,14,17,21,10,11`]]
But only the first level resources show in the menu.
Does anyone know what I've done wrong?
How deep into the site are the includeDocs? What happens if you set the level to 0.
First of, should the resources be showing? They're not hidden from menu?
Second, have you customized the TPL's used by wayfinder somehow? Maybe you've forgotten the [[+wf.wrapper]] that needs to be placed in each &rowTpl= to continue nesting.
Third, &includeDocs= only include those specific docs, not their children. The &level= parameter only works from the specified &startId=. I believe you have to modify your wayfinder snippet to include all the children docIds aswell, (i think they will be placed correctly in the tree).
Related
What is CollapsingToolbarLayout's toolbarId for? I can't find any description in Google and my AppBarLayout/CollapsingToolbarLayout works properly without it.
I figured it out myself by looking into the source code of CollapsingToolbarLayout (CTBL).
CTBL in fact doesn't need a toolbarId set explicitly because it searches for a toolbar in its child views if no id is set. However, by setting a toolbarId we can optimize our code because then the CTBL doesn't have to search itself (which happens repeatedly).
https://github.com/material-components/material-components-android/blob/master/lib/java/com/google/android/material/appbar/CollapsingToolbarLayout.java
I have multiple buttons and form inputs in one page. All these buttons and form inputs need to be disabled or enabled depending on a condition.
I know that it is possible to use the disabled keyword inside a tag to disable a specific input or button. Also, I can just add the code
:disabled="true"
to disable the inputs depending of the boolean value of a variable.
However, this solution is not acceptable for me, since I will have to add this line of code to every inputs on my page (I may create new pages in the future, containing as many inputs).
I would like to know if there's a way that allows me to simply disable the parent container of all the inputs so that the children item (the inputs) are disabled.
If you inspect the Vue instance itself of the VM when running your code you can have something like this when you console.log(this),
It will give you output similar to this if you use the correct scope:
{
$attrs
$options
.......
$el
}
Inside $el there's object properties for accessing firsElementChild, previousElementChild, previousElementSibling, etc. There's a lot of HTML related properties, however, accessing HTML element this way can get messy pretty fast. I think that your best solution is the one you already mentioned or changing the CSS class dynamically.
If you use v-if to conditional render on a parent you can achieve pretty similar functionality too.
See: Conditional rendering
I make a table with dojo script, but it should see the diferent order of pagination options as that: 1. the page navigation choices, 2. page length menu and, 3. current position display.
I need help with that, how can I change that?
http://dojotoolkit.org/reference-guide/1.10/_images/pagination_ui_overview.bmp
In order to customize/modify an existing dojo widget you will need to manipulate the dom.
In this specific case you should use selectors like dojo/dom and dojo/query to select the portions of the grid you wish to move and then use dojo/dom-construct to place them in the correct location.
domConstruct.place(pageNavigation, positionDisplay, "replace");
Here is a jsfiddle which demonstrates a portion of what you are trying to accomplish and is a good starting point http://jsfiddle.net/kagant15/u6edz0b9/
Still getting to know Orchard, I've now managed to create a custom default page using a module and routing rules.
Although Orchard properly shows my page, it also renders three what seem to be default widgets, with the headings "First Leader Aside", "Second Leader Aside", "Third Leader Aside". Ok so apparantly you need to overwite that default behaviour or something like that, but I can't figure out how.
So is there something wrong / missing with my module, or do I need to provide a setting or something like that?
If a widget is in the default layer, it will appear on every single page in the site. See http://docs.orchardproject.net/Documentation/Managing-widgets
You will need to put these widgets in a different layer that is defined by a rule that fits what you want.
I have a kentico CMSListMenu which contains 4 levels at it deepest, i want to display the menu as a nested list down the left hand side of my content, this works fine for 3 levels but i cant get the 4th level to display.
I have this working on another site using the exact same code so i must be missing something, these are the menu expressions i have tried using:
<cc1:CMSListMenu ID="CMSTreeMenu1" runat="server" Path="/{0}/{1}/{2}/%" DisplayHighlightedItemAsLink="True" DisplayOnlySelectedPath="true" Indentation="0" MaxRelativeLevel="5" /></cc1:cmslistmenu>
<cc1:CMSListMenu ID="CMSTreeMenu1" runat="server" Path="/Products---Solutions/%" DisplayHighlightedItemAsLink="True" DisplayOnlySelectedPath="true" Indentation="0" MaxRelativeLevel="5" /></cc1:cmslistmenu>
do i need to set this somewhere else? perhaps somewhere inside of kentico to output so many levels down?
Any help would be greatly appreciated, this has been causing me problems for days
I believe that the CMS List Menu only displays cms.Page (Menu Item) documents by default. If you're trying to display other types of documents, make sure you set that in the menu properties.
Try setting DisplayOnlySelectedPath="false" to see if it displays everything as you expect it to under the menu.