Vue3 Multi Tree view selected - vuejs3

i asked before but got no answer,
the only change I want in the treeview coding on the Vuejs official website, I want to apply it as a treeData Array. There is no problem so far, but Example; name: 'My Tree 1', if clicked and then name: 'My Tree 2', If clicked, I want the first clicked My Tree 1 to be closed.
VueJS
Codesandbox

Related

Drupal Webform Preview Page: Adding Bullets on Conditional Elements (theming)

There seems to be some kind of bug in webform or I'm doing it wrong. On the preview page of a webform, conditional based selections like checkboxes still display regardless of whether they are selected by the user or not. The code show in the source and a blank space will show if nothing is selected.
I just created a test page with three select components (multiple select checkboxes with only one choice ) and placed component A checkbox (in a fieldset) is on the level above the other two that are within a fieldset as well.
So for example,
Selection 'A' fieldset
>> Selection 'A' checkbox
>>>> Selection 'B' fieldset
>>>>>>>> Selection 'B1' checkbox (separate component)
>>>>>>>> Selection 'B2' checkbox (separate component)
The conditional set is like so.
IF: >> Selection 'A' checkbox is EMPTY
THEN >>>> Selection 'B' fieldset
ISNT SHOWN
The point of all this is that I need to place the selected options checkboxes in a bullet list but the bullets points still show on the preview page with out the words, even if those answers aren't selected. I added the bullets using css. I think the following code from this link might be on the right track but I'm not sure how to get it to work for the preview page.
https://www.drupal.org/node/79086
function phptemplate_webform_form_50 ($form) {
$form['submitted']['First Name']['#id'] = 'edit-submitted-first-name';
$form['submitted']['Last Name']['#id'] = 'edit-submitted-last-name';
$form['submitted']['Fluent in']['#id'] = 'edit-submitted-fluency';
return _phptemplate_callback('webform_form_50', array('form' => $form));
}
Conditions should work. A temp solution would be to hide both the check boxes if Selection 'A' is empty.

Rearrange child subtab in Netsuite

I have a requirement to have two custom record types under parent subtab arrange in order. I used parent-child relationship but the arrangement of the child subtab is something I couldnt customize. 'test one' and 'test two' are my custom record types, and Parent is item fulfillment record.
I want 'test one' to come first and then 'test two'.
I tried adding a new Subtab via customization under translation and this order customization is not available in netsuite. Am i missing anything?
Please help.
Edit the record
Click "customize" then "customize form" in the top right of the form
Navigate to "Lists" then select "Communication"
You can drag and drop your prefered order from this screen
Name then save the custom entry form
You can then manually select this form for the record or set it as the default form
If a field is visible on the form, then it appears somewhere in the Custom Entry Form screen. Which tab it's on depends on the type of field. It could be under Lists, or Fields, or elsewhere. Look for it.
When you find it, use the Field Group dropdown to move the field between the main view and sub tabs, and drag/drop the field to change its top-down display order. The drag handle looks like ⋮⋮.

Missing Dropdown in Component Styles Tab in CQ5

In the TextImage component, the Style tab has lost the css selection dropdown that used to show up when editing the component. It now just shows a blank area. It should have a dropdown for image alignment (left or right are your choices). This doesn't appear anymore.
This tab is xtype componentstyles (String), so I don't know where it references the source for the dropdown values. My local instance of CQ5 works just fine.
I cannot just add an xtype selection and feed it values because the css that gets added to the JSP code is outside the component's .jsp-specific page
It looks like the componentstyles xtype is driven by the CQ design that is associated to the page. Designs are stored underneath /etc/designs and are assigned through a page's Page properties dialog (cq:designPath property)
Let's look at an example in the Geometrixx website. If you navigate to the English homepage # /content/geometrixx/en.html and add an instance of the TextImage component to the page, you will notice that the Styles tab is empty in the component dialog. Now navigate to the 'Discover Geometrixx' page # /geometrixx/en/company/discover_geometrixx.html and examine one of the two pre-existing instances of the TextImage component. The Styles tab has the image dropdown you mentioned!
So what is the difference between the instances on the 'Discover Page' and the 'Home' page? The answer is in the design definition. If you open up CRXDE Lite and navigate to the Geometrixx design page for the Content Page template (which the 'Discover Geometrixx' page adopts), you will see the following nodes:
/etc/designs/geometrixx/jcr:content/contentpage/par/textimage
/etc/designs/geometrixx/jcr:content/contentpage/par/textimage/cq:styles
/etc/designs/geometrixx/jcr:content/contentpage/par/textimage/cq:styles/imagealign
/etc/designs/geometrixx/jcr:content/contentpage/par/textimage/cq:styles/imagealign/image_left
/etc/designs/geometrixx/jcr:content/contentpage/par/textimage/cq:styles/imagealign/image_right
The design for the Homepage template (which the 'Home' page adopts) is missing this definition.
If you want to continue to use the out of box TextImage component, it seems you will need to have this design configuration set up on all the paragraph systems and templates where the component can go. So for example, if you want these styles to be available to the TextImage component when it is added to the par paragraph system of the Homepage template, you would add similar style nodes to:
/etc/designs/geometrixx/jcr:content/homepage/par/textimage/cq:styles
Alternatively you could just overlay the component and/or create your own. Then for this custom component you could create your own Styles dialog that is independent of the design. You can simulate the out of box behavior by examining the saved JCR property and setting the appropriate CSS class name in your render script.
The problem is that a design path variable went missing. We don't know why or how, but the solution is as follows.
Open up Content Repository
Go to /content/-sitefolder-/ and expand
Click on jcr:content and view properties
Check for attribute cq:designPath and its value
/etc/designs/-sitefolder-; add to properties if it doesn't exist

Determine which (custom) component in a view currently has focus

I'm currently building a Flex 4.5 mobile project including several views and custom written MXML components that can be incorporated dynamically into those views.
How do I determine which component currently has focus, namely has been activated by the user tapping on it?
The background for this is a global search function in the main application. Depending on the results of this search, fields in the custom components are set. Given that I don't want all components in a view to listen to the outcome of that search function, I have to check which one is currently active.
I'm trying to bind the selected object (the result from the search function) to the active component.
Any help would be much appreciated.
Cheers!
You can determine which component currently has focusing using the FocusManager.getFocus(). Conceptually something like this:
var ComponentWithFocus : IFocusManagerComponent= FocusManager.getFocus();

Drupal search only titles

Is there a way for the Drupal search to only search article Titles and Tags.. not the content of the article? Possibly with the Views Module?
I am using Drupal 7. I do have Views installed and Views Search does not work on Drupal 7.
Create a View to search using Title of the Content (page,story,blog,article,book)
Step 1 : Click on Administer
Step 2 : Click on views
Step 3 : Click on Add
Step 4 : Fill in details for 'View name:' , 'View type: ' select 'Node' and hit 'Next' button.
Step 5 : Select 'Page' from dropdown on first column and click on 'Add display' button.
Step 6 : Under 'Basic settings' you can Select Name click 'page' and see below change the name from 'page' to say 'Search_Content' and push the 'update' button.
Step 7 : Under 'Page settings' you can Select Path click 'None' and see below change the name from 'Path' to say 'search_content' and push the 'update' button.
Step 8 : Under 'Page settings' you can Select Menu click 'No menu' and see below select 'Normal menu entry' give 'Title:' for text-field say 'Search' and select a Menu Link: 'Primary links' and push the 'update' button.
Step 9 : Now click the '+' link near 'Fields' column.
Step 10 : Now select 'Node' under 'Groups:' and select 'Node : Title' and click 'Add' button.
Step 11 : You can remove the text from 'Label:' Text-field and make the Text-field blank.
Step 12 : Click the 'Save' button below. Note all these changes are 'temporary' till when you dont press the 'Save' button below.
Step 13 : You will see a new menu link would be created click on it and check the list of
Step 14 : Edit the Search_Content
Step 15 : Now click the '+' link near 'Filters' column.
Step 16: Now select 'Node' under 'Groups:' and select 'Node: Title' and click 'Add' button.
Step 17: Now You will see 'Expose' button and push the 'update' button.
Step 18: Click the 'Save' button below. Note all these changes are 'temprory' till when you dont press the 'Save' button below.
Step 19: Click on same button with menu links the list of Content titles will be listed with Search bar.
That should be a good start.....ref
There's no way using the views UI to search for both using the same textfield. You have to code for that.
The best result you can take with just the UI consists of exposing two different filters, one for the title and one for the tag. I suggest an autocomplete filter for both, this will give the user good flexibility.
Edit:
With the UI: you have to edit the view, add a new filter, choose "title" and then expose it. Then you have to repeat the same for tags.
With the code you have to look at the documentation as it's not trivial to write it here in a few lines of code and it's strictly related to what you're likely gonna do.

Resources