Comments can be useful for a variety of sites. But, with core only, there are some shortcomings in the UX and configuration options, for example the order of comments on nodes can only be oldest to newest. Also, through Zulip discussions it was identified that not all comments were being indexed for search, only those on the first page of a full node display.
Here's what was assembled and used to enhance comments:
Core issues (PR available to patch if not merged):
- [Fix redirect on unapproved comments page](https://github.com/backdrop/backdrop-issues/issues/4314), merged.
- [Search results numbering resets to 1 on each page](https://github.com/backdrop/backdrop-issues/issues/7160)
- [Reply to comment link is missing anchor #comment-form](https://github.com/backdrop/backdrop-issues/issues/7162)
- [Comments pager missing anchor #comments](https://github.com/backdrop/backdrop-issues/issues/7163)
Contrib modules installed and configured:
- [Comment Sort Weight](https://github.com/backdrop-contrib/comment_sort_weight)
- [Comment Search](https://github.com/backdrop-contrib/comment_search)
- [Comment Publish](https://github.com/backdrop-contrib/comment_publish)
- [Search Combined](https://github.com/backdrop-contrib/search_combined)
- [Pagerer](https://github.com/backdrop-contrib/pagerer)
- [Pager Fix](https://github.com/backdrop-contrib/pager_fix)
Just read the issues and the module README files and see how they fit together.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists