Forum Replies Created
-
AuthorPosts
-
Jugibur
ParticipantOk, I found it 2 minutes later 😉
its 'menu_order'
November 5, 2024 at 10:50 PM in reply to: ✅How to prevent the removal of HTML entities / special characters? #46852ParticipantThanks for your fast reply, Peter,
works great!September 10, 2021 at 2:50 PM in reply to: ✅Conditional Logic doesn't work inside group field #30695ParticipantOh sorry, I've overloocked that it's not '==' but '=' to do a simple compare.
It works now – thanks for your hint!ParticipantOh that is great, thanks for your help!
PS: In the documentation it says we have to use 'contains' for some types, i.e. select multiple instead of '=='.
In my case I have just a single value select field (like in the example) but it likewise need 'contains' for value checking.
I'm wondering that the negation '!=' works fine here.ParticipantHello,
that's weird – after updating to the newest version yesterday I found the selection field not compressed but too long. The 100% width is overflowing my sidebar. The edit field has the right width.
Also the wrapper ".rwmb-input" has the correct width, but the selection input inside is to wide.I have noticed that "box-sizing: content-box" is the culprit.
It comes from.edit-post-sidebar *, .edit-post-sidebar :after, .edit-post-sidebar :before, [...] { box-sizing: inherit }Have you also observed this behavior?
I have disabled all custom admin styles.Edit: For now I have overwritten .rwmb-select with explicit "box-sizing: border-box"
Juergen
ParticipantMany thanks, Long, I'll give it a try!
ParticipantYes, for me too, it occurred after updating to the latest Meta Box version.
June 28, 2021 at 12:11 PM in reply to: ℹ️Feature request: Interpret NULL value in field settings to prevent creation. #29162ParticipantThanks Long, yes this could be a way – but please note that my original question was only about controlling the entries in the options field.
So with your way I must repeat the stuff for the radio field just to add the "slider" option (in my example) to the imagepool_type field. But the imagepool_type should always been there. Hope you understand what I mean.
And extending an array down to the "options" is a bit harder / error-prone, but anyway – if it's not possible to extend the behavoir of Meta Box with the null check I try to write an "array builder helper" for my purpose. It was just a suggestion and thought from me for Meta Box.June 27, 2021 at 12:58 PM in reply to: ℹ️Feature request: Interpret NULL value in field settings to prevent creation. #29146ParticipantHi,
thanks for your reply.
Unfortunately conditional logic isn't for the same purposes.
My case is for my customor library, so if someone wants some options, I can active them for his theme.
And the conditional logic only allows me to set a new field for toggle and is needful at runtime – but for a setup configuration (and for adding / removing options in the same field) it isn't made I think.June 25, 2021 at 12:38 PM in reply to: ✅Taxonomy Advanced: Set starting node of categories with query_args #29120ParticipantHi Long,
thanks for your reply! Yes, select_advanced works without errors but missing the hierarchy selection.
I'm using now the 'checkbox_tree' (without 'parent' query_args) and hiding the unwanted items (siblings) with CSS.
It's still not optimal , especially for a lot of items, because it takes up a lot of space, but it's good enough for now.But if I have more time I will take a lock at the docs for a customt type and give it a try.
June 24, 2021 at 4:51 PM in reply to: ✅Taxonomy Advanced: Set starting node of categories with query_args #29106ParticipantI am attaching the following question to this thread as it relates to solving the problem...
Unfortunately the option "parent" in the query_args() limits the hierarchy to the immediately following child-nodes.
My idea is to use a hook to be able to return all following child-nodes with my own function result. Is there a way to do this with the select field type? In the docs of this field I can't find an answer to this problem.June 24, 2021 at 4:32 PM in reply to: ✅Taxonomy Advanced: Set starting node of categories with query_args #29105ParticipantAfter changing the field_type to 'select' (and not 'select_advanced') it now works! No warning messages any more. But perhaps you could solve this problem for 'select_advanced'. Thanks!
June 24, 2021 at 4:21 PM in reply to: ✅Feature request: "radio_tree" or select_advanced with tree hierarchy #29103ParticipantEDIT: Ok, I found now a 'flatten' option for the normal select field, so this helped me a lot.
ParticipantAnd my too 😉
May 14, 2021 at 4:28 PM in reply to: ✅Fatal error after updating Meta Box because of extended class #28183ParticipantSorry to bringt this up again, but since today (?) the (class_exists('\MBAC\Post')) request doesn't work anymore.
I'm wondering if Meta Box changed something but I think this isn't the case, because extending '\MBAC\Post' works fine.Of course I could remove the (class_exists('\MBAC\Post')) request but I whish I can leave it for safty to prevent breaking the site if Admin columns isn't activated.
Does anybody know why this class_exists request doesn't work anymore?
Juergen
-
AuthorPosts