ModX getResources startId error - modx

I'm having trouble with my getResources call. It should start at the top of the menu, and display each direct child. Here's the call:
[[!getResources?
&parents=`1`
&depth=`depth`
&limit=`0`
&tpl=`Home`
&tpl_2=`Section2`
&tpl_3=`Section3`
&tpl_4=`Section4`
&tpl_5=`Section5`
&tpl_6=`Section6`
&tpl_7=`Section7`
&includeTVs=`1`
&processTVs=`1`
&includeContent=`1`
]]
It displays every resource other than the first correctly, but the first resource uses the right template but pulls from the wrong resource (resource 6, the first child that has children.
Update: It appears now that its displaying the array of info for resource 1 last. Still don't know why it's doing this at all.

Very strange behavior.. you might try:
&tplFirst=Home
&depth should be an integer, unlikely, but could cause problems
check to make sure your first resource is published and not hidden
by default I believe getResources sorts on menuindex - check your indexes [or specify a sort order explicitly - you can't always trust the order resources appear in the resource browser, it may be cached or set to not update on save]
Kind of looks like you are trying to build a menu/navigation, WayFinder will not work for you?
and as always, always-always clear the modx cache....

You did not specify a standard template:
&tpl=`Section`

Related

What's the use of CollapsingToolbarLayout's toolbarId attribute?

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

Is it possible to disable all the inputs from a page with VueJS and BootstrapVue?

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

Wayfinder includeDocs only showing first level reasources

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).

Orchard custom page renders default widgets?

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.

in drupal how to display 2 views with filter exposed in same page/path?

in drupal how to display 2 views with filter exposed in same page/path?
Have you tried having each view as a block? That way it is simple to have two different views on the same page - for example add the blocks to the body and limit them to the specific page. caveat - I don't know if exposing the filter makes using the block view problematic, but it is certainly worth a try.
The way I solved this is described here:
Create a view with two "page" displays
Make sure the filters are identical in both
Under exposed form set "Exposed form in block" to "Yes" in both
displays
Make the second display appear in the footer of the first
Set the exposed block to appear only in the path of the first
display
Now setting filters affects both displays.

Resources