I have been working on diagnosing this problem today and I found that disabling the 'File Framework' submodule, 'Attachment' present is the difference maker.

**Problem**:
I can preview, but submission does not load the comment so that it blinks and appears in real time as it is expected to do. Instead I have to reload the page in order to view the submitted comment.

**Other Observations**:
I was able to get the correct result only after disabling File Framework altogether. The issue had, in my case, nothing to do with theming as it does here: http://drupal.org/node/542846.

What is interesting is that when I select in admin/content/type/blog and remove 'file attachments' in comment form, the field in the corresponding form goes away ONLY when Ajax Comments is deactivated. When Ajax Comments is activated for the content-type, however, the ' File Attachments' array reemerges in the form even though it is "disabled" in the admin/content/type/blog settings.

This has led to a predicament. any ideas?

Although I would like to be able to have attachments in comments, it's not important. If I could effectively disable the field for comments so it does not conflict with Ajax Comments, that would be just fine. I'll post this issue to 'File Framework' as well.

Comments

Equinger’s picture

Since I last posted, I've messed around a lot with the weights of the modules ('Attachments', 'Comment', 'Comment Bonus API', and 'Ajax Comment') as I recently found that relevant to other Ajax loading. Hasn't affected anything unforunately.

Equinger’s picture

Any thoughts on this one?

Toxid’s picture

I have the same problem, I don't have comment bonus api. Perhaps this is theme related?

rjbrown99’s picture

If you are having issues, please test with the latest -dev branch and comment_bonus_api.

In terms of integration with other modules, I'm not personally using FileFramework so I won't be able to offer a lot of assistance with that one. The README has a bit more information now on troubleshooting so hopefully it will be of help. Otherwise I am happy to review a patch if you determine the source of the integration issue.

qzmenko’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Issue is closed because 6.x version is unsupported. Feel free to open new issue for 7.x or 8.x versions of module.