Forum Replies Created
-
AuthorPosts
-
LucaBarbi
ParticipantIn my case, I managed to solve it temporarily by adding
selector = selector.replace(/^##/, ‘#’);to line 15 in the file wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js
LucaBarbi
ParticipantIs there any news? We have at least a dozen non-functioning sites. At this rate we will have to switch to another plugin to handle custom fields.
LucaBarbi
ParticipantSame problem here. Is there any news about it?
LucaBarbi
ParticipantSolved! Thank you very much!
LucaBarbi
ParticipantSorry, I believed to find a solution, but didn't work, so my question is still open!
LucaBarbi
ParticipantSolved! The remove button is placed on the outer_html!
LucaBarbi
ParticipantHi Long,
I already tried with the solution you prospect, but the results is similar to set display: none in CSS and this solution doesn't impact on load time.
What I expect to find, is a solution that consent me to completely prevent loading the custom fields until user explicitly make a request for clicking the button (then I retrive the code by an Ajax call).
My only problem whit this solution are the remove buttons, because even if the callable function for the filter rwmb_{field_id}_html return null value, the remove buttons are still on page.
So, how can I prevent the load of the return buttons if the callable function return null?
-
AuthorPosts