cannot save Places CPT custom fields

This topic contains 7 replies, has 3 voices, and was last updated by  Kiran 5 years, 1 month ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: 

  • Author
    Posts
  • #469774

    Robert Ungemach
    Expired Member
    Post count: 11

    There are 2 fields that I cannot add to my listings for the Places CPT, they will not Save. Price Range I cannot get to Save at all. Fieldset (Section Separator) if added can only be saved once. If anything requires editing, it must be deleted and re-added. I found that the edit issue to be true for others as well. I haven’t tested them all since I don’t need many added.
    I am running the latest V2 versions. I’m in dev with very few other plugins.

    Cheers,

    Robert

    #469840

    Alex Rollin
    Moderator
    Post count: 27815

    Hello Robert,

    please try the tool at:

    GD -Status – Tools – Clear Version numbers
    1. Run the tool
    2. Close the custom fields page and reopen
    3. Try to adjust the field settings again
    Once you run that, check to see if the issue persists.

    If we should check on it, please write back with WP Admin credentials and the site login URL. Also tell us which field(s) we should check on specifically. We will check Price Range and Fieldset (Section Separator) to see if we can get those going, just let us know if there are others to check.

    Thanks

    #469877

    Robert Ungemach
    Expired Member
    Post count: 11
    This reply has been marked as private.
    #469891

    Alex Rollin
    Moderator
    Post count: 27815
    This reply has been marked as private.
    #469895

    Robert Ungemach
    Expired Member
    Post count: 11
    This reply has been marked as private.
    #469917

    Kiran
    Moderator
    Post count: 7069
    This reply has been marked as private.
    #470040

    Robert Ungemach
    Expired Member
    Post count: 11
    This reply has been marked as private.
    #470199

    Kiran
    Moderator
    Post count: 7069

    Hello Robert,

    The issue has been fixed. Some servers restricts “VARCHAR” as a value in POST request to prevent SQL attack.

    We have fixed it from our side.

    Let us know.

    Thanks,
    Kiran

Viewing 8 posts - 1 through 8 (of 8 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket