To reproduce:
- use browser with JavaScript disabled.

Results:
- when reply on threated comment - blank page with code:
[{"command":"settings","settings":{"basePath":"\/","pathPrefix":"","ajaxPageState":{"theme":"bartik","theme_token":"_7YNg2d8BIhsNwifqsRVCycM.............................................

Comments

walker2238’s picture

walker2238 commented

Yeah that's the case with all pages that ajax comments uses. I'm not too sure but I think it might have to do with improper use of arguments... I remember I had the same results when making a module with Ctools and that was the cause.

James Andres’s picture

James Andres commented

FWIW, the root of the problem is that Ajax Comments forcibly changes the URLs for all comment links (ie: Edit, Reply, Delete). The URLs should be pointing to pages like /comment/123/edit and not /ajax_comments/edit/123.

This patch is a move in that direction #1924816: Ajax comments should be disabled on all comment pages, comment/%comment (patch). Needs more work to have full support for disabled JS.

walker2238’s picture

walker2238 commented
Title: JavaScript disabled - problem with threated comments » JavaScript disabled - problem with threaded comments
formatC'vt’s picture

formatC'vt commented
Issue summary: View changes
Status: Active » Closed (duplicate)

We need a no-javascript fallback.
#2108557: Support for no-javascript fallback