Custom Field Bug

  • Resolved eff16

    (@eff16)


    1 year ago

    Since the last update, one of my custom fields is not working anymore.

    I suppose this has something to do with special characters in the meta key of the field.

    Here is an example:
    My field name is ‘Ticketpreis (AK)‘ and the automatically generated meta key is ‘_ticketpreis_(ak)‘.
    When I enter a value into this field in the backend, save the event and reload the backend page, the value is gone.
    In addition to this, I cannot delete the field in the field editor.

    Until the latest update, all this was working.

    If special characters are no more supported in the meta keys, then these should not be generated automatically.

    Cheers!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter eff16

    (@eff16)

    After experimenting a bit more, the problem exists even for a newly created field with no special chararcters.
    I enter the value, save the event, reload the event and the field ist empty.

    Note: I am editing the event in the backend.

    Plugin Author Rita Kikani

    (@kikanirita)

    Hi @eff16,

    Sorry for the inconvenient and thank you for informing about the issue. I would like to inform you that this issue is resolved for our upcoming version, you can verify here : https://github.com/wpeventmanager/wp-event-manager/issues/1648. If you have urgency then you can use this version : https://github.com/wpeventmanager/wp-event-manager/tree/3_1_44, you just need to reset field-editor first then create same field with newer version, your issue would be resolve.

    If you have any further query then please continue in this thread.

    Thank you once again.

    Thread Starter eff16

    (@eff16)

    Thanks!

    Thread Starter eff16

    (@eff16)

    Hi,
    I just updated to the new version and the issue still remains. What can I do?

    Thread Starter eff16

    (@eff16)

    After reinstalling the plugin and reconfiguring all fields and settings (ugh!) it seems to be working.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Custom Field Bug’ is closed to new replies.