-
-
Notifications
You must be signed in to change notification settings - Fork 178
029 How to overwrite the custom fields
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 is the default fields? 00:00:12 If you go to add a new Admin View or to an Admin View that already exists, it may be seen that 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' is already added to the view. 00:00:41 These are the default fields that always gets 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 is the only field that is been shown by default in the List view. 00:01:20
In the Experts area the 'Id field', the 'Status field' and as well as the Ordering field are shown. The Ordering field does not show the order number. To be able to move and order it, click on that "Up/Down" button(see video),. 00:01:45 All that is done by default. The other values are not displayed in the List View. 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 needed to be adapted so that those things could also be overwritten. What has been done is: 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 override the default.
In this specific Job Order view, there is a field 'Created-by'. That may be opened in a new tab, there is also a field 'Created-date'. 00:02:57 So in this field the 'Name' and 'Created_by', and 'User' is the type of field that is 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. Then in the Created-date, it's a calendar type. 'Created', the date, it was created, the label and some of its defaults are used.
If these values is unknown it may be seen at the compiled field.00:03:51 Open 'Administrator' that is 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 needs to be overwritten. Then these values need to 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 a attempt has been made to override one of the default fields because it uses the name as the identifier. Back in Editing the field, the fields that were created was the first part. Close them again.
When any other field is needed simply go to fields (if 'Settings' is selected in Editing the Admin view) then those fields can be added. 00:05:08 There's the 'Created-date' and there is the 'Created-by'. Both is added to be shown, and also the position and how it should be treated. It had been set in the 'left tab' of the '15th'. 00:05:37
If you would like the fields to be displayed in the same place as before, in the Edit view, then add it to the '15th' tab. It very unlikely that somebody would create so many tabs. Now what is a tab? If you would to go to the view, then this is tab 1 this tab 2 3 4 5 and 6(see video). Since publishing may vary. 00:06:14 It wasn't making any sense to me that I would It does not make sense to target it in any way directly as the 5th of the 4th. So a very high number 15 is chosen. If number 15 is selected, it will add these two fields in the same place it would 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 and put in the 3rd tab and saved. 00:06:53 Compile the components and install it. Then 1, 2, 3, will appear in the third tab. Then indicate in what tab you would like it now to display. So 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 gets moved to a different tab, and displays the field in the List view as well. Simply because the fields were added(see video) and set to be displayed and to be added to the third tab. It is moved back to number 15 which is its default place. Save it, compile and install it. 00:08:03<<<<<<<<<<<
Basically updating the component. Refresh the page, if we go to where it was, it's no longer showing there(documents), it's not showing there(production), It is not showing there(stock list), it's back in published in the correct place. That's where it will be set if you don't overwrite it. Using the 15th tab as the the target puts it's in default place. If you use another tab number, it removes it from its default place, and puts it where you have assigned it to be placed. That is how you can overwrite the custom added fields, fields of a back end view. 00:08:49 I hope that will be very helpful.
- Home
- Beta Testing
- Custom Code
- PHP Settings
- Demo Component
-
Tutorials
- Hello World JCB
- Intro JCB Guide
- JCB Installation Steps
- Planning Components
- Field Type Overview
- Basic Fields Creation
- Admin View Management
- Advanced Field Usage
- Admin Component Integration
- Component Setting Customization
- Scripting Components
- Component FTP Options
- Dynamic Get Method
- Site View DynamicGet
- Site View Templates
- Template Setup Guide
- Layout Configuration Steps
- Custom Admin Management
- Adding Site Views
- Custom Admin Integration
- MySQL Demo Tweaking
- Global JCB Settings
- Custom Time Field
- User Helper Integration
- Email Helper Usage
- Message Store Email
- List View Unescape
- Export Import Customization
- Overwrite Custom Fields
- List Field Filtering
- Automatic Code Import
- Manual Code Implementation
- Component Export Import
- Custom Admin Buttons
- Translation Management
- Site View Permissions
- Component SQL Updates
- Site Edit Configuration
- JCB Backup System
- Helper Structure Integration
- JCB v2.5 Upgrade
- Tab Setup Guide
- JCB v2.6 Release
- Extended HelloWorld
- Field Rule Validation
- Community Snippets Intro
- Snippet Forking Tutorial
- Pull Request Snippets
- Library Manager Area
- Excel-based Translation
- Dynamic Router Details
- Database Auto Updates
- Subform Quick Demo
- VDM Package Import
- Dynamic File Inclusion
- File Field Upload
- Drag-n-Drop Upload
- Quick HelloWorld JCB
- Non-database Fields
- Dashboard Customization
- Menu Prefix Toggle
- Community JCB Packages
- Collaborative JCB Workflow
- JCB Package Install
- JCB JAB18 Event
- Convenient New Fields
- Component Language Strings
- Library Functionality Anticipation
- Join Field Relations
- License Template Change
- Code Reusability
- Local Dev Environment
- Extended Field Types
- Joomla Custom Fields
- Custom Field Expansion
- Site View Listing
- Run Expansion Method
- Form Site View
- Field URL Update
- Additional Helper Methods
- Field Validation Rules
- New Placeholder Feature
- Component Config Params
- Per-field Default Values