WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [Plugin: Custom Field Template] Definite bug: values from keys removed (12 posts)

  1. proximity2008
    Member
    Posted 4 years ago #

    This could be related from this post

    Consider this template:

    [page_title]
    type = textfield
    size=35
    label = Title of the page
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description
    
    [event_date]
    type=text
    date = true
    dateFormat = dd/mm/yyyy
    label = New Event Date
    class=event-date
    
    [event_title]
    hideKey=true
    type = textfield
    size=35
    class=event-title
    label=Event Title
    
    [event_desc]
    hideKey=true
    type = textarea
    cols=63
    rows =2
    class=event-desc
    label = Event Description

    Step 1. Populate some the fields with data. I used consecutive dates with consecutive titles and descriptions and publish.

    Step 2.
    Everything is fine.

    Step 3.
    However edit some of event titles and dates and publish.

    Result:
    Some fields will be wiped out. Checking the values in the normal custom fields confirms the data is lost.

    Settings:

    Use wpautop function = true
    Disable the save button = true
    Disable the quick edit = true
    Replace the box title = true

    http://wordpress.org/extend/plugins/custom-field-template/

  2. proximity2008
    Member
    Posted 4 years ago #

    bump.

  3. Hiroaki Miyashita
    Member
    Posted 4 years ago #

    I confirmed the bug you mentioned above. I will try to fix it in the next release. Let me have some time.

  4. endolil
    Member
    Posted 3 years ago #

    I found a bug as well - I am not sure if this is the same.
    When I am switching between two templates within the edit screen a of page and save new values in one template, values in another template (that is valid for the same page) are lost.

    At this time it seems to be impossible to use two different templates for pages that store values and allow to change the values in each of templates. It looks like there is only one template at a time storing values in the customf fields and changing one template causes the deletion of the values in another template.

    It's a shame!

  5. endolil
    Member
    Posted 3 years ago #

    I just realized that even only switching between the templates is causing the complete deletion of all values in the template that I am switching from.

    Hiroaki Miyashita, do you have any idea how to fix this?

  6. Hiroaki Miyashita
    Member
    Posted 3 years ago #

    You need to click save button on the right upper corner before switching the templates. Or if you check Use the auto save in switching templates on the Global Settings of the custom field template plugin, you do not need to click save button each time.

  7. endolil
    Member
    Posted 3 years ago #

    Thank you for your response.

    I can definitely say that it does not work for me.
    Neither the save button nor the autosave function.

    When for example I enter a value in an input field and save the document than it will save the value as expected. After saving the document - what means a reload of the page as well - I switch the template and after switching back the input field is empty where there was a value before. The save function does not help here either.
    Anyway it should not delete the value when switching the template, right? The value is actually a permanent thing after saving the document. For what ever reason the switching of templates causes the deletion of values - in my case.

    Any ideas?

  8. wottenad
    Member
    Posted 3 years ago #

    I'm having the same issue, though it seems to be related to Quick Edit only.
    If I add the values on the normal edit screen then update, the values are saved and are retrieved when doing subsequent edits (though in the very clunky custom field boxes below the main post).
    If I add values in Quick Edit then update, the values are saved, but when going back into Quick Edit to do subsequent edits, none of the values are retrieved and ALL values have to be filled back in to have ANY of them saved.
    I've used this plugin very successfully for a year without any problems, and only started seeing the issue when I upgraded to WordPress 3.0 (which is currently 3.0.1) I'm using Version 1.7.8 of CFT and have not changed the format of the template nor changed the permissions on the database.

  9. cosmictap
    Member
    Posted 3 years ago #

    I am experiencing this as well - following proximity's steps I get the value of several keys wiped out. Any fix on the horizon?

  10. BrenFM
    Member
    Posted 3 years ago #

    Yeah I've noticed some odd behaviours too. In one of my templates if I put too much content into a textarea with tinyMCE = true then the switching between templates plain old doesn't work.

    Also I've just spotted that if I use a fieldset_open and fieldset_close to group data together, any form elements with the multiple=true and multipleButton=true don't function correctly, i.e. I only get the option to enter ONE value. (noticed this with type=file and type=select at least).

    I can work around both of these but just thought I'd point them out.

    I DO have to admit that my cutsom fields are poorly named (mainly in the interests of keeping them human readable for our client) and have spaces all through them ([Header Images] instead of [HeaderImages]). Not sure if this relevant or not though!

  11. fldtrace
    Member
    Posted 3 years ago #

    Having same problem, however I found a work around, thanks to @BrenFM pointing out that spacing might create issues. And it does! So no space guys and add labels for the clients to make it readable. Works well.

  12. BrenFM
    Member
    Posted 3 years ago #

    Nope... still having issues with this - I've put up a new thread (probably frowned upon by the community - sorry!) as this has been marked as resolved, and my issue is slightly different to above.

Topic Closed

This topic has been closed to new replies.

About this Topic