ACF and Elementor Front-End Rendering Issue
Budget: $30 – $100 USD
We are currently seeking a WordPress Developer with extensive experience in troubleshooting and resolving issues pertaining to the Advanced Custom Fields (ACF) 'flexible content' widget within our Elementor template. The ideal candidate will demonstrate an understanding of WordPress, Elementor, ACF and Anywhere Elementor.
**Scope:**
We’re experiencing a bug when using multiple elements in an ACF flexible content module. The subfields from one element—like a customizable divider line—overwrite any other instance of the element. We want to be able to ensure each instance has its own ID and retains the settings entered into the subfields.
**Our Setup:**
- Elementor page template has a “flexible content” widget installed from Anywhere Elementor
- The AE flexible content widget is allowing us to add pre-built modules into the final Wordpress page. The first example we have set up is a line divider. When you add a line divider via the flexible content widget, you can then customize the line width, line thickness, line style and line color via ACF subfields.
- These subfields are created in the database via ACF Pro
- Connecting the Elementor page with the ACF subfields is an Anywhere Elementor template that will load in the pre-designed line divider
- The Anywhere Elementor template for the line divider is using dynamic tags to set the divider width (a selector field type), line thickness (a container with display conditions), line style (a selector field type) and line color (a color picker field type).
- The final Wordpress page displays the added line divider with the customized width, thickness, style and color. Authors then have the ability to added multiple instances of the line divider and reorder each instance within the module.
**Bug to Solve:**
- When we add multiple dividing lines via the flexible content widget to our Wordpress page, our subfields are not controlling each instance individually. The first line divider’s settings (width, thickness, etc) will overwrite any other line divider element on the widget. We would like each instance from the flexible content widget to be unique.
**Scope:**
We’re experiencing a bug when using multiple elements in an ACF flexible content module. The subfields from one element—like a customizable divider line—overwrite any other instance of the element. We want to be able to ensure each instance has its own ID and retains the settings entered into the subfields.
**Our Setup:**
- Elementor page template has a “flexible content” widget installed from Anywhere Elementor
- The AE flexible content widget is allowing us to add pre-built modules into the final Wordpress page. The first example we have set up is a line divider. When you add a line divider via the flexible content widget, you can then customize the line width, line thickness, line style and line color via ACF subfields.
- These subfields are created in the database via ACF Pro
- Connecting the Elementor page with the ACF subfields is an Anywhere Elementor template that will load in the pre-designed line divider
- The Anywhere Elementor template for the line divider is using dynamic tags to set the divider width (a selector field type), line thickness (a container with display conditions), line style (a selector field type) and line color (a color picker field type).
- The final Wordpress page displays the added line divider with the customized width, thickness, style and color. Authors then have the ability to added multiple instances of the line divider and reorder each instance within the module.
**Bug to Solve:**
- When we add multiple dividing lines via the flexible content widget to our Wordpress page, our subfields are not controlling each instance individually. The first line divider’s settings (width, thickness, etc) will overwrite any other line divider element on the widget. We would like each instance from the flexible content widget to be unique.