Toby

No it was released on 16 April! Maybe try clearing your Composer cache with composer clear-cache?

Laravel 11 support has been added in 0.4.8

@Ryan Pitts Hopefully you're able to switch back over to the official package - let me know if any issues. But for future reference, the command to compile Waterhole's assets is npm run prod.

Hey @Tyler DuPont, this is a great point. I've created an issue for this here which will aim to fix in a future version. As a workaround, if you're on a Mac you can hold down the Option key as you press the Space bar to continue filtering suggestions.

Yep, that's right about conditional rendering - there's a note on this in the Extenders doc. The way you've done it works well, or an alternative would be to replace the search component with a closure and conditionally return the search component:

use Waterhole\View\Components\HeaderSearch;

Extend\Header::replace('search', fn() => Route::is('waterhole.*') ? HeaderSearch::class : null);

Regarding adding relationships to Waterhole's User model, using resolveRelationUsing is fine when you're interacting with a package like Waterhole – the Laravel docs are talking about "normal application development" as in within your own app's codebase. Creating your own subclass of the Waterhole User model is also a nice idea, although I'm not 100% certain it will work in all cases as I believe some instances of the User model are hardcoded throughout Waterhole's codebase – I will definitely look at making this configurable in the future.

Hey @Stormlight,

The Waterhole project skeleton is really just a slightly stripped-down version of the Laravel 10 skeleton (no Vite, no API routes, etc.) with some default configuration in place – use the Waterhole User model for auth, and add a service provider for Waterhole customizations.

Whether you start with the Laravel skeleton and pull in Waterhole, or start with the Waterhole skeleton and pull in things from the Laravel skeleton as needed, you'll end up at pretty much the same place. So do whatever you're most comfortable with

As you've discovered, you can build new pages within the Waterhole layout using the <x-waterhole::layout> component, or if you just want the CSS (and not the layout) you can use <x-waterhole::html>. A list of all Waterhole components is available in the class reference.

See here for Laravel 11 discussion - we'll stay on top of future Laravel releases relatively quickly.

Hi @Ryan Pitts, thanks for your interest in Waterhole! Laravel 11 support is planned, it should be pretty straightforward and I hope to look at it in the next week or so.

Hey @Greg Garrison, "private discussion" on the homepage is referring to the ability to set up user groups and permissions for different parts of the community. Let me know if you have any questions about how it works!

Ah, I see - that link is a part of Waterhole by default so I wasn't sure if it was the one you were talking about. But, it only shows up if there is a route named waterhole.register - and if you have set the allow_registration config to false (as you should when setting up the Laravel integration), then that route won't exist.

The solution is to register your own register route to redirect to your app's registration page, similar to what should already be doing for the login route:

Extend\ForumRoutes::add(function () {
    Route::name('register')->get(
        'register',
        fn() => redirect()
            ->setIntendedUrl(url()->previous())
            ->route('register'),
    );
});