1: I will be installing WP Amelia on many client sites. In the settings, the licence code is visible in plain sight. This means my customers can give my licence code to whoever they want. Please hide this. If this remains plain text, I will have to request a refund.
2: Also, as I have seen, you have received many requests for whitelabel/removal of branding. Again, lack of a custom branding option makes this plugin more risky for me to sell as a service. I have circumvented your branding on a test server in CSS, but it's a pain. Are there any plans to introduce custom branding? If so, I can recommend at least 3 agencies I work with to buy the lifetime agency licence from you. Otherwise, they will not buy.
1. You can hide the Activation setting in Amelia -> Settings and this needs to be done in your database. When you access your database, please open the wp_options table (it can have another prefix rather than wp_ depending on your database) and then find the amelia_settings option there. You need to edit it and find the activation property in it, and change the value for the the showActivationSettings from true to false, like here:
2. It's on the the features request list, unfortunately, I can't say when exactly that will be introduced, sorry.
Regarding the white labeling question.
- Just create the .svg images that will be the same size as amelia-logo-symbol.svg and amelia-logo-horizontal.svg, name them exactly the same as these two images, and then replace these two images from folder ../wp-content/plugins/ameliabooking/public/img/ with the images you created.
- You can change this in file ../wp-content/plugins/ameliabooking/src/Infrastructure/WP/WPMenu/Submenu.php in function addOptionsPages(). The image from the menu is called amelia-logo-admin-icon.svg, you should call your image the same replace with your. Also, you can change the name of the menu item in this function.
Please note: When you update the plugin, your changes will be lost, so you will need to do this each time after you update the plugin.
Words (like name) can be changed using POEDIT or Loco Translate for example very easily. I suggest installing Loco Translate and then to translate the strings you need.
This manual method of protecting the licence code I have paid for is like something out of the 1990s.
I have bought a lifetime developer licence, and expect to add this to many, many client sites. To have to hide the code in this way is bizarre. This should be addressed with priority. Currently you have 100s, maybe 1000s of agencies with active developer licences on 1000s, possibly 10,000s of client sites. Each of those sites is providing £400+ worth of licence code for free. I wonder how many licence sales you have missed out on, because a nulled site is offering lifetime licences. Do you have plans to add some form of obfuscation, like almost every other premium plugin out there?
This and the white-labelling issues are the only issues making me consider requesting a refund. While they are circumventable, they are a drag on any agency looking to seriously consider your software. As I mentioned, I am in contact with at least three other agencies who would be interested in buying developer lifetime licences, but would be discouraged by these issues.
Regarding the white labelling issue, you can do this in CSS, negating the need to repeat the process every time the plugin updates.
Thank you for your suggestions. They will be forwarded to our development team for review. We're developing new features based on the number of votes they receive from our customers, and by their priority. We do not provide any ETAs for upcoming features, as there are many factors in the development, so we can't say if there will be a crucial bug that will postpone development of a new feature; or if developing a new feature will cause some issues with currently working features of the plugin.
We have a full white-labeling option planned for the future, but I can't share any details of that with you, so I cannot even remotely guess when it will be added. You're correct that adding that CSS would be useful for your use case, and thanks for your advice. I'll make sure it is used as a response for other customers that have similar requests.
Our developers will be working on a different way of hiding the purchase code, but at the moment this is the only way.
Yes I understand that the database method is superior, but I have just given you the code that would make a HUGE improvement RIGHT NOW. It is 100% better than what you currently have, and I have written it for you. Copy/paste, walk away. No?
Your approach to this is bewildering; It's like saying "I'm not going to replace my flat tyre with this free silver tyre, because in a years time I might buy a gold one!"
Replace your flat tyre so you can get to the garage, and then aim for perfection. There is NO downside to you implementing this now, and replacing it later.
Sorry if my response came off wrong, it was not my intention.
What I meant to say is that we are going to work on a better solution than just adding type="password" and that we're currently exploring better options so even modifying it through the console will not reveal it.
We will, however, use the code you generously provided in our next update, and hide the purchase code behind asterisks.
I'm sorry, we have a lot of tickets coming in, so I never finished that thought.
Thanks for your candid reply, Aleksandar, it's appreciated. Apologies if I came across as impatient, I've just been getting rather frustrated with Amelia recently I'm afraid.
In May of last year, you (specifically you - https://imgur.com/aqsepsL) told the folks over at AppSumo that a white label option for developers was on the cards soon. But since then I've seen multiple comments form you and staff that this either isn't happening at all, or isn't planned any time soon. It's also not on your roadmap.
All this requires is implementation on the dashboard, and an upload field linked to it. Yes, I'm sure it's far from perfect. But it would satisfy the commitment you gave to the AppSumo crowd (and others) in very little time. I'd then be able to recommend my 3 associates to buy developer licences, too. £1500 in your pocket and a whole chunk of happy developers for likely less than a couple of hours work. Copy/Paste/tweak-a-bit/win.
Having worked in web design+development for over 6 years I can assure you that I understand what a developer licence is for, and how it works. I am of course not selling licence keys on, or installing Amelia on websites separate to me. My meaning was, of course, selling Amelia as part of websites that I build or significantly upgrade. I offer full website design with booking included, please let me know if this falls outside the licence terms. My associates are web designers, but do not work in development very much (calling me in when needed), and would therefore be beholden to me to change the branding for every project they produce. They are keen on positioning themselves as specialists in creating booking websites. As companies solely offering booking websites, my fees for simply changing a logo are an ongoing cost that they're unwilling to pay.
That said, I find it rather difficult to believe that your team is particularly interested in how these licences are used, given that it has taken so long for you to hide licence codes, but hey-ho.
Your response on the other thread was, again, yet another example of waiting for the gold tyre, to the detriment of your customers.
You say that complete white labelling is not planned, but then immediately discount the silver tyre solution I have given you. If I can achieve it on my client installs, (albeit via laborious CSS and plugin messing around) then you can as part of your plugin.
I can't speak for the other developers here, but in my case specifically, being able to change the logo easily (achieved via the silver tyre supplied) would satisfy (in my mind, at least) your commitment to the AppSumo folks. Many people on Appsumo would have stacked many codes, based on your promise that they could change the branding easily, soon. One of the reasons I felt so comfortable buying a developer licence (at full price) was that I'd read many comments saying it was planned, and a few (from yourself, too) that it was coming soon.
An upload field for a logo is not difficult, Aleksandar. It really isn't. Sure; perhaps it doesn't satisfy every condition to be a complete white label solution (gold tyre), but it's enough of a silver tyre to satisfy your commitment, at least in the short to mid-term.
I believed that was the case originally, but wanted to make sure. You wouldn't believe how many times we ran into duplicates of Amelia, being sold as another plugin (while the back-end pages would still show "wp-admin/admin.php?page=wpamelia-services#/services" for example). Thanks for being cool about my question, as I was not implying anything, just asking for an explanation.
You are, of course, allowed to create and sell websites with Amelia installed on them.
Covid-19 shifted our focus to Zoom, Packages, and some other features, so adding options to change the logo, and the name were put aside. Again, thank you for the silver tyre, I will definitely forward it to our development team, like I did for the password yesterday.
I'll see if I can push this with our developers, so it's included sooner rather than later.
Hello!
1: I will be installing WP Amelia on many client sites. In the settings, the licence code is visible in plain sight. This means my customers can give my licence code to whoever they want. Please hide this. If this remains plain text, I will have to request a refund.
2: Also, as I have seen, you have received many requests for whitelabel/removal of branding. Again, lack of a custom branding option makes this plugin more risky for me to sell as a service. I have circumvented your branding on a test server in CSS, but it's a pain. Are there any plans to introduce custom branding? If so, I can recommend at least 3 agencies I work with to buy the lifetime agency licence from you. Otherwise, they will not buy.
Kind regards,
Mike
Hello,
Thank you for getting in touch.
1. You can hide the Activation setting in Amelia -> Settings and this needs to be done in your database. When you access your database, please open the wp_options table (it can have another prefix rather than wp_ depending on your database) and then find the amelia_settings option there. You need to edit it and find the activation property in it, and change the value for the the showActivationSettings from true to false, like here:
2. It's on the the features request list, unfortunately, I can't say when exactly that will be introduced, sorry.
Regarding the white labeling question.
- Just create the .svg images that will be the same size as amelia-logo-symbol.svg and amelia-logo-horizontal.svg, name them exactly the same as these two images, and then replace these two images from folder ../wp-content/plugins/ameliabooking/public/img/ with the images you created.
- You can change this in file ../wp-content/plugins/ameliabooking/src/Infrastructure/WP/WPMenu/Submenu.php in function addOptionsPages(). The image from the menu is called amelia-logo-admin-icon.svg, you should call your image the same replace with your. Also, you can change the name of the menu item in this function.
Please note: When you update the plugin, your changes will be lost, so you will need to do this each time after you update the plugin.
Words (like name) can be changed using POEDIT or Loco Translate for example very easily. I suggest installing Loco Translate and then to translate the strings you need.
Hi Dan,
Thank you for your reply.
This manual method of protecting the licence code I have paid for is like something out of the 1990s.
I have bought a lifetime developer licence, and expect to add this to many, many client sites. To have to hide the code in this way is bizarre. This should be addressed with priority. Currently you have 100s, maybe 1000s of agencies with active developer licences on 1000s, possibly 10,000s of client sites. Each of those sites is providing £400+ worth of licence code for free. I wonder how many licence sales you have missed out on, because a nulled site is offering lifetime licences. Do you have plans to add some form of obfuscation, like almost every other premium plugin out there?
This and the white-labelling issues are the only issues making me consider requesting a refund. While they are circumventable, they are a drag on any agency looking to seriously consider your software. As I mentioned, I am in contact with at least three other agencies who would be interested in buying developer lifetime licences, but would be discouraged by these issues.
Regarding the white labelling issue, you can do this in CSS, negating the need to repeat the process every time the plugin updates.
3: replace the URL with any logo image.
This will swap the logo and changes will persist throughout plugin updates.
Is there an ETA on either of these issues?
Kind regards,
Mike
Hi Mike,
Please, let me clarify this with the tech team and get back to you. This will be early next week.
Hi Mike,
Thank you for your suggestions. They will be forwarded to our development team for review. We're developing new features based on the number of votes they receive from our customers, and by their priority. We do not provide any ETAs for upcoming features, as there are many factors in the development, so we can't say if there will be a crucial bug that will postpone development of a new feature; or if developing a new feature will cause some issues with currently working features of the plugin.
We have a full white-labeling option planned for the future, but I can't share any details of that with you, so I cannot even remotely guess when it will be added. You're correct that adding that CSS would be useful for your use case, and thanks for your advice. I'll make sure it is used as a response for other customers that have similar requests.
Our developers will be working on a different way of hiding the purchase code, but at the moment this is the only way.
Has there been any update on this?
Every one of my customers has access to a lifetime developer licence worth over £500 because you don't bother hiding it.
This is NOT a difficult task for your developers. Obscuring a field is a few lines of code, at worst.
Literally ALL you have to do is add this to your plugin:
One of my clients could be selling lifetime licences on Fiverr and you'd be missing out on 1000s of sales.
I'm just shocked that this is still a thing.
Yes I understand that the database method is superior, but I have just given you the code that would make a HUGE improvement RIGHT NOW. It is 100% better than what you currently have, and I have written it for you. Copy/paste, walk away. No?
Your approach to this is bewildering; It's like saying "I'm not going to replace my flat tyre with this free silver tyre, because in a years time I might buy a gold one!"
Replace your flat tyre so you can get to the garage, and then aim for perfection.
There is NO downside to you implementing this now, and replacing it later.
Sorry if my response came off wrong, it was not my intention.
What I meant to say is that we are going to work on a better solution than just adding type="password" and that we're currently exploring better options so even modifying it through the console will not reveal it.
We will, however, use the code you generously provided in our next update, and hide the purchase code behind asterisks.
I'm sorry, we have a lot of tickets coming in, so I never finished that thought.
Thank you once again for the suggestion!
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thanks for your candid reply, Aleksandar, it's appreciated.
Apologies if I came across as impatient, I've just been getting rather frustrated with Amelia recently I'm afraid.
In May of last year, you (specifically you - https://imgur.com/aqsepsL) told the folks over at AppSumo that a white label option for developers was on the cards soon. But since then I've seen multiple comments form you and staff that this either isn't happening at all, or isn't planned any time soon. It's also not on your roadmap.
Again; here is a silver tyre
All this requires is implementation on the dashboard, and an upload field linked to it.
Yes, I'm sure it's far from perfect. But it would satisfy the commitment you gave to the AppSumo crowd (and others) in very little time. I'd then be able to recommend my 3 associates to buy developer licences, too. £1500 in your pocket and a whole chunk of happy developers for likely less than a couple of hours work.
Copy/Paste/tweak-a-bit/win.
Hi again Mike.
I already responded to the other ticket you commented on regarding what I said on AppSumo:
https://tmsplugins.ticksy.com/ticket/2535776
There's a far more pressing concern in that ticket about reselling Amelia, so please take a look at it and let me know what you meant by that.
Once again, thank you for the code for the purchase code. We will add this option in the plugin (hopefully with our next update).
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Aleksander,
Having worked in web design+development for over 6 years I can assure you that I understand what a developer licence is for, and how it works. I am of course not selling licence keys on, or installing Amelia on websites separate to me. My meaning was, of course, selling Amelia as part of websites that I build or significantly upgrade. I offer full website design with booking included, please let me know if this falls outside the licence terms. My associates are web designers, but do not work in development very much (calling me in when needed), and would therefore be beholden to me to change the branding for every project they produce. They are keen on positioning themselves as specialists in creating booking websites. As companies solely offering booking websites, my fees for simply changing a logo are an ongoing cost that they're unwilling to pay.
That said, I find it rather difficult to believe that your team is particularly interested in how these licences are used, given that it has taken so long for you to hide licence codes, but hey-ho.
Your response on the other thread was, again, yet another example of waiting for the gold tyre, to the detriment of your customers.
You say that complete white labelling is not planned, but then immediately discount the silver tyre solution I have given you. If I can achieve it on my client installs, (albeit via laborious CSS and plugin messing around) then you can as part of your plugin.
I can't speak for the other developers here, but in my case specifically, being able to change the logo easily (achieved via the silver tyre supplied) would satisfy (in my mind, at least) your commitment to the AppSumo folks. Many people on Appsumo would have stacked many codes, based on your promise that they could change the branding easily, soon. One of the reasons I felt so comfortable buying a developer licence (at full price) was that I'd read many comments saying it was planned, and a few (from yourself, too) that it was coming soon.
An upload field for a logo is not difficult, Aleksandar. It really isn't.
Sure; perhaps it doesn't satisfy every condition to be a complete white label solution (gold tyre), but it's enough of a silver tyre to satisfy your commitment, at least in the short to mid-term.
Thanks for the explanation, Mike
I believed that was the case originally, but wanted to make sure. You wouldn't believe how many times we ran into duplicates of Amelia, being sold as another plugin (while the back-end pages would still show "wp-admin/admin.php?page=wpamelia-services#/services" for example). Thanks for being cool about my question, as I was not implying anything, just asking for an explanation.
You are, of course, allowed to create and sell websites with Amelia installed on them.
Covid-19 shifted our focus to Zoom, Packages, and some other features, so adding options to change the logo, and the name were put aside. Again, thank you for the silver tyre, I will definitely forward it to our development team, like I did for the password yesterday.
I'll see if I can push this with our developers, so it's included sooner rather than later.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
https://wpamelia.com/changelog/
🤦♂️
I was expecting and questioning this concern in a few of my ticket.
Hello Mike and Frenk.
I suppose both comments are referring to the purchase code not being hidden with v3.1.2.
This will be included in the next update.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables