Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 21 total)
  • Author
    Posts
  • in reply to: r.replace is not a function error #47363
    alpha.mediaalpha.media
    Participant

    You 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.

    in reply to: Items in group field are out of order #35922
    alpha.mediaalpha.media
    Participant

    I 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.

    alpha.mediaalpha.media
    Participant

    Is 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.

    in reply to: Default block width #33629
    alpha.mediaalpha.media
    Participant

    Any update on when this could possibly roll out? I was hoping to have this feature soon.

    in reply to: Select Advanced Field Display Issues #33628
    alpha.mediaalpha.media
    Participant

    It 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.

    in reply to: Select Advanced Field Display Issues #33584
    alpha.mediaalpha.media
    Participant

    Here is an image for reference: https://ibb.co/wQjR1gC

    alpha.mediaalpha.media
    Participant

    Thanks. That seems to be the issue.

    alpha.mediaalpha.media
    Participant

    I 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

    in reply to: Way to re-use field groups? #31296
    alpha.mediaalpha.media
    Participant

    Thanks,

    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.

    in reply to: Date field, timestamp problem ? #19279
    alpha.mediaalpha.media
    Participant

    I 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.

    in reply to: Update error (v1.3.8) #18194
    alpha.mediaalpha.media
    Participant

    I 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.

    alpha.mediaalpha.media
    Participant

    Can this be fixed or is it just something we have to live with? Also, thank you for video!

    alpha.mediaalpha.media
    Participant

    I 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.

    in reply to: MB Rest API Fields POST Method #6463
    alpha.mediaalpha.media
    Participant

    Interesting. 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.

    in reply to: MB Rest API Fields POST Method #6452
    alpha.mediaalpha.media
    Participant

    To 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.

Viewing 15 posts - 1 through 15 (of 21 total)