Home Forums Plugin Support WP User Frontend Pro custom field problem fixed?

This topic is: resolved

Tagged: , ,

This topic contains 14 replies, has 3 voices, and was last updated by  Tareq Hasan 5 years, 10 months ago.

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #5588

    tppp
    Participant
    Post count: 12

    Hi there,

    I've tried out WP User Frontend and really like it, I'd like to upgrade to get extra features but….

    My one problem with the free version is that custom fields do not work, a “cf_” is prefixed to the Field Name and the data added to my form is not collected.

    Could I ask if this problem is resolved in the Pro version?

    #5589

    tppp
    Participant
    Post count: 12

    Also, apologies, but the custom fields I am attempting to populate are created within this theme: http://themeforest.net/item/viewr-visitorauthor-review-magazine-niche-theme/3375669

    I believe they are inside the standard wordpress table.

    #5590

    Mahi
    Member
    Post count: 1555

    You have to get the correct meta_key name. From my point of view WPUF Pro should work with this theme without any issue.

    #5591

    Tareq Hasan
    Keymaster
    Post count: 2831

    The meta key names in the free version is prefixed with “cf_”, but it doesn't with the PRO version. Means, you can use any meta key you want.

    #5593

    tppp
    Participant
    Post count: 12

    Thank you for such a quick reply. Mahi, am I to under that using name _prod_spec_officially is not the correct name for the field below?

    <label for="_prod_spec_officially">Officially</label>
    <input type="text" name="_prod_spec_officially" id="_prod_spec_officially" value="">
    

    On adding this to the custom posts it becomes

    cf__prod_spec_officially
    

    Tareq, if the cf_ is prefixed does that mean there is no way to use custom fields in the free version? The pro version looks great but I'm surprised custom fields was released if it didn't work?

    #5598

    Mahi
    Member
    Post count: 1555

    as Tareq mentioned with in Free version is has a prefixed value “cf_” so i am afraid that it will not works unless you change it manually.

    #5599

    Tareq Hasan
    Keymaster
    Post count: 2831

    If you used _prod_spec_officially in the free version, it would become cf__prod_spec_officially, but in the PRO version it'll be the original _prod_spec_officially. In the free version, you could use custom fields but prefixed!!

    The pro version looks great but Iโ€™m surprised custom fields was released if it didnโ€™t work?

    Do you mean it doesn't work in the PRO version?

    #5601

    tppp
    Participant
    Post count: 12

    Sorry, I meant I'm surprised custom fields was used in the free version if it didn't work.

    It shows great potential though, is there a trial version of pro to test things?

    #5605

    Tareq Hasan
    Keymaster
    Post count: 2831

    Yes, there is.

    #5607

    tppp
    Participant
    Post count: 12

    Ha, I meant with my data ๐Ÿ˜‰

    But no problem! The fact you replied so quickly to my questions has inspired me to buy, here's hoping Pro solves my issues ๐Ÿ˜‰

    #5609

    tppp
    Participant
    Post count: 12
    This reply has been marked as private.
    #5610

    Tareq Hasan
    Keymaster
    Post count: 2831

    Can you share login details so I could investigate?

    #5615

    tppp
    Participant
    Post count: 12
    This reply has been marked as private.
    #5626

    tppp
    Participant
    Post count: 12

    Turns out your plugin works flawlessly!

    I've found a number of errors in the theme I'm using though ๐Ÿ™

    #5635

    Tareq Hasan
    Keymaster
    Post count: 2831

    Sorry, I didn't have the time to check your site. But glad to know that it works great!

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

The topic ‘custom field problem fixed?’ is closed to new replies.