Added possibility of custom plausible domain

[mascali33]

Added an option to use custom plausible domain in grav admin

Modified php file to reflect changes in config

Lang file need to be reworked, did "en" but not the other langs

[iainsgillis]

@mascali33 Is this better described as pertaining to serving the plausible script from a custom domain as described here?

[iainsgillis]

Hi -- Thanks for initiating this!

I've added a couple of comments about specific lines. In languages.yaml, the help text about the new field you've suggested (self-hosted vs custom domain) will ultimately have ramifications on the README and in the translations, so I want to be clear about that before proceeding.

In general, what do you think about adding a toggle (enabled/disabled) in addition to the custom domain field? I'm guessing that most users (like myself) use the hosted Plausible service with the default setup.

Adding a toggle doesn't complicate the UI much, and is a little more intentional for users who wish to setup a custom domain (whether by running their own docker instance, or the CNAME record).

My concern is that the semantics are a little confusing if we use the placeholder of a custom value as the default value for the stock configuration that Plausible's hosted service ships with.

Also, adding a toggle gives users an easy way to undo changes when rolling out a custom domain setup.

@rootarch @Audiotape-2 -- since you're among the very few who have starred this repo (thanks!): do you have any thoughts about the toggle/custom domain field implementation?

Thanks again for moving this plugin forward.

[rootarch]

@iainsgillis I like the simplicity of the toggle to easily enable/disable the Custom Domain feature.

I also agree with your thoughts about using https://plausible.io/ as the default value for a custom variable. Is it worth defining logic that uses https://plausible.io/ as the default, ignoring the Custom Domain field if it is left blank/empty?

[iainsgillis]

Hi, Folks --

Apologies for the delay: bit of a busy stretch personally and professionally.

Appreciate the initial pull request, @mascali33, and your weigh-in @rootarch. I'm going to proceed with this beginning this evening and hope to release it by the weekend.

Cheers,
Iain