Hello Ele Custom Skin Pro team,
We’re experiencing a critical issue with Ele Custom Skin Pro that causes some items in our loop to display the wrong post data — specifically, ACF fields from the first published post instead of the correct post in the loop.
Environment
• WordPress: (latest version)
• Elementor: (latest version)
• Elementor Pro: (latest version)
• Ele Custom Skin: (exact version)
• Ele Custom Skin Pro: (exact version)
• Advanced Custom Fields Pro: (latest version)
• Advanced Custom Fields: Extended: (latest version)
Troubleshooting already attempted
• Verified ACF fields and field keys — all correct.
• Regenerated Elementor CSS & Data.
• Cleared all caches (server, browser, and Elementor).
• Rebuilt the template from scratch.
• Disabled AJAX pagination and Masonry — no change.
• Tested with all other plugins disabled (except Elementor + ACF + ECS) — issue persists.
• When we place the ACF fields directly inside the loop item (not via nested template), the problem disappears.
Are you aware of this bug?
Hello Ele Custom Skin Pro team,
We’re experiencing a critical issue with Ele Custom Skin Pro that causes some items in our loop to display the wrong post data — specifically, ACF fields from the first published post instead of the correct post in the loop.
Environment
• WordPress: (latest version)
• Elementor: (latest version)
• Elementor Pro: (latest version)
• Ele Custom Skin: (exact version)
• Ele Custom Skin Pro: (exact version)
• Advanced Custom Fields Pro: (latest version)
• Advanced Custom Fields: Extended: (latest version)
Troubleshooting already attempted
• Verified ACF fields and field keys — all correct.
• Regenerated Elementor CSS & Data.
• Cleared all caches (server, browser, and Elementor).
• Rebuilt the template from scratch.
• Disabled AJAX pagination and Masonry — no change.
• Tested with all other plugins disabled (except Elementor + ACF + ECS) — issue persists.
• When we place the ACF fields directly inside the loop item (not via nested template), the problem disappears.
Are you aware of this bug?