WP User Frontend multiple forms

WP User Frontend multiple forms!

WP User Frontend is a wordpress plugin developed by tareq1988. And you are here because you are interested in WP User Frontend multiple forms which is currently not supported by the latest version of  WP User Frontend at this time of writing.

Reading the description about WP User Frontend on this link, wp-user-frontend. It really looks promising and I love it.

Gives ability to the user to create new post, edit post, edit profile from site frontend. So users doesn’t need to enter the admin panel. Everything they need to do can be done from the frontend.

Features:

So here is my plugin that solves your problem. This features of this plugin are follows:

  • User can create a new post and edit from frontend
  • They can view their page in the custom dashboard
  • Users can edit their profile
  • Administrator can restrict any user level to access the wordpress backend (/wp-admin)
  • New posts status, submitted by users are configurable via admin panel. i.e. Published, Draft, Pending
  • Admin can configure to receive notification mail when the users creates a new post.
  • Configurable options if the user can edit or delete their posts.
  • Users can upload attachments from the frontend
  • Post featured image can be set
  • Admins can manage their users from frontend
  • Pay per post or subscription on posting is possible

 

But as many others has been asking, why can’t it support multiple forms? Might be great if it has this kind of feature. WP User Frontend multiple forms would be great. Well, who doesn’t want multiple forms?

 

And so, I’ve tried to edit it and here’s the result.

 

At first, this was for my personal use. But seeing a lot who has the same problem, I’ve decided to share it. The edited plugin can be downloaded below.

Credits still goes to the original plugin author.

Before using it, be sure to back up everything first… Just in-case..

Feel free to comment below if you found any problem.

 

Note: Currently, the ability for WPUF to add custom fields using functions.php is disabled. I’ll put it back at the time I solve the problem behind it.

29 Responses so far.

  1. JAsko says:

    Hy,

    thanks for sharing this plugin with us, and this addon of yours. It’s amazing :)

    I my have one question, is it possible to make form with your addon, that can add an event post type to the current event type within the front end ?

    Sorry, I’ll try to explain better, well here what I want to do. I have a page Events, where it displays all the events that I put in, so I want to add an another page, something like, “Add event” and in that page I would like to put this shortcode for exactly that post type.

    When I add this:

    [wpuf_addpost post_type="event"]

    it adds just the same post type like this one

    [wpuf_addpost]

    I would like, that my users can add a date, and some description on it, and that’s it, I don’ want them to add attachments, or anything else in it. So, when I switch to the main calendar page, it should display it within the calendar itself.
    I hope you will understand what I meant :D sorry for my bad english, or my bad example. I really hope that you will help me out with this.

    Thanks in advance.

    Warmest Regards

    • Reigel Gallarde says:

      @JAsko, I’ve checked this version and tested with [wpuf_addpost form_id="10" post_type="portfolio"]. The post went in my post type portfolio. Or I didn’t understand your problem?

  2. Kelvin says:

    I got this error:
    Warning: Invalid argument supplied for foreach() in /home/uleven/public_html/wp-content/plugins/wp-user-frontend/admin/custom-fields.php on line 330

    How to solve this? Thanks. I’m using wordpress 3.4

    • Reigel Gallarde says:

      Can you explain what you were trying to do first? I’m not sure how you got that error…

      • Kelvin says:

        I used to install original version of wp user frontend from wordpress plugin installer itself.
        After i found your extended version, i deactivate the original version and re-install with your extended version.
        Then under the custom filed tab, there is error of Warning: Invalid argument supplied for foreach() in /home/uleven/public_html/wp-content/plugins/wp-user-frontend/admin/custom-fields.php on line 330 appear.
        I haven’t do any configuration and filling yet, the error appear right after the plugin activated.

      • Kelvin says:

        Is that possible there are some crash with other plugin? Thanks.

      • Reigel Gallarde says:

        the closest thing I could think of is there’s something wrong with your prefix… can you look for custom prefix in wpuf settings… I’m not sure what tab cause I’m not on my pc right now… can you check the default custom prefix, should be “cf_” without the quotes.. and that is if you didn’t change that from the original wpuf.

      • Kelvin says:

        Hooley. You are great pal. Problem solved. Thanks for your help and you did good job for this extension. Billion thanks.

  3. Amanda says:

    This is wonderful if it would work. I keep getting the same message;

    Warning: Invalid argument supplied for foreach() in /home/content/95/10176095/html/wp-content/plugins/wp-user-frontend/admin/custom-fields.php on line 330

    Do you have a solution? The prefix I tried was cf_list and cf_list_. I then receive error above and “Something went wrong”.

    • Reigel Gallarde says:

      that error would just mean you have an empty “form”. Make sure cf_list and cf_list_ has field(s) in it.

      • Amanda says:

        Ok. Perhaps, I’m missing a step. This is what I did:

        1) downloaded file to Plugins; it updated original i had
        2) In Dashboard, I clicked on “WP User Frontend”, then “Custom Fields”
        3) I go to “Add Form” first as I can’t add a field to a form that has’t been created yet.
        4) I get the error message.

        Please let me know where I went wrong when you can. HAPPY NEW YEAR!

      • Reigel Gallarde says:

        You have added a “form”, are you by chance forgot to include form_id in the shortcode? -something like, [wpuf_addpost form_id="10" post_type="portfolio"].

      • Amanda says:

        I re-installed. It seems to be ok now! Thanks for replying so fast.

  4. glen says:

    Hi cool plugin…

  5. George says:

    Hey, could you share how you did this? I might like to alter the code outside of the core plugin so it can be updated and doesn’t prevent use of custom fields.

    • Reigel Gallarde says:

      just do a search folder of the original plugin. Search for ‘cf_’. The thing is, every custom field has this prefix. You have to find a way to make this prefix not fixed. What I did was changed that to a variable. Then when a form is added a prefix is saved for that particular form. Now, every time a shortcode is called, the plugin will check what form it is. If the shortcode has no parameter form_id, it will use the default ‘cf_’.

      How hope I’ve explained something :D
      I’m not so good on explaining…
      Anyway, I was just waiting for their final/official release of a new version, then I will fork this idea to the original.

  6. Eugene says:

    Hey. A great addition to the plugin.
    Can you suggest how to make one form to post an entry in only one category, and the other to another?

    • Reigel Gallarde says:

      I think this one is not available on the plugin yet. I was thinking of implementing it, but I’ve read somewhere that the plugin already has this capability but is commented out in the source code. I have not touch that one yet though. And will not for this time being cause I’m a little busy with some projects.

      • Eugene says:

        I solved this by hidden category listings.
        The problem is quite important: you have added many forms, but they apply only to the addition, if the user wants to change the record – he is issued the default form.

  7. Rob says:

    I keep getting “Please use another prefix. Prefix already present in”
    when I add a new form.

    I have put “cf_”, “mf_”, “mf3_”… etc

    I don’t know what I should put for prefix.

    I put the default form this.
    Prefix used in custom fields : cf_friends

    I have to find prefix name or it should unique names?

    • Reigel Gallarde says:

      you can use any prefix… I’ve put that field so that users of the plugin will know that the custom post fields uses prefix… prefixes are needed in this plugin… you can use ‘abc_’, ‘def_’, or ‘house_’. Just about anything… you can even use garbage like text. As long as it’s unique in relation to your other forms.

  8. George says:

    Hey Reigel,
    Check this out…

    https://mega.co.nz/#!B0Z2kQrI!GxMz1TiLVpXTNmWGdFQAbR6M4OFBrePuvJ8JJwiVJOE

    It’s not complete by any means but it’s a start. I created a separate forms.php file and added your code (slighly modded) to it to separate the forms menu from the custom fields menu. I modified settings.php a bit to add the submenu.
    I added a field to indicate the post type but it’s just a field, it doesn’t do anything right now.

    So if, anything, I think that the foundation for the forms page and interface are solid, although it will eventually need to integrate the form builder so that forms can be made with different fields. For the most part though, now it’s a matter of functionality. I know Tareq has a pretty strong idea of how the forms should be saved. He suggests saving the forms as a custom post type, which is fine, that might be better but I admit, I am still learning and I’m not sure what the best method would be. However we end up doing it though, it is essential that forms allow you to submit different post types.

    Also, something would need to be done to the dashboard to reflect all post types but right now, I just use 2 short codes with the post type indicated so users see 2 dashboards on the dashboard page (1 for each type).

  9. George Spake says:

    Added fork on github with a lot of this code. added to separate forms.php and moved to a ‘Forms’ submenu so it doesn’t interfere with the existing custom fields functionality. per Tareq’s suggestions, forms will be saved as a post with a custom post type ‘wpuf_form’ and settings will be saved as an array in a custom field associated with the post. Any input or contributions would be greatly appreciated. Here is the link… https://github.com/gpspake/WP-User-Frontend

    • Reigel Gallarde says:

      I hate to say this, but I don’t know how to use github! :D I will look into it… thank you for reminding me… ;)

    • Reigel Gallarde says:

      I’m not sure if it’s a good idea to make form as custom post type.. what if I have a custom post type for example students… then different form for college, high school, pre-school, etc… That would be a problem I think.

      What I’m thinking is to still add the form as a variable. Like what it is now. But of course, making it to a separate file is the best. This version of mine is not yet the best. Recently, I found out that edits doesn’t work as expected. But I already have a fixed. Not yet complete though as to I’m currently busy.

      But hey! I like this plugin, let me know how I can help. cheers!

  10. Vitaly says:

    Hello! Sorry for my english, I’m from Russia! To write a comment I use “google translator.” :) I really need to use your pladin. But I can not add a custom field! :( I create a custom field, insert a short code [wpuf_addpost form_id = "10" post_type = "event"] me in the right page. But in the end it does not work! And on the page I get the form, the same as if I put a short code [wpuf_addpost]. HELP ME PLEASE!

    • Reigel Gallarde says:

      Hi, I’ve seen your swf video. I have not used this plugin for a while now.
      I have tested it and found out that there’s a error in codes using 3.5.1 version of wordpress.
      I can’t test it now because of this error. Also, the original plugin already has multiple form support. You can try that one. Here’s the link, http://wedevs.com/plugin/wp-user-frontend-pro

      • Vitaly says:

        Oh, it is very sad that you are no longer working on this plugin! :( I was hoping that I could use it! WP User Frontend is good, but it’s paid! Thank you very much, that did not disregard my cry for help! :) Do you think there is any other way to do what your doing a great plug-in?

Leave a Reply