Support

Account

Home Forums Backend Issues (wp-admin) Unable to delete Fields, seem to be cached?!

Solving

Unable to delete Fields, seem to be cached?!

    • Kevin

    • November 25, 2013 at 9:16 pm

    Hey Elliot,

    it seems that I have a similar problem like here (http://support.advancedcustomfields.com/forums/topic/unable-to-change-fields-once-ive-created-them/ adding links doesn’t work because it closes the tab?!). But when I delete the field it seems that it’s kind of cached. But we have no cache plugins or anything like that running. Tried it in our dev and production environment also with the latest version (4.3.1) but nothing changed.

    Please let me know, if you need any further informations.

    Thanks in advance.

    Best,
    Kevin

    • Elliot

    • November 26, 2013 at 10:41 am

    Hi @keeev

    Thanks for the bug report. Can you please elaborate more on the issue? I don’t understand what you mean by: “adding links doesn’t work because it closes the tab?”

    Perhaps start at the start and provide a clearer description of the issue with steps to reproduce the issue?

    Thanks
    E

    • Kevin

    • November 26, 2013 at 7:35 pm

    Hey again.

    Aaaahm, the issue with “adding links doesn’t work because it closes the tab” happens here in that WYSIWG-Editor on support.advancedcustomfields.com. That had nothing to do with the actual bug.

    The link was just a reference to the actual problem but it’s not exactly like that in our System. I just can’t delete a field which has been set earlier. Neither through the plugin itself nor the “native” custom fields of WordPress. It seems like it’s kinda cached and after I Update the Settings it still appears in the “native” custom fields of WordPress.

    We built our own slider with ACF (where you set the images) and they should only appear where you actually set them (e.g. Pages->Home/Index (created as a normal WordPress Page). And if I want to delete it in Pages->Subpage it’s still there even if I delete the fields.

    Hope it’s a little bit clearer now. 🙂

    • Elliot

    • November 27, 2013 at 3:58 pm

    Hi @kevin

    What do you mean by ‘delete fields’? Are you talking about editing a field group and deleting the field there?

    Another question, are you hosting on WP Engine? There are many reports of that server caching data and conflicting with ACF

    Thanks
    E

    • Kevin

    • November 27, 2013 at 5:46 pm
    This reply has been marked as private.
    • Elliot

    • November 28, 2013 at 9:55 am

    Hi @kevin

    I’m sorry, but I really don’t understand your issue. Please refrain from language like:

    “I empty or clear the fields where their given input shouldn’t appear.”

    And use clear language like:

    “When editing a post, I highlight a select field value and delete it. Upon save, the value is not updated and I see the original value”

    Can you please re-explain the issue?

    Thanks
    E

    • Kevin

    • November 28, 2013 at 5:50 pm

    Hey!

    Sorry but I’m no native speaker so it’s sometimes a bit weird to describe technical problems as it would be in German.

    Because of the settings in the field group it’s only possible to see this field group on the “Options Page” (because of ACF Options Page Plugin). But it also visible on a real Page (with content and stuff like that). And like you said: “Upon and after save, the value is not updated and I see the original value”, in other words: this field shouldn’t be there – and shouldn’t be set and because of that a “slider”(which we built with ACF) appears where it shouldn’t be.

    • Elliot

    • November 29, 2013 at 9:40 am

    Hi @kevin

    Perhaps the issue is that ACF does not ‘DELETE’ and custom field data which is not posted.

    If you have saved a custom field value in the past for ‘slider’ and want to delete it, you will need to save an empty value for this field.

    For instance, display the ‘slider’ field and delete all content from it and then update the post.

    I think I now understand what you previously described with the conditional logic. Because the ‘slider’ field is hidden, it is not posted, therefor, the DB value is not updated / changed.

    Either show the field and save an empty value, or edit the DB and remove the value.

    Does that help?

    Thanks
    E

    • Kevin

    • December 9, 2013 at 6:53 pm

    Hey Elliot,

    seems logical but it didn’t work. When I try to save it without a value it says „Please provide a custom field value.“ or when i delete the field, save the post without that custom field it still appears. Same happens when I delete it in the DB. :/

    Best
    Kevin

    • Elliot

    • December 10, 2013 at 3:34 pm

    Hi @kevin

    It sounds like the field in question is ‘required’. This is a setting on the field which means that a value is required to save the post.

    Is this possible?

    • Kevin

    • December 10, 2013 at 5:43 pm

    Hey Elliot,

    nope it’s not required regarding the Options page.
    Sorry for still bugging you with that.
    Maybe I should dig deeper in the DB, do you have any idea where to start?

    • Elliot

    • December 11, 2013 at 10:13 am

    Hi @kevin

    Can you please elaborate on what you meant by:
    “Please provide a custom field value”

    Perhaps a screenshot will help?

    THanks
    E

    • Kevin

    • December 11, 2013 at 6:39 pm

    Sure, that was my first idea yesterday.
    Here they are:

    • Elliot

    • December 12, 2013 at 12:31 pm

    Hi @kevin

    Your screenshots don’t show much of your admin screen, only the specific elements you have already described.

    I have a feeling that the custom field interface you are using is not actually ACF. Can you please attach a screenshot of the complete admin page?

    Thanks
    E

    • Kevin

    • December 12, 2013 at 7:01 pm
    This reply has been marked as private.
    • Elliot

    • December 13, 2013 at 10:03 am

    Hi @kevin

    Thanks for the screenshot.
    Is this issue regarding all fields?
    Can you update any fields at all?
    Are you modifying the ACF field value, or the WP custom fields value?

    Perhaps to clear up all question I have, you could take a short screencast of the issue to clearly demonstrate the issue.

    Also, I you wish, please feel free to post login details and I can have a look myself.

    Thanks
    E

    • Kevin

    • December 18, 2013 at 5:57 pm

    Hey Elliot,

    I’ll answer your questions asap, hope that I will make it this week, working on a different project these days.

    Best
    Kevin

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

You must be logged in to reply to this topic.

We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.