• First of all – really, really great plugin, that takes ACF on a another level.

    I absolutely like your “Post Field” feature although I don’t use it, but it is a great concept. I need a different thing, so I was wondering if you have plans to implement the same thing, but for users ? Call it “User field” if you want. The concrete problem I have is, that I’m working for a Dutch company and the Dutch naming scheme is quite … errrrm … complicated. It has Initials, First, Prefix 1, Last, Prefix 2, Last 2 names. As you’ve might imagine – it is somewhat of a nightmare to implement. So, having an option like “User filed” would allow simply extending the naming scheme instead of actually duplicating and synchronizing it. I think this would also allow great flexibility on adding secondary emails and other contact information etc etc … all-in-all – it would be a hit, I think.

    Another issue I have, although it can be somewhat workarounded, although not easily – some sort of integration between ACF and Woocommerce profile/registration, billing address and shipping address.

    Hope to hear from you and keep up the good work.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Konrad Chmielewski

    (@hwk-fr)

    Hello,

    Thanks for the feedback! I’m glad to hear that you enjoy ACF Extended ??

    Regarding your feature request, well, ACF already allows you to add any custom fields in User views. Adding a custom wrapper with builtin “new fields” would remove the flexibility and customization which are the core philosophy of ACF. I’m not sure how that would work for developers TBH.

    For the Woocommerce integration, this is planned for a future release, I’m very busy right now with the upcoming cool features, but this one will definitely comes!

    Have a nice day,

    Regards.

    Thread Starter joroabv

    (@joroabv)

    Hi,
    Thanks for your answer. Yes, ACF does allow great flexibility (and I do use it as much as possible), with just one major drawback – no way to mix system and custom fields in an existing system section. So I was thinking – since your “Post Field” offers exactly that for posts – why not have it for users too ?!
    As I described in my example with extending the user naming scheme – it could be of great help in some cases. To be honest, I’m somewhat new to WordPress and I was really wondering how everyone around the world lives with such a big shortcoming of the default system at all – I’m from Bulgaria and we have 3 segment names, working for Dutch company – 3 to 5 segment names, latino world – up to … idk … 16 names :-))) … I’m really wondering how everyone is handling this when WP have just first and last … even UK and US can have 3 segments ?
    So, if you think it can’t be useful – it’s fine, as after all you’re the one that decides priorities on your own product, just have in mind – it can be something for a lot of people. Other solutions are available, of course – like building full custom dahsboards and separate member systems, but in many cases it is an overkill.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘“User field”’ is closed to new replies.