We are evaluating Backpack for Laravel. One missing thing, a showstopper, that we can't find, is, how we can display multiple entities on the same page.
Examples:
- List of persons, i click one person (an action button), and then it routes to a page, where one can edit the persons details, below the edit form show a list of all the person's pets. If I click one of the pets, then below it shows a form where one can edit the pets data.
Two lists, left the "Machines" list, on the right a "Parts" list. If i click a "Machine" item, then it loads it's "Parts" on the right.
Three Tabs, the first shows a detail view of a "Person" entity. The second tab shows a list of the person's friends (also Person entities), the third shows the list of the person's cars.
Is anything like this possible using Backpack for Laravel? Is there a way to include a whole list, or edit form, an action of an entity in a blade template?
Related
I have a list view, showing news of a specific category A.
I want to further limit the list by one additional category the user can select.
I add a category menu to the page. The list view page is the same as the initial list view page.
After the user chooses a category B from the category menu, the page displays the news items with category B.
Instead of this, I want the news items that are of the initial category A and the user selected category B.
How would I do that?
You need to build a link holding both category IDs. Currently it is not implemented that you can provide an additional category.
I am working in a small SharePoint project to let school students pre-order the lunch online.
the main idea is the student can login to a school site, fill an order form.
I try use a list form to do it, just simply put a InfoPath form as web part on the home page.
When students open the site, he can fill the order form directly.
but the problem is the default view of this web part is always the new item form. so when a student already make the order, then login to site again,
how can I let him see his order and edit it instead a new order form.
another way may be use the form library, but i don't know how can i transfer the filed from the form to a list. because at last we still need a list instead a bunch of documents to get the summary of order.
Thank you for help.
Perhaps you can use a custom list and show that on the homepage?
A 'custom list' by default only has a title column but by adding more columns through the list settings you automatically add form fields on its new item form.
Since you are creating an order form you might want to hide the title column. Go to the settings of the list, then advanced settings, allow editing of content types. Then back in the list settings click the 'item' content type, then the title column then click the radio button for hidden.
I am new to Umbraco, and am trying to get to grips with its concepts, in particular how to create lists. For example, you might want a news listing that appears on a page as a list of headlines with mouseover extra content, but you don't want to be able to click on an item and open a full page, it's just there as a list.
You could create a repeating grid of content on the page itself, but that could become unwieldy.
It looks like (correct me if I am wrong) the Umbraco way is to create a parent page, and each news item to be a child page, which can be edited individually, and use a partial view to list them on the required page.
Is this the recommended approach?
If so, two questions :
How do I exclude these news 'phantom' pages from the main navigation - I understand I could set a true/false property on the page with alias umbracoNaviHide and tick this (which excludes it from 'visible' in the queries)
If so, how do I prevent direct access to the news page by its url (the umbracoNaviHide does not prevent the page opening)
Presumably these news pages would show in the back end main view as they would be descendants of the home page?
Any advice welcome!
You can use a Content Repository to hold content objects that won't be pages in your application.
Use following steps:
Step 1: Create the root content repository document type
Go to your backend to the Settings section. Under Document Types create a new type and give it the name Content Elements. After creating this make sure to check the checkbox of Allow at root in order to add this element to your root in the Content section.
Step 2: Add your newly created document type to the root of the content
Go to the Content section and choose to add a new item directly under content ( select the three dots next to Content ).
Select your Content Elements item, give it a name and click save.
Step 3: Remove the checkbox allow at root
You only want to add one Content Reposity item to your root where you will place all items like news, jobs, locations,...
Go to the settings of the Content Elements document type and remove the checkbox of Allow at root.
Step 4: Create a child repository for each type
Using your example I will now create a News document type which will be a child item of the Content Elements repository.
Go to the Document Types under Setting in your backend and choose to add a new document type. Give it a name News and choose save.
In the settings of the Content Elements check the checkbox of the newly created News item to allow as a child.
Step 5: Add the news list in your content
In the content section choose to add a new item under the Content Elements using the three dots.
Select the News item, give it a name and choose save.
Step 6: Create a new document for the news item
One more item is a NewsItem which will hold the properties/information of the item.
Using the same steps of 4 you can easly add this. Be aware that now you have to go to the News item where you will add a check to the NewsItem checkbox to allow as a child.
Also now define some properties of the newsitem.
Step 7: Add newsitems in the content
Using the same steps from 5 you can now add items in the news list.
Step 8: How to place a content element on to your page
If you have created a page you can add a property with a ContentPicker datatype which can be used to select a item from the Content Elements repository. Or using partial views you can create a list from the News to get all items.
Hope this helps!
I'm quite new to MS Access but understand basic dvl concepts. I have a form (SalesOrder) where I can create sales order info. Creating a new sales order populates more than one table.
I'd like to have a two search buttons on the bottom of the form that will display the results of a query (search by customer name or order id). The results of the query need to be displayed in a subform, and once I click on the selected row, it should populate the master form fields with read-only data (i'll have an edit button to change to writable).
Do I simply link a query to the subform? If so, how do I do that? and how do get the event in the main form (the search button click event) to trigger action in the subform?
thanks in advance.
jeff
I would like to bring view details button in my form when right clicked on my form view details should be shown like in standard any form for example when we right click on item number field on the form we have view details option when clicked that opens the details form of that item.
I tried using the normal right click method but could not succeed, please help me how to bring the view details functionality in my custom form.
To have the "View details" standard context menu, the following must be true:
The foreign key (FK) must have a relation defined on the table of the key
The table pointed to by the FK must have a form
The form must have a display menu item
The menu item must have the same name as the table or the FormRef property must be set
The menu item must have security set up, and the user must have read access (or better)
Running the Best Practice check will usually spot the errors.
This blog entry explains it nicely.
You have to create Display Menu Item with the selected form.
Then you can set newly created menu item for the FormRef property of the Table.