Thread Starter
YuMyo
(@nikho)
Since the error seems being not blocking (post save or update action), I came up with a kind of fix (shame) adding !important to line 52 of global.css in advanced-custom-field-pro/css/global.css
So turning:
.acf-visible { display: block; visibility: visible; }
.acf-hidden { display: none; visibility: visible; }
in:
.acf-visible { display: block!important; visibility: visible; }
.acf-hidden { display: none!important; visibility: visible; }
prevent inline styles injected by Tabify to overwrite ACF styles.
There’s still the need to inspect if this could be enough or there’s any other compatibility issue especially concerning data.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
After upgrading ACF to Pro 5.0.2 (WP 3.9.1, Tabify 0.8.1):
For pro or commercial product support please contact the author directly on their site.
http://support.advancedcustomfields.com/
As the author is aware, commercial products are not supported in these forums. As you are their customer I am sure they will have no problem supporting you there.
Thread Starter
YuMyo
(@nikho)
Thank you Jan, you’re right but ACF 5 Free & Pro version just differs by addons inclusion over the same code base. Since the issue reported here is not directly connected to any of the ACF addons, I think it could be still considered relevant for this board.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
If you stick 100% to the version here without the addons then yes, I agree with you. The code in the WordPress repo is supported here. Include code from outside of the WordPress repo? Nope.
If the author begins supporting his addons or pro version in these forums then the author will get a shoulder tap asking for that to stop. Commercial products, and that includes addons are just not for here.
Edit: Looks like support won’t be in these forums. Give this a read.
https://ww.wp.xz.cn/support/topic/please-visit-the-official-support