Toby
Waterhole
waterhole.dev
Toby's Comments
-
-
Ideas
- Edit post date
-
-
Toby
Waterhole
Founder
Nov 5, 2023 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.
-
Answer
Toby
Waterhole
Founder
Nov 5, 2023 This was fixed in the 0.3 release.
-
-
Support
- Issues with locked comments
Toby
Waterhole
Founder
Nov 5, 2023 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)
-
-
-
Blog
- Waterhole 0.3
Toby
Waterhole
Founder
Aug 16, 2023 In reply to
Manuel
Manuel
Aug 16, 2023 Yeah I had included these commands already. I actually dropped all tables with a migrate:fresh as well, as it's just test installations. But I still get the errors. Not sure how I can further investig...Curious! Can you please create an issue on GitHub containing the full details (SQL queries, environment info)?
-
-
-
Blog
- Waterhole 0.3
Toby
Waterhole
Founder
Aug 15, 2023 In reply to
Manuel
Manuel
Aug 14, 2023 I get errors on my local test instances after the update. I changed the requirement to 0.3 on two local instances, I don't get errors on the composer update, but when I try to access the sites I get d...Oops, forgot to include these command in the upgrade instructions:
php artisan migrate php artisan waterhole:cache:clearTry that and it should solve those errors. See the Updating docs page for info.
-
-
-
Development
- SSO with Firebase Auth
Toby
Waterhole
Founder
Aug 12, 2023 In reply to
René
René
Aug 9, 2023 Quick update — We're now considering using Waterhole's default auth as the main Login method for our web app too (blank.page). This way we have a single user database and avoid having to match account...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.
-
-
-
Ideas
- Avatar position
Toby
Waterhole
Founder
Jul 28, 2023 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.
-
-
-
Development
- SSO with Firebase Auth
Answer
Toby
Waterhole
Founder
Jul 28, 2023 Hi @René, I've never used Firebase Authentication before but I just had a look into this. As far as I can tell, Firebase doesn't expose an OAuth server so it can't be used with Laravel Socialite.
For the next Waterhole release (0.4) I am planning a single sign-on (SSO) feature that should make this integration possible. I'd be happy to help you set this up if you're happy to beta-test it!
In the meantime, launching with Waterhole's default auth should be fine as the SSO system will allow you to match up accounts by their email.
-
-
-
Blog
- Waterhole 0.2
Toby
Waterhole
Founder
Jul 24, 2023 In reply to
René
René
Jul 24, 2023 Hey @Toby, just out of curiosity, is there an expected timeframe for new updates?@René Aiming for releases every 1-2 months. 0.3 will release within the next week.
-
-
Toby
Waterhole
Founder
Jul 7, 2023 Hi @Joe,
Yes, this is something that I'm planning to add official support/docs for. For now it's untested and probably fairly limited (eg. there's no way to configure a separate DB connection for Waterhole). But the gist would be:
composer require waterholeforum/coreinto your Laravel project- Follow the rest of the Waterhole installation instructions
- Configure Waterhole's path prefix
In terms of auth integration, there's no solution at the moment but it's also on the roadmap for one of the next couple releases.
-
Toby
Waterhole
Founder
Jun 21, 2023 
Please note that running Waterhole on shared hosting is not officially supported. -
-
Development
- How to add a Stimulus controller?
Answer
Toby
Waterhole
Founder
Jun 21, 2023 Hi @mtdmy, you'll need to:
- Create a new Stimulus controller at
resources/js/controllers/hello_controller.js, and then register it with Waterhole's Stimulus instance inresources/js/app.js:
import HelloController from './controllers/hello_controller'; window.Stimulus.register('hello', HelloController);Set up a JavaScript compilation step - probably the easiest way is to use Laravel Mix. Output your compiled JavaScript to
resources/dist/app.js.Add this script to Waterhole's JavaScript bundle in your service provider:
Extend\Script::add(resource_path('dist/app.js'));Hopefully that's enough to get you started – let me know if you have any specific questions.
-
-
-
Support
- Keep me logged in
Toby
Waterhole
Founder
Jun 21, 2023 Hey @René! It doesn't seem to happen to me on this forum, at least
Checking the "Remember me" box should set a cookie called
remember_web_[random string]with an expiry of 1 year. Can you confirm that this is being set correctly? -
-
Answer
Toby
Waterhole
Founder
Jun 13, 2023 In reply to binksbinksJun 13, 2023 this one https://chrome.google.com/webstore/detail/%E7%81%AB%E5%B1%B1%E7%BF%BB%E8%AF%91-%E5%88%92%E8%AF%8D%E5%92%8C%E7%BD%91%E9%A1%B5%E7%BF%BB%E8%AF%91/klgfhbiooeogdfodpopgppeadghjjemkThis seems to be a conflict between Turbo Drive (a library that Waterhole uses to speed up page navigation) and this extension. Turbo Drive is simply replacing the
<body>via XHR, so it's a bug with the extension if it can't handle that. I would suggest contacting the extension developer to submit a bug report.A workaround is to reload the page, and then it will work again (up until you navigate to another page).
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_atdate in the database.