Forum Replies Created
-
AuthorPosts
-
alpha.media
ParticipantYou can disregard this as I fixed what the issue was being caused from. It was an issue in my render template and not setting a fallback empty array when no posts have been selected yet in the group field.
I don't know why in the past it worked, but possibly before it returned an empty array on initial page load or something but by adding a fallback to an empty array the errors all went away.
alpha.media
ParticipantI figured out the issue. It was on my end. I was grabbing all the post IDs and using the post__in query argument and realized that doesn't order them by the post ID order.
March 11, 2022 at 12:51 AM in reply to: ✅Problem with conditional logic used in a clonable group field #34461alpha.media
ParticipantIs there no way to re-attach whatever javascript listeners there are whenever a new clone group is created? I would think there is a codeable solution to this.
I could have sworn this feature used to work before as I have received bug reports from clients with cloned fields no longer working with conditional fields.
alpha.media
ParticipantAny update on when this could possibly roll out? I was hoping to have this feature soon.
alpha.media
ParticipantIt looks like it's a conflict between plugins using different versions of Select2 library. I have found this post https://github.com/Yoast/wordpress-seo/issues/17681 and it looks like Yoast SEO made an update and it's caused conflicts with people and their meta fields. Unfortunately, Yoast SEO is such a widely used plugin, I don't know if they are going to fix it or ask other plugin developers to update their Select 2 libraries to be compatible. It appears the library version they are using is placing the x is an absolute position from the CSS so it then overlays the text in the select bubble.
alpha.media
ParticipantHere is an image for reference: https://ibb.co/wQjR1gC
December 16, 2021 at 1:48 PM in reply to: ✅Conflict using multiple taxonomy advanced fields in same block #32677alpha.media
ParticipantThanks. That seems to be the issue.
December 14, 2021 at 12:42 AM in reply to: ✅Conflict using multiple taxonomy advanced fields in same block #32578alpha.media
ParticipantI am still running into this issue and have an update. It appears the field data is saving correctly to the database but when I go back to the "edit page" the select fields show empty and not the saved value. I hope you can help further troubleshoot this. I have added a few more taxonomy advanced with select advanced fields to the options and the same issue is appearing.
The strange thing is it happens intermittently at times and then for some reason the field will show. This field is within a group type option.
I have attached a screen recording so you can see the issue as it happens.
https://drive.google.com/file/d/1MajZJSaNYl-yC43twpfWKdGcrlnaO-go/view?usp=sharing
alpha.media
ParticipantThanks,
I assume that means though I can't assign it to multiple places on the same settings page?
For instance, our settings page is to choose modules to be in specific places on the homepage and those modules are the same settings that are re-usable in the specific places they can go. It looks like I can't do that currently.
alpha.media
ParticipantI am also seeing a problem after updating Metabox and Metabox Group in the past few days. It's been a while since this feature has been coded so i'm not quite sure the problem but something is up with the latest release and the datetime field saving.
alpha.media
ParticipantI can confirm the same issue. When going to update the plugin using the auto update in WordPress, it still keeps showing the plugin has an update.
July 18, 2019 at 2:13 AM in reply to: Metabox switch not saving when in Metabox grouping on MB settings page #15389alpha.media
ParticipantCan this be fixed or is it just something we have to live with? Also, thank you for video!
July 16, 2019 at 9:12 PM in reply to: Metabox switch not saving when in Metabox grouping on MB settings page #15369alpha.media
ParticipantI can't really post a video, but it is the switch type field. First, it's an MB settings page and to reproduce the error I:
- Add a new group ( i.e. add clone )
- Set the toggle switch type field to true
- Save settings
After the page has saved and refreshed, it does not show the setting saved. I then set the toggle switch type field to true, save, and it saves correctly. I am trying to understand why it does not save the first time.
alpha.media
ParticipantInteresting. The strange thing is this was all working previously and when I went to retest it wasn't working. Keep in mind the Meta Box fields that don't begin with an underscores are working properly. Only protected meta with an underscores that is setup as MB fields won't update but any of the others will just fine. I'll have to take a look and see if there is something else within WordPress that could have updated to cause this.
alpha.media
ParticipantTo clarify, the meta fields are showing properly when using a GET request to the endpoint, they just don't seem to update with an underscores. This was working a few months ago and i'm not sure what happened but it stopped working.
-
AuthorPosts