Problem/Motivation

Hello,

it is not possible to comment on a node. I can ckick "Add comment" and get the comment form. But if I wanna save or preview the comment I get an 404 error. The system log shows that error: "/comment/reply/node/248/null". The interesting thing ist the null at the end.
Well, if it's not possible to comment the theme ist not usable for me. This problem occurs only with AT. I can switch to any other theme and commenting works as it should.
I'm working with D9.3.2 and PHP 8.0.

Hopefully this works soon because I really like that theme and want to use it on my production site by the end of this month.

Kind regards,
Reiner

Issue fork at_theme-3257635

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

    Comments

    RFMP created an issue. See original summary.

    mattbloomfield’s picture

    Hi,

    What's the full output of the watchdog log? Also, just to be sure, where are you hosting your site and are you using git or SFTP?

    rfmp’s picture

    Hello Matt,

    this is the full output. Nevertheless I send you a screenshot. I'm using neither git nor SFTP. With my shared hosting everything is allright, no problems there. As I said before it's the AT theme. When I switch to any other theme commenting is no problem.

    Regards, Reiner

    rfmp’s picture

    Hello,
    I just wander what the state of this issue is. It is still impossible to comment on nodes. Whatever I try, it doesn't work. I sent you what you requestet one month ago. And now?

    mattbloomfield’s picture

    I haven't been able to reproduce the error on my end. Have you done anything to the comment field that might be interfering with the theme? I'm kind of grapsing at straws since I can't seem to experience the error myself.

    rfmp’s picture

    I haven't done anything with the comment field, but I had changed the form layout. I've hidden the comment title field. No Problems with other themes. Now I put the title field back again, flushed chaches, ran cron - same result. Impossible to comment.

    rfmp’s picture

    I just added a new comment type where all settings are exaktly the same as in the default comments. (Except the system name of the comment type, of course.) And that works! :-o I added a comment field of the new type to a node type, now I can comment on nodes of this type.
    That is good news on the one hand, on the other hand I ask myself what to do with all the existing comments and why commenting doesn't work with the default comments.

    sd123’s picture

    May this be related to an upgrade from D7? Check the known issues when upgrading from Drupal 6 or 7 to Drupal 9 or higher (several entries regarding comments).

    My site has no comments, so I haven't had any upgrade troubles in this regard.

    rfmp’s picture

    @sd123: No. I did switch from D7 to D9 but I didn't umgrade. I made everything new in D9 and managed the migration myself. And once again: the problem occurs only with AT. No Problems with other themes.

    @all: Now I deleted the comments field from the content type I used for testing and added a comments field of default type. Then again commenting doesn't work. I tried both options, adding the existig field and adding a new field. Same result, same error.

    rossidrup’s picture

    I have exactly the same problem...I cant edit the node and cant comment.....
    this theme is prehistoric.....when that guy got sick who created it ...seems it lasck a proper expert....

    I get mixin problem with it HTTP HTTPS problems which prevent the ckeditor and comment field to appear...
    my site works fine with other themes like bartik

    But I did upgrade from d7 to d9......

    mattbloomfield’s picture

    Wasn't the HTTP/HTTPS issue related to the RDF module?

    I still haven't been able to reproduce this issue. I don't know what modules you're using and I don't have much of an error log to go on other than a screenshot with a warning. If I had more info, I'd love to dig deeper.

    rfmp’s picture

    As I said months ago there are no more entries in the error log than the one that is shown in the screenshot. The important thing ist the "null" at the end instead of a URL. Well, there is one more entry, it is "access denied" because the access to the URL created by AT theme is denied.

    In order to recreate the malfunktion you need a website that was built with any other theme than AT and that has comments. Then install AT, switch to AT and post a comment. Then you'll have the error.

    Meanwhile I have installed a couple of further themes. AT is defenitely the onle one that produces this arror.

    rossidrup’s picture

    it exists....but not on all site....
    I have several installation of latest d9...adaptive theme works on 3 of them, it does not work on 1 of them

    the problematic one is the only one that was migrated from d7.....
    also perhaps there is a host problem...that is causing http / https issue

    RFMP if you look at the console...what do you see when you edit the content ?

    rfmp’s picture

    @rossidrup: I don't have the problem with editing nodes. My only problem is the commenting.

    mattbloomfield’s picture

    Have you by any chance tried creating a new field for comments on the Adaptive Theme? Maybe the comment field from the other theme doesn't exist in the generated theme.

    rossidrup’s picture

    I have problem both on commenting and editing ....both do not work....RFMP can you try another theme?
    I can edit and comment on bartik for example

    rfmp’s picture

    @mattbloomfield
    I wrote that already on Feb. 9th. I created a new comment type and added a comment field of the new type to a node type. That worked. But that's good for nothing because I have plenty of existing comments. They are important.
    Why should the existing comment field not exist in AT? And if, then why are existing comments shown in AT? If the "old" comment field is shown, it must exist.
    But your post/question leads me to another phenomenon. Since things worked with the new comment type I had the idea to simply convert all comments of the type "default" to the new type. Let's call the new type "test". At first I did that manually in the database for a few comments. There are three affected tables: "comment", "comment_field_data" and "comment_comment_body". I changed the feld "comment_type" from "default" to "test" in those three tables. But on my website I stll saw the default comments. I deleted the default comments field from the content type and added a test comments field. Then I didn't see any comment. And, of course, commenting an the default comments field didn't work.
    Then i took the module Convert Bundles and convertet the default comments with that. Same result. The same field in the same tables was changed, my website still showed the default comments and didn't show the test comments.
    That means: there must be another table in the database which stores information on comment types. A table that also the module Convert Bundles doesn't know. Do you know which table that could be???
    (By the way, this module workes fiine for node types.)

    @rossidrup
    I tried at least four themes. AT is the only one with that problem. I said that several times before. Maybe you didn't read my posts on this issue.

    rossidrup’s picture

    i have strange problem....I cant edit when logged in, the ckeditor does not show up and also the commend cbody is not showing....
    when I am logged in
    but when I am not logged in, the comments work fine....this is so strange....

    sahilgidwani’s picture

    Status: Active » Closed (cannot reproduce)
    sahilgidwani’s picture

    sahilgidwani’s picture