Assign special forms to tabs

I like the idea..

other forms, like contact page could be used as tabpage also, but I guess all these forms can be created easily within blocks (or nodes), and you can add the block (or node) as tabpage.

Postponing for now..

I think this feature can be achieved with the Form Block module. Please test it. You can write your results/problems into this issue..

Form Block indeed solves this issue. You can see a screenshot of this in action at http://groups.drupal.org/node/13162#comment-46310
The comment below it also describes how I automatically filled the nodereference field of the node/add form using the current page's nid.

This info should be a good tip for using QT..

QT doesn't respect the (?form?) block's permissions. I'v created a tab which is a node/add form (form block module). Anonymous users doesn't have permission to post these nodes but there is the node/add tab. It doesn't solve the problem if I configure the block permissions too.

I've tested this access control problem on other block types (independent from form block module) and the problem is still remains so I've posted a dedicated issue for it.

replied
#413226: block visibility problem

While this works in general, in ajax however field editors do not get applied correctly to fields.

Neither do node form columns:

http://drupal.org/project/nodeformcols

Is this part of that same settings issue from the other thread that's been plaguing me?

Thanks.

Can you post a screenshot of nodeformcols, I do not know which form you are trying the node form (1) or the nodeformcols admin form (2)..
as I see (1) uses nodeformcols.css file and (2) uses js and css files.
#345175: what could be inside ajax quicktabs:

you can put anything inside ajax QT unless it does not require additional javascript or css files

I do not know what you mean by "field editors", if you mean wysiwyg editors like fckeditor, then yes that does not work inside ajax quicktab as it require additional js and css files..

you need to load the required js and css files manually (and the correct functionality is still not guaranteed, as the form may use dynamic ajax settings) or you need to switch to non-ajax quicktab.