How to implement custom field to show a modal to add a new CRUD? - laravel-backpack

I need to make "add new" button on select2_multiple field. Which show a modal to add new item.
I have no idea how to implement this type of custom field.

You should check out https://github.com/webfactor/laravel-backpack-instant-fields - they've already created a field type with this functionality, but I believe it's only for 1-n relations.
Creating a new field type isn't difficult at all, it's just adding one blade file in your resources/views/backpack/crud/fields folder. Documentation here. That file will include all the PHP and JS logic you want. However, creating this particular field type will be more complicated, it will involve a lot of Javascript, and most likely an AJAX request to a route and controller method you create.
In Backpack v4 we plan for this to be an official feature. We're still 1-2 months away from v4, though.

Related

I addded a custom field in mdl_user in SQL, I want to show this custom field in the frontend, in profile edit page

I am using Moodle 3.8, I added a custom field called razon_social, I just want to show it in the profile edit page, in the optional section.
Custom field added in mdl_user
Section where I want to show my custom field
Does anyone know in which file in .php, do I have to call my custom field?
Thank you very much for your time
I want to do this, I have Moodle 3.8
enter image description here
Adding a custom field to the mdl_user table (or any other core table) is a really bad idea. There are all sorts of ways it can conflict with the core code (particularly for tables which Moodle uses with "persistent" classes, but still a problem in other situations).
Thankfully, Moodle already has a build in custom user field system (using the tables mdl_user_info_field and mdl_user_info_data) and fields defined this way automatically appear on the user profile page (unless you mark them as hidden).
It should be fairly easy to write a script that will transfer the data from the mdl_user field you created, into a custom user field. After that, you can drop the extra field you added.

Backpack crud field that displays an included filtered table

I need to make a new type of field, let's call it included_table. If in Model employees I have a field of type select2 from model Departments, in Departments, I want to have a field of type included_table which displays the table of the employees from that department, in the same way as the crud does.
Is there an easy way of doing this? Or what would be the best way to start?
Thank you.
I don't think there's an easy way to do it. You'd have to code it yourself. You can start from the table field type, put it won't get you very far.
That's because it's a lot more complicated that it looks at first glance. Keep in mind that Backpack create/update forms work with refresh; if you put a table inside one of them, the expected behaviour might be to only "save" the information when you click the final "save" button; but you probably can't do that for the nested entity, because you'd be saving it with AJAX. Plus, you need to build that entire AJAX functionality yourself, including validation. It's not at all more difficult than using plain old Laravel - it's exactly the same. But Backpack won't help very much in this regard.
That being said, you'd probably be better off just putting a button in the list view for each Department, to go edit its employees. That's a lot easier to do, if you follow the nested resources tutorial.
Hope it helps.

SYMFONY FORM - filter attribute form on top with submit button, that provides a table with other form used to edit each row details

I am looking for best practices on SYMFONY FORM handling to achieve the following standard page (surprisingly I haven't found anything similar existing yet on SO).
Here is a shema of what I want to achieve:
As you can see at the top there is a SYMFONY FORM to filter the results that should be displayed.
It displays a table and each tuple of the table should permit to open another SYMFONY FORM kind linked to the tuple.
I am in the process of learning SYMFONY FORM, so far, I can manage to create the top row FORM to set the filter that'll apply to the table display.
But I wonder if anyone has experience on the second part: Displaying the table that embed as well many forms of a similar kind -That seems a bit more complex. I read about TWIG.EXTENSION and FORM.COLLECTION, I'll investigate that. But if someone could save me to re-invent the wheel and lead me to some direct shortcut, I'd be really grateful.
No idea if it's the best practice, but one way to do it would be to create a new property for your entity being listed in this table, called $editionForm (without mapping it to the database) for example.
Then, either throught a custom loop or by listening to a doctrine (or any ORM you use) hydration event (or triggering such an event if you don't use any ORM), fill the property with the generated form, probably within a dedicated service.
Then, just use it in your template like this :
$entity->getEditionForm()->render()

SugarCRM fetching data from outside REST service to subpanel

I'm trying to create subpanel in Account detail view where list of elements is fetched from external REST service.
I know how to define subpanel, but have no idea how to fill it with data from external network source. Was trying to use get_subpanel_data but there I can only change SQL.
Any ideas how can I do this?
When I've done this in the the past, at least with Sugar 6, I opted distinctly not to try to create a true subpanel. The data being loaded is coming from an outside source and is loaded dynamically with the page, so why present it as if it's static data coming from Sugar? Instead, I created a custom Smarty template to use as the footer on the detail page. For such an example, you can check how it works on the Calls Edit View. I think it's the footerTpl parameter in the detailviewdefs.php or editviewdefs.php. I loaded the smarty template by creating a custom detail view for my module, so custom/modules/MyModule/views/view.detail.php - extend the base Detail View class and override the display to feed Smarty new params, then your Smarty template only needs to iterate through and present the data that your view defined.
To be super-hip and abide by MVC, you could even put your custom code into your bean (if it's a custom module) or into a custom controller method, then reference that from the view.detail.php, and still feed it from there to the Smarty template.
Alternatively, you could just load JavaScript into the Smarty template and use the JavaScript to call the third-party service, parse and present it, etc.
I realize this question is a little bit old now however it comes up fairly often so why not provide an answer with a couple possible solutions. I won't get into code but more just into the design theory of how it can work. If someone needs more specific code help then that is another question.
A couple ideas...
As you mentioned you can define a custom Function which will load in Data to the SubPanel from your own SQL Query. That is one method that I just recently got to finally put to use after knowing about it for a good year and a half.
When you go this route, you are restrained to using the Columns in the SubPanel. I assume it is using the actual Metadata files to determine which Field Columns a SubPanel can use so you pretty much need your custom data in a Database table to have the same column names as the fields defined in the SubPanel Metadata.
Obviously this works great in the right situation, however not always and that leads us into the 2nd method I know of.
The other way is pretty much what #Mattew-Poer mentioned in his answer. It means abandoning the SubPanel altogether and instead generating your own HTML. This is by far my favorite and prefered way of doing it and I have been some really custom modules due to this being possible in a custom module! I will show an example below.
(Click HERE to View full size image)
In the screenshot, you can see in this example that I have something looking Similar to a SubPanel however it is not and is much for flexible and easy to customize.
Example, to the far left column in my fake subpanel is image checkboxes. When clicked on, an AJAX request is made to change the Task row Status.
After that, the checkbox image is updated to indicate the new Status state, the Modified DateTime is updated, the Status column has color background SPANS and is also updated with the correct text and background color when the left side checkbox is clicked.
Doing any of this with the standard SubPanels is a complete nightmare and would be difficult to do some of the stuff that you are open to do when you build your own version of a SubPanel.
With that said, I have built an identical clone of the above screenshot using SugarCRM default SubPanels! It was a nightmare. I could easily update the content and HTML in some of the columns. I even had the AJAX click checkbox image to update and do all the other updates I mentioned above. It wasn't too hard and worked fairly good but it had some issues.
When you do inline edit, inline create record, or subpanel paging to load different set of record. You would then lose all the custom HTML formatting that was applied. The reason is, in the SubPanel you are limited to using the After UI load logic hook. So since the "Page" is loaded already, when an AJAX request is made to add/edit the subpanel content or load a new set of items with the paging links. It only loads the SubPanel content on those events and the whole Page content does not reload. Because the logic hook only fires off 1 time after the page loads, this newly loaded subpanel data doe not receive any of your custom HTML formatting.
In my case, this means that nice looking colored background Status spans are lost, the image checkboxes are lost, and some other functionality is lost.
Now to get super technical, I could have gone another 3rd route and instead made new Custom Field Types for each SubPanel filed that I needed to apply custom HTML to. This process is super hard in my experience and in some cases it really isn't the BEST solution.
Because of the reason explained, this is why my new modules use the Custom HTML route to generate my own version of a custom subpanel or whatever Data is needed in my Module pages! So far it is working better than I imagined and has opened doors for me to build custom SugarCRM modules that I previously didn't even realize would be possible to build due to some of the issues I mentioned above. Now I bypass them altogether and open the door to do pretty much anything!
I've got some really cool stuff for SugarCRM in the works right now. If anyone has any questions feel free to ask in a new question or for me personally in a comment here.

Umbraco DropDown List

I have a requirement to store a list of designers with logos and some bio information in my Umbraco CMS. I created a document type called 'Designer' with all those properties. I'd like to now create a dropdown list with those designer names so I can associate it with other document types. How do I create this dropdown? I'm using the v7 of umbraco.
Checkout nuPickers for Umbraco v7. Should have everything you need.
http://our.umbraco.org/projects/backoffice-extensions/nupickers
http://github.com/uComponents/nuPickers/wiki
http://www.nuget.org/packages/nuPickers
Look here for help with creating custom labels using macros
http://github.com/uComponents/nuPickers/wiki/Custom-Labels
As I understand, your intention is to let editors pick designers from the designers dropdown when editing content items in the backoffice.
If so, you may want to either use an existing data type called 'Dropdown' or create a custom data type.
If you only want the names in the dropdown, the default 'Dropdown' data type may suffice. Take a look at the article explaining how to customize the 'Dropdown' data type
Otherwise (say, if you want to show the avatar of the designer in your designer picker), you may want to implement your custom property editor (designers picker) and a custom data type related to it. Then you will be able to associate your data type with any document type you want.
A couple of useful links in this case:
how to create a custom property editor in umbraco 7
the demo which includes building a custom picker property editor to assign custom data to a document
Umbraco v7 XPathDropdownList implementation