• Resolved scottl100

    (@scottl100)


    I created a custom post type (“playlists”) with PODS that has some fields. These fields usually show up on the WordPress backend when viewing a “playlist” under both the “More Fields” and “Custom Fields” sections. Up until today this is the way it has worked. One of the fields is an HTML field, and so I have had to enter the HTML content into that field under the “Custom Fields” section in the backend.

    Now when I create a new playlist, none of the custom fields that I created in PODS are showing up under the “Custom Fields” section. I am not sure what changed. I have performed regular plugin and theme updates over time. I use the Divi theme, with a child theme. Any ideas how to get my fields to show up on the backend? Alternatively, any idea how to enter HTML content into a HTML field when it is under the “More Fields” section in the backend? Currently, my HTML fields do not have a text box next to them under the “More Fields” section.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Jory Hogeveen

    (@keraweb)

    Hi @scottl100

    I think you might be referring to the default WordPress metabox for custom fields?

    If so, could it be that this is simply hidden from your interface?
    https://www.ads-software.com/documentation/article/assign-custom-fields/

    Please note that this metabox can cause issues with plugins that work with metadata.

    Cheers, Jory

    Thread Starter scottl100

    (@scottl100)

    Thanks so much for your feedback. I do have the default metabox for custom fields shown on the page. I have checked to display the metabox from the screen options.

    I have been using my custom post type and fields successfully on my website for some time now, and only recently I noticed that the custom fields stopped displaying on the backend.

    The below image shows how a working “Playlist” backend post should look. This is one of my previous posts. Notice that the four custom fields I created in Pods (Playlist Duration, Playback crossfade, Spotify Link, and Spotify Embed Code) are all shown under both the “More Fields” AND “Custom Fields” sections. *Some parts of the image are intentionally blurred.

    Previous Playlist post that is working properly (shows all custom fields in the “More Fields” and “Custom Fields” sections.

    When I want to make a new post for my custom post type (Playlists) I generally duplicate a previous post, and replace the info. But now when I duplicate a previous post the only custom field that is not showing up is one that holds html content. The “Spotify Embed Code” custom field does have a text field next to it in “More Fields” , and is not showing up at all under “Custom Fields”. I also also unable add it there.

    The backend for after duplicating an existing post. The “Spotify Embed Code” filed does not appear under “Custom Fields”.

    Further, when I create a new post for my Playlist post type (rather than duplicating an old post), none of the custom fields show up under “Custom Fields”. I can still use the text boxes next to the fields in the “More Fields” section, but as you can see I cannot enter anything for my html content field (Spotify Embed Code) as it has no text box next to it. It is strange that none of the fields appear under the “Custom Fields” section.

    When I create a new post for a Playlist, none of the custom fields appear in the “Custom Fields” section.

    I have tried switching to different themes, and disabling all plugins (except for Pods), but the behavior persists. Since the custom fields still display under the “Custom Fields” section on old posts and some of them appear in that section when I duplicate a post — but none appear under that section when I create a new post, I am wondering if there is some sort of new error happening. Any ideas?

    Thread Starter scottl100

    (@scottl100)

    A little more info. I use the Divi theme with a custom child theme.

    Plugin Author Jory Hogeveen

    (@keraweb)

    Could you try to clear the Pods cache (Pods > Settings)?

    And did you check the browser console for Javascript issues?

    Regarding the custom fields box:

    Further, when I create a new post for my Playlist post type (rather than duplicating an old post), none of the custom fields show up under “Custom Fields”. I can still use the text boxes next to the fields in the “More Fields” section, but as you can see I cannot enter anything for my html content field (Spotify Embed Code) as it has no text box next to it. It is strange that none of the fields appear under the “Custom Fields” section.

    This is actually expected. At the time of creation that particular post doesn’t have custom fields yet, only after Pods adds them will they show.

    Note that I do not recommend the Custom Fields box. It can cause issues with field overrides as I mentioned.

    Cheers, Jory

    Thread Starter scottl100

    (@scottl100)

    Hi, Jory.

    I cleared the Pods cache, and created a new “Playlist”, but it did not resolve the issue. I also tried checking whether the Pod needed to be repaired (it didn’t) and recreating any missing tables (of which there were none). I saw a javascript error from the plugin Jetpack, but the same error was present on the backend page for another “Playlist” that was working properly. I don’t think a javascript error is stopping the Pod elements from loading.

    As I described above as well, the Pods fields for a Playlist are showing up next to “More Fields” (but not in the “Custom Fields” section they normally also appear in). However, one of my fields is an HTML content field (called “embed code”), and there is no text box on the backend next to that field where I can enter any HTML. Previously, I had been inserting the HTML for “embed code” in the “Custom Fields” section, but I can’t do that anymore since none of the Pods fields are displaying in the “Custom Fields” section anymore.

    Plugin Author Jory Hogeveen

    (@keraweb)

    As I described above as well, the Pods fields for a Playlist are showing up next to “More Fields” (but not in the “Custom Fields” section they normally also appear in).

    This is expected, see my comment on this in my previous message.

    However, one of my fields is an HTML content field (called “embed code”), and there is no text box on the backend next to that field where I can enter any HTML.

    This is the strange part. It seems the fields aren’t rendering properly.
    Since all our fields are JavaScript based (React) I would think this is a Javascript issue.

    Can you reproduce this on:
    1. Another CPT?
    2. A clean installation of WordPress with only Pods active?

    Cheers, Jory

    Plugin Author Jory Hogeveen

    (@keraweb)

    Hi @scottl100

    We havent heard from you anymore so I’m closing this topic.
    Feel free to reopen if you still need help!

    Cheers, Jory

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Pods Custom Fields Not Displaying on Backend’ is closed to new replies.