Dwight Watson

See #54 for more information. You’ll need to provide a lot more sample code if we’re to have any hope working out what’s wrong on your end.

You shouldn't have to do that - the `render()` method will check for a cached view and return it by default. See [these lines](https://github.com/dwightwatson/sitemap/blob/master/src/Watson/Sitemap/Sitemap.php#L169-L189).

Yeah... that's actually a very fair point. Will re-open this as to address the documentation on this area better. Open to PRs on it otherwise I'll try and find some...

I suppose it could, the question would be how should it route to multiple sitemaps. If you have any good ideas on how to approach this let me know. Here's...

Cool, I've added some details to the docs about using `select()` and `chunk()` to reduce the memory being used for a sitemap request - that should alleviate most blank screen...

Happy to look over any PR that wants to take a stab at implementing this.

Laravel's Vonage channel provides a way to change the client on the message if required: https://github.com/laravel/vonage-notification-channel/blob/3.x/src/Channels/VonageSmsChannel.php#L69 I've followed that pattern on a few notification channels too. Sounds like it could...

This is an old issue so I'm going to close it. Please reach out if it's still a problem.

I'm not overly familiar with the concept of "projects" but I'm concerned this might not be the right approach for solving this. Are push tokens scoped to a project? If...

As mentioned in the PR I suspect this is is an issue with the return of your notification's `via` method.