Admin View Linked Fields "Admin Behavior - Default" and add content to Joomla administration, data not visible in view #607
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#607
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I have found something within the Admin View Linked Fields "Admin Behavior - Default" and add content to Joomla administration, data not visible in view
Steps to reproduce the issue
Expected result
Admin View
"Here are my thoughts: By leaving the "Admin Behavior" fields "Default". I excepted that it will select a default behavior for example "Show in All list Views" and automatically provide an order "Order in List views" I don't see any changes here, also not after looking at it when saved.
But within Joomla it is perfectly in good condition.
Add content to joomla
The movie be added to joomla and shown in the list view.
Actual result
No items created within joomla and not shown in the list view. Also not searchable within Joomla
Looking at the MySQL database the movies are added
System information (as much as possible)
Additional comments
Workaround
For the Admin Behavior fields, select an option for example; Show in All list Views. Don't use "Default"
Expected solutions
Change the "default" value to "select a behavior view"
or
Code needed to be looked at, as it is working almost as expected
I have followed the demo and the important instructions from YouTube. Also tried to built a movie database myself by testing component builder step by step. Also to get a better understanding and feeling of JCB.
Sorry noticed Pull request instructions later and entered an issue here. As i thought this was really an issue.
I am not sure how to answer you, since it seems like we have a few wires crossed here, and I can't in a few words make sure we are on the same page.
The field in question only relates to list views, meaning:
The default behavior is that it does not get linked to any list view, but is in the database, so that is exactly why selecting none of the fields will cause issues. So if we where to rename it, it will be
Not Displayed in any List view but add to databasewhich is to long really... soDefaultseemed simple enough. That said, I can see the wisdom of saying what default means.. so let me see... all field are originally added withDefaultselected, so we could change the column name to be more descriptive, like.... ahaaa I have no idea.But just changing the word
Defaulttoselect a behavior viewwill make it even more confusing as the field deals with both list view linking, and database linking. The first four options (Default, Show in All List Views, Only in Admin List View, Only in Linked List Views) are all going to link the field to the database, but only the second, third, and forth options (Show in All List Views, Only in Admin List View, Only in Linked List Views) will add the field in a list view.The first option (Show in All List Views) of the list views will make sure the field gets added to all list views that could be build. The second option (Only in Admin List View) of the list views will make sure the field gets added to only a normal list view like seen above. The third option (Only in Linked List Views) of the list views will make sure the field is only shown when this admin view is linked into another admin view, via the linking system of JCB.
But all five options (Default, Show in All List Views, Only in Admin List View, Only in Linked List Views, None DB) will add the field in the edit form view.
Yet the last option (None DB) will not add it to the database nor to any list views. But this is in fact the advance option, as JCB has at field level the option to set how a field should be modeled:
Then there is also the field relationships option:
This allows for you to customize the list views of fields to combine them in one column, or to add even more modeling on a field before display... really a powerful area.
So yes we can do more to explain what default means... But I tend to get to technical and find it hard to explain things without making a video seeing that we are often faced with a very great deal of issue all bearing on each other. Having written this up her made me think that JCB needs a lot of work to make it user focused... as it was originally intended for private use only.
After reading all this what are your first thoughts that comes to mind? and how will this help solve this issue?
Let me know if you have any further questions.