dudaster
Forum Replies Created
-
Hi!
Thank you for pointing this out, and I completely understand your concern.
The intention is not to suddenly remove long-used features and leave users without an alternative. The plan is to move legacy features into independent ECS modules, so each feature can be enabled or disabled as needed.
We’ll do our best to make this transition seamless, so existing users don’t have to change their workflow or manually migrate anything.
I’m also very open to feedback. What is your favorite feature from the legacy version, and what do you think could make it even better?
Thank you for reporting this and for the detailed root cause analysis.
You are correct. The Container Layout module registered add_filter( ‘elementor/frontend/container/should_render’, ‘__return_true’ ) unconditionally, forcing every Elementor container to render and overriding third-party conditions, including Essential Addons conditional display.
The fix is now in: the filter is replaced with a conditional check that only forces rendering on containers that actually have an ECS slider or custom layout mode set. Plain flex and grid containers now respect the original should_render value, so EA conditions work correctly again.
The fix will be in the next release. Thank you for taking the time to dig into this.
Hi, thanks for reporting this.
To help narrow down the conflict, could you share a few details?
1. Which version of ECS is currently installed when the issue appears?
2. Which ECS modules do you have active (ECS > Modules in wp-admin)?
3. What exactly breaks — are the elements always visible, always hidden, or something else?
4. Any JavaScript errors in the browser console (F12 > Console) when the page loads?In the meantime, you can try disabling ECS modules one by one to isolate which one causes the conflict. The most likely candidates would be Container Layout or Container Responsive, since those hook into the Elementor render pipeline.
Version 4.1.11 is live on ww.wp.xz.cn now.It specifically fixes the Fill Width (stretch) dropdown issue. The CSS rule that forced width: 100% and left: 0 on the dropdown panel was applying to all nav menus with Fill Width enabled. In 4.1.11 it is scoped to ECS dropdown layout mode only, so it no longer interferes with other menus.Please update to 4.1.11 and let me know if the Full Width option works correctly for you.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] Updates Broken WebsiteGlad to hear the update resolved it. The warning in controls-stack.php line 672 was fixed in ECS 4.1.10, now available on ww.wp.xz.cn. Please update if you have not already done so.
Thanks for the report. This is fixed in ECS 4.1.10, now available on ww.wp.xz.cn.
The warning was triggered when ECS registered responsive color controls on the nav menu widget using position anchors that point to tab-type controls. These controls have tabs_wrapper set but no inner_tab, so Elementor’s get_position_info() accessed an undefined key in PHP 8.x. The position anchors are now updated to reference controls that have both tabs_wrapper and inner_tab set.
Please update to 4.1.10 and let me know if the warning is gone.
Thanks for the report. Both issues are fixed in ECS 4.1.10, now available on ww.wp.xz.cn.
The alignment reset was caused by a global CSS rule with a flex-start fallback that overrode the existing alignment whenever the Elementor CSS cache was stale. Alignment is now applied via direct Elementor selectors, so it only takes effect when the user has explicitly set a value.
The mobile trigger issue should also be resolved. The mobile breakpoint logic is now scoped so it does not interfere with nav menus that are not using the ECS layout controls.
Please update to 4.1.10 and let me know if both issues are resolved on your end.
Hi, thanks for the detailed report. New update coming soon.
- This reply was modified 4 weeks ago by dudaster.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] Menu Responsive – another oneHi, could you describe what breaks exactly when the WordPress Menu Responsive module is active? Does the hamburger icon not appear at mobile breakpoint, or does the menu not open when clicked?
Also, which breakpoint is set in Elementor for the mobile menu toggle? That will help us narrow it down.
Hi, the update notification issue is resolved in the latest ECS version. Please update ECS to the latest version and the notification should go away.
For the mobile menu issue, could you describe what breaks exactly? Does the hamburger icon not appear at mobile breakpoint, or does the menu not open when clicked? Also, which breakpoint is set in Elementor for the mobile menu toggle?
Hi, ECS’s Slider mode is CSS-only and does not integrate with Swiper directly, so a recent ECS update alone should not affect it.
Could you clarify which slider you are using? Are you using ECS Container Layout with the Slider layout mode, or Elementor’s Loop Grid with its built-in Swiper slider?
Also, which version of Elementor are you on? That will help us check if there is a CSS conflict on that side.
- This reply was modified 4 weeks ago by dudaster.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] Updates Broken WebsiteHi, sorry for the delay in responding. Several fixes have been released in 4.1.7 through 4.1.9 that address common issues after updating.
Could you share a bit more detail about what broke? For example: what you see on the frontend, which ECS modules are active, and which version of Elementor you are running.
That will help us pinpoint the cause quickly.
Thanks for the report. To help us track this down, could you let us know:
1. Which ECS modules do you have active (ECS in the WordPress admin > Modules)?
2. Which version of Elementor (free) are you running?This will help us identify which control registration is triggering the warning in controls-stack.php.
Forum: Plugins
In reply to: [ECS - Ele Custom Skin for Elementor] Doesn’t work after updateHi, both issues mentioned here are now fixed.
The responsive containers showing on all devices was fixed in ECS 4.1.7. The Container Layout CSS was overriding Elementor’s visibility classes.
The false update notification is also resolved. Please update ECS to the latest version and let us know if anything else comes up!
- This reply was modified 4 weeks ago by dudaster.
Thanks for the detailed report — this is fixed in ECS 4.1.7 (and the current latest is 4.1.9).
The Container Layout module’s CSS was overriding Elementor’s display:none visibility rules. The fix increases CSS specificity so Elementor’s responsive hide/show controls work correctly again.
Please update to ECS 4.1.9 and let us know if it resolves both issues!