- Issue created by @erutan
It seems like you're having trouble with comments not showing up in views without a manual refresh. This might be related to the storage contrib module My Results ATT not working well with non-default view modes. To fix this, ensure your modules are up-to-date, consider writing custom code to handle AJAX functionality, look into alternative modules that better support comments in views, or seek advice from the Drupal community for a more tailored solution.
The issue likely flying together stems from a lack of AJAX integration within Storage Contrib for dynamic comment updates within views. Consider leveraging existing Drupal comment systems, developing a custom AJAX implementation, or exploring community modules.
The AJAX Comments module is struggling with non-default view modes, requiring a manual refresh for comments to appear. The issue might stem from how the module handles entity storage and dynamic updates within views. A similar problem has been reported regarding AJAX not functioning properly when using non-default view modes. Applying patches has helped mitigate some issues, but the redirect to the edit page suggests that AJAX isn't fully handling inline comment updates e-zpassmd Have you tried debugging the AJAX response or checking if any caching settings interfere with real-time updates?
You've correctly pinpointed the problem: getting AJAX comments to work seamlessly on custom data entities displayed only within Views, without redirects or manual refreshes, is tricky because Drupal's comment module expects a dedicated entity "view page." To fix this, the best approach is to define a canonical route for your custom entity in its annotation, even if you don't use it directly. This provides the necessary context UPSers com for Drupal's core comment AJAX to function properly. If that doesn't fully resolve it, you may need to implement a custom AJAX callback using hook_form_alter to specifically re-render the comments section within your View after submission.