The menu acts as a jumpmenu (meaning that the createcontentblock form is automatically submitted with a JavaScript 'onSelect' or something) and really don't think the "Create Content" button should be shown. On a psychological level, the presence of the button tells the user that his or her menu selection isn't final until the button is clicked.

Comments

douggreen’s picture

douggreen commented

Hmm, good point, but... you can click the button without selecting one of the content types.

If you don't have OG enabled, it sends you to node/add. If you have OG enabled it sends you to a new page node/add-og which is very similar to node/add but replaces the OG enabled content types with the gids[]= values and gives the appends group titles.

Do you think that it's worth losing this behavior for the simpler UI? I think that you're right, and it is, but it's worth discussing.

Christefano-oldaccount’s picture

Christefano-oldaccount commented

How about adding a new menu item below "choose one" that goes to node/add? I have some mockups posted at http://drupal.org/node/189699

douggreen’s picture

douggreen commented

I can see adding a block setting, that gives the site admin control over whether the button displays or hides itself when Javascript is enabled, but I think a global default behavior that hides itself isn't going to work for all sites. Of course, you could do this with some theming or custom code, but the idea behind this module is to create an easy to use block, so it also needs to be easy for the administrator to use.

douggreen’s picture

douggreen commented
Category: bug » feature
GregoryHeller’s picture

GregoryHeller commented

It might make sense to give the admin the following option:
* selection of content type
* required (user must select content type from drop down menu)
* optional (if use does not select content type, user will be taken to node/add page)

douggreen’s picture

douggreen commented
Status: Active » Closed (won't fix)