AdvancedCustomFields / AdvancedCustomFields/acf

Please help me answer this conundrum about ACF Field và SubField. Please Please Please :(

Open
#799 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
945
Forks
197
PR merge metrics
No merged PRs in 30d

Description

Please help me answer this conundrum about ACF Field. I have searched in many places but there is no answer, I can only hope in this place.
Please help me :(

Question: Should I name the SubField of the Repeater Field a simple separate name like: Title, Image... or should I include the parent field in it like: Parent_Subfield???

Case 1: If I name Subfield as a simple name that does not include parent fields like Title, Image... but they will overlap and be the same as Subfield names in other groups of fields with the same subfield as Title, Image. ... I'm afraid this will cause an error because ACF recommends that field names should be unique.

Scenario 2: If I set a Subfield with a name that includes the parent field name along with a child field like parent_subfield - then I should be able to create unique field names and not confuse subFields in other field groups. But the problem here is that if used together with the parent field name in the child field, it will make the field name sometimes very long and confusing (especially with many layers of field groups and many repeating fields with subfields in the field). my project)
Example: Field group name is Movie - group field is Video - repeat field is Hero Banner - Subfield is will be Image
Then the name of the Image field will be movie_movievideo_movievideoherobanner_image

It is very long and very confusing!

I hope I have described it clearly enough for you to understand this dilemma
So please give me the best solution for this?
Once again I would like to thank you very much ^^

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names ACF Field, SubField, and Repeater Field but provides no repository file, test, or entry point. Start by locating the relevant ACF field-name documentation or implementation. Done would require a maintainer-confirmed naming rule, ideally documented for future users.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.