Automatic Child Record (resolved)

[automan25]

In the database I've set up I have two lists in a one to many relationship. One is the parent list (the one side), the other is the child list (the many side). I have created a left side join from the parent list with cascade delete selected. When I create a new parent record, Fabrik automatically creates a blank child record. This behavior is undesirable in my situation. Does anyone know why this might be happening?

 

[cheesegrits]

In the Group settings for the group we automatically create when you create a list join, for the repeated (child) group, what do you have "Min repeat" set to?

Try setting it to 0.

-- hugh

 

[automan25]

Min repeat was set to blank. I changed it to zero, but there was no change; one child record was created with a new parent record. Interestingly there is another child list attached to the parent list that does not generate a blank record when a new parent record is created.

 

[troester]

You have to set the min repeat for every group separately.
Setting the min won't delete already existing "empty" child records.

 

[automan25]

I have since tested this thoroughly with new parent/child lists. min repeat is set to 0 for all groups involved. As before, every time a parent item is created, a blank child item is created right along with it.

 

[troester]

It's working.
A new record is showing "no data" in the repeat group an no child record is created.

I assume you have JS issues.
Are you running default J! template (Protostar) and default Fabrik bootstrap form template?

 

[automan25]

Thanks for your investigation into this troester. I appreciate it. I've been using the Gantry 5 Hydrogen template. Just to verify my results though I set up a sandbox site with default everything, including using Protostar. I created a simple make/model automobile database using two tables. These are structured exactly as the ones are on my other site that I'm having trouble with. The results are the same. When I create a make (parent record), say Honda, then a blank model (child record) is created. Perhaps we've been talking apples and oranges somewhat so far and that is why we're getting different results.

You can access the site at:
joomla.automan25.com

feel free to explore the back end too at:
joomla.automan25.com/administrator

login: visitor
password: visitor

 

[troester]

You shouldn't post access data in the forum (you can put it in your-site).
You had set the child group layout to display=no.
You must display the child group (may be hidden), otherwise the default 1. group can't be "deleted"

 

[automan25]

Thanks for taking a look. I'll play with the hidden feature and make sure not to post login credentials in the future. I appreciate the help.


Sent from my iPhone using Tapatalk

 

[automan25]

I finally got this figured out. Although the items mentioned above did affect the issue, the real culprit was the Gantry 5 template I was using. I switched back to an older version of the template and now everything works just fine. Who would have though?

 

[cheesegrits]

Hmmm. I need to take a look at that. We should be (more or less) copacetic with Gantry 5.

But yes, templates can have weird effects, even with stuff like that, if they mess with the DOM structure. Some templates do nasty stuff like inserting wrapper divs and otherwise screwing with the DOM structure in page content, which can have weird side effects on JavaScript that relies on that structure (which some of our repeat group code does).

-- hugh

 

[kimbare]

I'm having this exact same problem - getting blank children records every time I create a new parent record - only I have types of 2 children attached to the parent, so I get 2 blank children (1 of each type) being created each time I create one of the parent records. I'm using Gridbox and based on other issues I'm having I think many of my problems with Fabrik are actually related to using this product as my page builder/template (they say it's a website builder, not a page builder and template). Crap!

Update: I'm trying another template and page builder and the problem seems to have stopped.