Hi, I looked around a bit and didn't see reference to this, so hope it's not wasting your time:
I am just updating my Cloudmin subscription to the new setup (last time I renewed was on the old shopping cart system). I was reading instructions and I'm seeing a spelling error that could cause confusion:
On this page about Software Licenses, it references running the "change-licence" command: https://www.virtualmin.com/license-faq
At first, I thought it was a spelling error, so I spelled it "change-license", which of course didn't work. So, the command itself is in fact spelled incorrectly. As long as people follow the instructions explicitly, they'll get it to work right, but if you just type it in w/ correct spelling, it will fail.
Not sure if this is worthy of a fix or not, since the instructions are clear and it does work as listed (or maybe I'm wrong and it should be spelled with a 'c'?). I just figured I'd point it out in case it comes up for anyone searching the issue queue for the correct spelling not working.
Cheers.
Comments
Submitted by andreychek on Thu, 07/27/2017 - 22:21 Comment #1
Howdy -- thanks for contacting us!
You're right, that should indeed be changed. Jamie, can we make both versions work, just as Virtualmin does now?
paulhoza, Jamie (the primary developer) is from Australia, where they spell things weird like that :-) We updated Virtualmin to accept either version, though it seems Cloudmin escaped fixing :-)
Thanks for the heads up!
Submitted by JamieCameron on Fri, 07/28/2017 - 00:41 Comment #2
Sure! I'll fix this for the next release ..
Submitted by JamieCameron on Fri, 07/28/2017 - 00:41 Comment #3
Submitted by paulhoza on Fri, 07/28/2017 - 01:12 Comment #4
Haha! I didn't mean to ignite a cultural firestorm! :)
Thanks.
Don't forget to update the documentation on the aforementioned FAQ, in case that wasn't already lined up. It should be consistent with the rest of the page in the code quote sections.
...I'll stop adding more work for you guys now. Promise. :P
Submitted by IssueBot on Fri, 08/11/2017 - 01:30 Comment #5
Automatically closed - issue fixed for 2 weeks with no activity.