Forum Replies Created
-
AuthorPosts
-
Olivier
ParticipantThank you Peter, I have shared them via the contact form as indicated.. I appreciate you looking into it a lot
Olivier
ParticipantPeter, thank you for trying. I could but I don't have a staging website, that would be quite complicated. Do you have any idea what could cause this issue, so I could try to test them?
Olivier
ParticipantI have no idea where that 'old data' is stored as it keeps coming back. The only change (other than updating custom fields) I made to that page recently is to update the permalink, in case that's relevant
Olivier
ParticipantI also tried clearing the cache for that page, and cleared the cache of the field group. No change.
Olivier
ParticipantHere is the field group export, in case you were going to ask: https://pastebin.com/amnhGSv4
September 1, 2023 at 6:25 AM in reply to: ✅After Edit, Custom Field Group Only Applies to "Posts" #43114Olivier
ParticipantI had the exact same problem. I increased
max_input_varsand it solved it.Surprising because I didn't think I had reach the limit of '1000 inputs' already (by previous value). I have less than 100 custom fields on that page alone, so I don't know what counts as 'input'. But anyway, it's solved for me.
Olivier
ParticipantActually, I think the first line
{% set post_id = mb.get_post_id() %}is not necessary. It works without it.Olivier
ParticipantFor anyone reading this in the future, for reference here is a code that works for my use case (finally!).
{% set post_id = mb.get_post_id() %} {% set author_id = mb.get_the_author_meta( 'ID' ) %} {% set args = { post_type: 'licensee', relationship: { id: 'user-provider', from: author_id } } %} {% set posts = mb.get_posts( args ) %} {% for post in posts %} <a href="{{ post.url }}"> <div class="mb-container related-provider provider-related-to-user"> <div class="provider-logo"> {% set field = attribute( post, '_thumbnail_id' ) %} {% if field is defined %} {% for item in field %} <img src="{{ item.medium.url }}" alt="{{ item.medium.alt }}"> {% endfor %} {% endif %} </div> <div class="provider-name"> <span>{{ post.title }}</span> </div> </div> </a> {% endfor %}Nobody here could help me apparently, but ChatGPT helped me without hesitation. Working code, awesome!
Olivier
ParticipantIf I just enter a User ID like
7it works, but if I place the{{ author.ID }}variable it breaks the page. Does the{{ author.ID }}variable return anything else than the actual author user ID?Olivier
ParticipantOh, I rejoiced a bit too fast unfortunately. The View was set up for testing with the user ID "7", but of course I need a variable. I tried {{ author.ID }} but it still breaks the page...
Olivier
ParticipantAh gotcha - I got tricked by my own slug rewrite. Thank you Peter!!
Olivier
ParticipantThank you Peter, I just submitted a message with the login credentials
Olivier
ParticipantI understand - thank you Peter
Olivier
ParticipantPeter,
I think I understand - and I'm not expecting MetaBox to manage capabilities. But for example when creating a CPT with MetaBox, there is a
Capability typeoption, and one can choose either Post, Page, or Custom.By choosing Custom, I can then use another plugin to manage these capabilities for my user roles.
I would like the same flexibility for custom taxonomies and for Relationships. Basic capabilities such as read/edit/create would do the job. So my question is whether MetaBox can define the capabilities so that I can manage it with a third-party plugin.
Olivier
ParticipantThanks Peter. So if you say it's beyond the scope of Meta Box, am I correct in understanding that Meta Box natively registers no capability that can be used to control permissions, and that it otherwise offers no feature or hooks to be used in a multi role environment?
I see MB registers at least 3 capabilities
- create_metabox_field_groups
- delete_metabox_field_groups
- edit_metabox_field_groupsBut that's all - is that correct?
-
AuthorPosts