joomla/Component-Builder
joomla
/
Component-Builder
38
19
Fork 11
Code Issues 42 Pull Requests Projects 3 Releases Wiki Activity
Page: 029 How to overwrite the custom fields
Pages
001 Hello World with Joomla Component Builder 002 Intro to JCB 003 Installation of JCB 004 General Planning 005 Field Types 006 Basic Fields 007 Admin Views 008 Advanced Fields 009 Adding Admin Views to a Component 010 Component Settings 011 Component Scripts 012 Component FTP and more 013 dynamicGet 014 Adding dynamicGet to a Site View 015 Adding Templates and Layouts to a Site View 016 Template Setup 017 Layout Setup 018 Custom Admin Views 019 Adding Site Views to a Component 020 Adding Custom Admin Views to a Component 021 Tweaking MySQL Demo Data 022 Global Settings of Component Builder 023 Adding a custom time field 024 How to integrate the Create User Helper Method in your Components 025 How to use email helper in your components 026 How to setup a store message method along side the email helper class 027 How to ensure that a field is not escaped when added to list views 028 How to change exported values and setup custom import options 029 How to overwrite the custom fields 030 How to filter a list field based on association with another field 031 Automatic import of custom code during compilation in JCB 032 JCB manual custom code implementation 033 Export Import of fully mapped components 034 How to add Custom Buttons in JCB to your component Admin Area 035 Translation Mananger in JCB explained 036 Setting Site View Permission 037 Auto create SQL updates for Componets in JCB 038 Setup Site Edit View in JCB 039 Automated backup system in JCB 040 Adding Helper Structures to any JCB component 041 Upgrade to JCB v2.5.8 and using the new Admin View and Admin Fields 042 How to setup tabs after upgrade to v2.5.8 in JCB 043 Major Release of JCB v2.6.0 044 Hello World Component with Joomla Component Builder Creator Extended 045 Adding your own rule validation to a field in JCB 046 General overview of how community snippets work 047 Tutorial on forking JCB snippets so you can share your snippets with the rest of the Community 048 Tutorial on making a pull request at Joomla Component Builder Snippets 049 The New Library Manager Area 050 Easy Translation via excel 051 Dynamic Router Implementation Explained 052 Automated database updates in Joomla during development of a component 053 Quick Subform Demonstration 054 VDM Package Import Option 055 Dynamic File and Folder Inclusion concept 056 How to use the file field type to upload a file in JCB 057 Drag and Drop Upload functionality in JCB 058 The Quick Hello Word with JCB 059 Adding none database fields to an admin view 060 The custom dashboard option in JCB 061 Add or Remove Prefix to Component Name in Joomla Menu 062 Add your own JCB packages to the JCB Communty Directory 063 Proposed Collaborative Workflow in JCB 064 How to install jcb packages 065 JAB18 Using Joomla Component Builder 066 The new fields Area to make things easier 067 Adding Language String to your Component and get the Language Placeholder for dynamic use 068 Library Manager Anticipated Functionality 069 Join Fields in the admin list view with field relations 070 How to change the License Template in JCB 071 Reuse Custom Code 072 Setup Local Development Environment with Bitnami 073 JCB Fields Type Extended 074 How to add Joomla Custom Fields 075 Expand Custom Field Type Beyond The Default 076 A Quick Demonstration to Load a List of Items in a Site View 077 Run Expansion Explained 078 How to Add a Form to a Site View 079 Update the Site Form Field via URL Parameter 080 How to Add More Helper Methods to Your Components Helper Class 081 Easy Validation Rules for Fields in JCB 082 New Placeholders Feature 083 Manage a Components Global Config Option Field in Relation With Menu Params 084 Default Database Values can be set per Field Type Beta Testing Component Settings Develop a Joomla Component Guide to use the Component Builder Developing with Joomla Component Builder Home PHP Settings TIPS: Custom Code Using the JCB Demo Component While Building Your Local Development System
17 029 How to overwrite the custom fields
Amigo edited this page 2019-08-22 15:46:31 +02:00
Table of Contents

HOW TO OVERWRITE THE CUSTOM FIELDS

Using Default Fields With Custom Code

00:00:00 (Click on these time links to see Youtube video)

It may happen that you would prefer to use some of the default fields in a different manner than that of Component Builder's way of implementation. What are the default fields? 00:00:12 If you add a new Admin View or go to an Admin View that already exists, there is this note above Adding Fields. It indicates that the 'ID', the 'asset_id', the 'state', the 'access', the 'ordering', the 'created_by', the 'date_created', 'modified_by', 'date_modified', 'checked_out', 'Check_out_time', 'version', 'hits', 'metakey', 'metadescription', and 'metadata' has already been added to the view. 00:00:41 These are the default fields added to the view even if you do not create them. In fact, it is not necessary to create them. Sometimes you might want to display some of these fields in a different area of the application. Currently, the ID field and the State field are the only fields being shown by default in the List view. 00:01:20

  • Example Of Default Fields Displayed in List view

In the Experts area the 'Id field', the 'Status field', and the Ordering field are shown. The Ordering field does not show the order number. To be able to move and order it, click on "Up/Down". 00:01:45 All that is done by default. The other values are not displayed in the ListView. Once a client requested that it should be possible to see the date on which something had been created as well as the identity of the person who created it. Component Builder then must be adapted so that those things could also be overwritten.

This is what has been done: If a field is created in Component Builder, as a field would normally be created and any of these names should be given to it, 'Created by' or 'Created date', but exactly the same name. 00:02:23 Then it will overwrite the default.

  • Example Create_By Field In View

In this specific Job Order view, there is a field 'Created-by'. It may be opened in a new tab. There is also a field 'Created-date'. 00:02:57 In this field the 'Name', 'Created_by', and 'User' are the types of fields that are used. The label is 'Created by', and the user that 'Created this' is the description. 00:03:26 That's all that is needed for a user type. In the 'Created-date'(which is a calendar type,) 'Created', the date, it was created, the label and some of its defaults are used.

Compiled In Code

00:03:46

If these values are unknown it can be seen in the compiled field. 00:03:51 Open 'Administrator' in the back end of the component and open the relevant component. If 'Models' is opened, there is a place called 'Forms'. When it is opened, a list of forms may be seen that correspond to the back end views that you have created. In this instance, this 'Job Order' is the one. 00:04:19 Open the XML, double click on it and scroll down. 'Modified by' and some of its default can be seen. So this value must be overwritten; these values must be updated or used. 00:04:45

NB. This is the only part that should not be changed. If it is changed, it will not be known if an attempt has been made to overwrite one of the default fields because it uses the name as the identifier. Back in Editing, the fields that were created was the first part. Close them again.

Adding The Fields

00:05:06

When any other field is needed go to fields. (If 'Settings' is selected in Editing the Admin view.) Those fields can be added. The 'Created-date' and the 'Created-by' is there. Both are added to be shown, as is the position and how it should be treated. It had been set in the 'left tab' of the '15th'.

Adding In Tabs(default 15 tab)

00:05:41

If you would like the fields to be displayed in the same place as before, in the Edit view, add it to the '15th' tab. It is unlikely that so many tabs would be created.
What is a tab? If you would go to the view, these are tabs 1 2 3 4 5 and 6. Since publishing may vary. 00:06:14 It does not make sense to target it in any way directly as the 5th of the 4th. So a high number like 15 is chosen. If number 15 is selected, it will add these two fields in the same place it would have if it had to build it for you. But if for some reason the field should be displayed in a different tab, it may be selected, placed in the 3rd tab, and saved. 00:06:53 Compile the components and install them. 1, 2, 3, will appear in the third tab. Indicate in what tab it should now be displayed. Now the 'Create' date no longer shows in the 'Publish' tab. It is only created by what shows up here. (See video.) 00:07:24 The field is moved to a different tab, and displays the field in the List view as well because the fields were added and set to be displayed and added to the third tab. It is moved back to number 15 which is its default place. Save, compile, and install it. 00:08:03 Update the component. Refresh the page. It is no longer seen in 'Documents', 'Production', or 'Stock list'. It is back in 'Published', the correct place. There it will be set if it is not overridden, using the 15th tab as the target places it in its default place. If another tab number is used, it removes it from its default place and puts it where it is assigned. That is how you can overwrite the Custom Added Fields in the back end view. 00:08:49