Hi,

I just found your module and it looks pretty good. I haven't finished tinkering with it yet, but I thought I'd ask before presuming it can't.

In the related content block, your type drop down pre-fills with all types, is there a way for an admin to select what types appear there?

What I want to accomplish:

  • Users can select a Node type from a drop-down or static box (even a duplicate taxonomy list would work)
  • On the same screen they can fill in the normal title field
  • On the same screen they can fill in the normal body field

After hitting submit or a link, they are taken to the selected node's content add form with the title/body pre-filled from the previous fields.

Thanks for any help/advice!

Comments

alan d.’s picture

alan d. commented

Is there a way for an admin to select what types appear there?

Yes. This will only show the content types that the user is allowed to create.

To refine this more, a hook_form_alter will be required to trim the list down.

Handling title and body fields

The title yes, which can prepopulate the menu title too depending on the settings.

The body, no. Three reasons why were:

These two fields make up the required fields on 80% of the content types that we use and making the user submit the "same form" fields twice would make the block a redundant step, so not including this was by design.

The body field has the format options attached, making this bulky in a block.

The submission of the block is converted into a GET request, and is limited in size. Normally not an issue, but when a large content segment is added here, it will be lost as the GET parameter length is trimmed after it exceeds the maximum allowed length. (16Kb from memory)

While I can not think of the modules off the top of my head, there are some that allow you to embed a create content form in a block, or if you can do some PHP programming, a custom block and Prepopulate module may also match your needs.

alan d.’s picture

alan d. commented
Status: Active » Closed (fixed)
Ariesto’s picture

Ariesto commented

I was already leaning towards an embedded block with the prepopulate module, so I'll investigate those further. Thanks for your detailed response!