Front End Form For Users to Add Content

By jhoffmcd on 19 Apr 2014 at 00:06 UTC

I'm using ECK to create a new entity type with about 4 bundles (with fields). I want users to be able to get to a page where they can now add content based on these new bundles:

Entity Type: Callboard
- Bundle 1: Hiring Attempts
- Bundle 2: Member Docs
- Bundle 3: Studio Exclusions
- Bundle 4: Shooting Locations

The path's would look like this:

hiring-attempts/add
member-docs/add
studio-exclusions/add
shooting-locations/add

How can I expose the fields of these bundles to a front end page where my users can get access to them? I understand that they need to have permissions, that part is no problem. I just need to know how to set the paths for these things.

Comments

Why not simply use four

nevets commented 19 April 2014 at 00:18

Why not simply use four content types?

Content Types

haqinai commented 19 April 2014 at 02:49

Adding content types give you the freedom to have them tooled to the types of forms that you want them to fill out. This can also have distinct taxonomy that you could organize in parent and child directories. Whit these two you may find that you will be able to achieve the desired results.

Cheers,

I tried this out, it works

jhoffmcd commented 20 April 2014 at 21:27

I tried this out, it works nicely because I can just use the path node/add/hiring-attempts for example and that works, but what if I don't want the Title field that is required?

You can use the Automatic

nevets commented 20 April 2014 at 23:45

You can use the Automatic Entity Label module to hide the title field on data entry/edit.

Limit Module Usage

jhoffmcd commented 21 April 2014 at 16:41

I'm trying to limit module usage. Ideally I don't want to stretch the functionality of something that isn't really purposed for what I need, and I don't want any extra data going into the database that isn't necessary if possible. That said, I can see that using this method with the module you recommended will achieve what I am looking to accomplish. I'll try it in the next round of test I do on this.

=-=

VM commented 21 April 2014 at 18:22

to remove the title - https://drupal.org/project/title is another option.

I'm trying to limit module usage.

In this case if you didn't use an already existing module you would have to write your own module as D7 core does not provide a way to remove the default title field. In part, I'd guess because the default content lists in the admin ui are listed by title. If there is no title field the content lists would be problematic.