Toby

v0.3.1

v0.3.1 has been released with the following changelog:

Added

• Add Traditional Chinese (zh-Hant) translation (#8 by @efast1568)
• Update French translation (#14 by @Qiaeru)

Changed

• Load reaction counts as a relationship rather than via query scopes

Fixed

• Fix reactions disappearing when following/unfollowing a post
• Opt out of smooth scrolling on Google Chrome
• Fix Copy Link action not working
• Disable login submit button to prevent double-submission
• Fix mobile page selector sometimes displaying incorrect page number
• Fix active nav items and buttons not highlighted in Firefox
• Remove max-height from images causing loss of aspect ratio
• Remove extra space from post title on comment page
• Fix post Delete Forever action not working
• Fix crawlers causing 500 error with invalid pagination cursor
• Don't scroll all the way to bottom of the page when opening composer

Good call @Subarist - I have made an issue for this to be implemented soon.

This seems to be a bug! Will look at a fix soon.

Hey @René, this is a good idea which I'll consider for a future release. In the meantime the workaround would be to manually edit the post created_at date in the database.

Thanks for the suggestion @Subarist. IMO displaying a larger number of pages does serve a couple of purposes:

• Provide the user a bigger target in which they can scroll through and navigate pages
• Serve as a visual cue that there are a large number of pages in the discussion, not just a few

So right now there are no plans to change this part of the UI, but you can easily customise it yourself by changing the max-height of the scrollable container. Your suggestion to display the date alongside the current page number is potentially a nice idea.

Hey @René! Locking comments doesn't apply to administrators (or anyone with the "moderate" permission for the current channel). However, in this case the "Comments are locked" notice should still display above the comment box.

Can you confirm that if you impersonate a regular user, you're unable to post a comment in a locked post? And as an admin, is there any discernible pattern to when the notice displays vs when it doesn't? (e.g. in a specific channel, only when there a multiple pages of comments, etc)

Using Waterhole as an auth provider for external apps is not currently supported. I will keep this in mind when building the SSO feature – that could definitely be a useful addition.

The other way to do it would be to implement Laravel Passport to add an OAuth2 server to your Waterhole installation, and then authenticate external apps with that. But this would require a bit of custom dev work.

Can't see the image you linked (and sorry about the attachment issue, should be fixed now). I know what you mean though! I'll make this change.

@René Aiming for releases every 1-2 months. 0.3 will release within the next week.