form_with reverting to HTML processing only about rails HOT 5 CLOSED

The naming conflict was the root problem, but not the one described above. A class attribute's name was the same of a class goverend by a has_many relationship (initially this had not been specified in the model). Once specified, the record was no longer creatable and the processing reverted to HTML.

from rails.

Are you sure that your controller action has a format.turbo_stream response?

If it is not found, it will try to respond with format.html instead.

P.S. data: { remote: true } has no effect in rails 7

from rails.

Definitive.
I run the controller •without• mentioning format, in order to default processing the rails way ...
If there is no view with the turbo_stream format, the 'html' file is then rendered.
In both cases, however, the logging will be
Processing by PartisController#create as TURBO_STREAM .
Something in this controller is forcing the processing to got to HTML...

from rails.

I belive rails determines the content type based on the Accept header. If it includes text/vnd.turbo-stream.html the request will be handled as a TURBO_STREAM.

You can check the request header using the browser or with logger.debug request.headers["Accept"] in the controller action.

from rails.

well the content type is being established as HTML
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
and not the default TURBO_STREAM.

I've tried many variants, trying unsucessfully to override... Now <%= form_with( url: create_consumers_partis_path, data: {turbo: true}) do |form| %> which renders in HTML <form data-turbo="true" ... but it still processes to HTML...

So something is diverting the normal process.

update I worked on the assumption of some naming conflict: there are multiple classes who are compounds (Parti, ConsumerParti, GroupParti), as well as compounded named actions ('create_consumers') which might be generating routing confusion, and thereby diverting the intended processing method. Having eliminated potential conflicts derived from action names, the behaviour remains stuck to HTML processing for any action that regards the Parti, ConsumerParti, GroupParti classes

from rails.