Toby

Yeah, this is strange – I've been trying to repro on your actual account using the impersonation feature, but it works fine (see your updated avatar).

I'm at a bit of a loss here... are you running any browser extensions that might interfere? Can you try with JavaScript disabled?

Regarding the broken image in the email notification, that should be fixed. Please let me know if it happens again.

@Adeala Ademola You've just posted an nginx config and an Apache config. Which webserver are you using? I'm not confident I'll be able to help you since this seems like a server configuration issue rather than an issue with Waterhole itself.

Edit: Just thought of something that might help. Try running php artisan waterhole:cache:clear

Migrations can be so painful! Nice job working through the issues here @Subarist.

It would be quite trivial to write an extension to enable BBCode on Waterhole - it uses the same formatting library under the hood as Flarum.

Hi @Subarist, take a look at the Troubleshooting docs to start with.

1. Can you check the permissions of the public/storage directory and the files within it?
2. Assuming these are okay, then I think the issue is likely at the nginx level. Can I see the configuration of your full server block? The config you've posted above is just an excerpt.

Hi @NathanK, I can't seem to replicate this issue... What browser are you using?

Hi @Subarist,

I've just pushed a couple of fixes to user importing. Please make sure the version constraint for the waterhole/import package in composer.json is set to * or 0.1.x-dev, and then run composer update to pull in the changes, then try running the import again.

The groups error indicates your database already has some data in it. Per the docs, make sure you're running this on a fresh Waterhole installation, before the waterhole:install command has been run.

Thanks for the ideas! Some of the stuff I've written in the Philosophy is also highly relevant here:

The Waterhole business model is very simple: We make great software. You pay to use it. That money goes back into making the software even better. [...]

By charging for licenses, we avoid having to undertake other activities which would distract from product development, like soliciting donations, or running services. We believe that others are better placed to offer services around Waterhole, and we encourage freelancers, agencies, and entrepreneurs to seize this opportunity and become a part of the ecosystem.

That is to say, I'm not interested in doing anything involving services at this stage.

Dual licensing is too complicated. I think the only way I could see this working is with some kind of product limitation, like the Craft/Statamic model. Will keep thinking about it.

Thanks for the question. I've started a new discussion as my response: How could a free tier work?