# Journal Plugin

**URL:** https://meta.discourse.org/t/journal-plugin/317785
**Category:** Plugin
**Tags:** pavilion, broken, experimental
**Created:** [July 23, 2024, 9:04am UTC](https://meta.discourse.org/t/journal-plugin/317785 "2024-07-23T09:04:50Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [July 29, 2024, 8:34am UTC](https://meta.discourse.org/t/journal-plugin/317785/9 "2024-07-29T08:34:07Z")

</div>

> [@jrgong](#):
>
> Instead of regular posts, comments (aka replies to journal entries) should work in a similar fashion as in the [post voting plugin](https://meta.discourse.org/t/discourse-post-voting/227808)

Could you be more specific on this front? You think it should be identical?

Note that the Post Voting plugin was originally the Question Answer Plugin, which the Journal Plugin was a spun out of ([see further](https://meta.discourse.org/t/question-answer-plugin/56032/284)). Bringing this one up to speed with the commenting changes in Post Voting is doable.

> [@Mr.X\_Mr.X](#):
>
> The comment button should be more visible, for examples for instances using Reactions, the button is not even visible unless one horizontal scrolls.

Interesting. Not sure if that’s an issue with this plugin or the post menu itself, but yes that’d need to be resolved. Is that mobile or desktop? What browser is it?

> [@Jagster](#):
>
> I don’t allow mega-topics and after 50th post that topic shall be closed and new topic is created.
> 
> - such automatic created are own by system, so I have to change owner, right?
> - in my case 50 post limit is still valid and because Journal is ”just” a topic in steroids, even comments of enries are counted toward 50 limit because technically those are comments of a post when entries are comments of topic, right?

hm, interesting system you have going there. The answer will depend on how you’ve set up this automated topic splitting system. Entries are distinguished from Comments on the basis of whether the post has a `reply_to_post_number`, i.e.

```ruby
entries = posts.where(reply_to_post_number: nil)
comments = posts.where.not(reply_to_post_number: nil)

```

So you could tweak your topic splitting algorithm to take that into account.

> [@Jagster](#):
>
> can I change a comment that is now entry instead beeing comment of an entry

To turn a Comment into an Entry remove its `reply_to_post_number` value.

> [@Jagster](#):
>
> I have a lot journal type topics and Ichanged those to this system, but everyone commented to topic, and now those show as entries. Well, old topic and quite few new members read those even and I’m totally sure they don’t care how content is shown.

hm not quite sure what you mean here, but hopefully my explanation of the distinction between entries and comments will give you the answer.

> [@piffy](#):
>
> I think the only thing I could highly recommend improving is how it jumps to new comments when you revisit the topic. It’s hard to explain but sometimes it’s janky/unclear where the new comments is when you’re catching up

Yes, the “topic entry” and timeline UX would need to be improved.

### Working to do list

- Improve comment UX
- Improve topic entry and timeline UX
- Add full suites of frontend and backend tests
- Resolve UX conflicts with other widely used plugins and core.

---

_[View the full topic](https://meta.discourse.org/t/journal-plugin/317785)._