When I add custom fields it includes a colon automatically after the label. The problem is that when I ask questions ending in question marks, the colon stays there, regardless. And of course, it shouldn't. Can you please look into this?
PS: I've already asked Marija in another ongoing ticket. I decided to open a new one as the subject is different.
The colon is added programmatically, and changing it would require changing the code.
JS files are modified (minimized) in public version of plugin (in our development environment is accessible), but unfortunately I can not send you our source code because that is the policy of our company.
All those files that have extension .vue are compressed and minimized in JS files that is very hard and not recommended modifying. So in order to add some other features you can unminify the js and customize it.
You could probably do it by editing innerHTML element, and removing the colon from there, but that would require a custom JavaScript to run on the page, target each of the custom fields, and edit their content.
Please note that customization questions like this are not included in provided support, which only refers to advice, but you can explore stack overflow, and you may be able to find some useful tips there.
It never even crossed my mind that I would have to edit files and fix that myself. That's not my responsibility. I find it extremely intriguing that you'd suggest a way for me to fix that problem, when it's your product's flaw. Maybe you deal with programmers here and you're used to saying things in their language. But I'm just a customer who bought your product and it has a problem.
Now, are you saying that this error will stay on the page and you won't fix it?
That's not an error, that's the feature of the plugin. You're adding custom fields, and their description is ended in a colon. Exactly like "Type of call:" in the first step:
I can see that you rethought the custom fields, so they have more sense with a colon instead of a question mark.
The suggestion that this is something customers can choose will be forwarded to our development team, so they can work on it for one of our future updates, but at the moment it is considered a custom solution, which doesn't fall under included support for the plugin, so I can't help you with it.
If our developers find a workaround for you, I will share it with you.
Thank you for your response. I thought it was an error because other softwares don't have this issue. Calendly (the one I was using before Amelia), has no colon. When you don't use any punctuation, it stays how you left it, with nothing. You'd have to include the colon yourself. Which makes much more sense. You can see it in the picture attached here.
I was about to open a new ticket for this but I see there's one already here.
+1 for Jack's suggestion!
Looking forward to the devs removing those colons from the source code. 🙂
If you have any questions, let us know below!: Is there anything else we should know?:
I see where they were coming from but, unfortunately, colons don't really belong after terminal punctuation (i.e. . ? ! ) and custom fields often have questions or exclamations in their titles.
Hi, Daniel. I'm glad to see other people having the same issue. That seemed so obvious to me that I started to wonder whether I was the only one seeing the problem. Let's just hope they remove it and allow us to include colons if we so desire. Thanks!
I'm glad to inform you that our developers already took a look at this, and they will add a new logic in the future.
I can't say if we'll remove the colon all-in-all, so you get to chose if you're going to include a symbol; or if we'll add an option (like a slider) to remove the colon. There are a lot of users that are perfectly fine with this, so if we completely remove it, we may end up with a hundred tickets regarding why the change was made.
Our development team is working on this, and I hope they'll manage to resolve it by the next update. If not by then, then most likely the one after that. There are other priority tasks they are working on, so I cannot guarantee anything. The only thing I can guarantee is that they've accepted the task.
Hi, Piclauched. I tried to submit an issue on github. But I never got the email to confirm my account. I installed your upgraded version. This time the colons remaine untouched :/
When I add custom fields it includes a colon automatically after the label. The problem is that when I ask questions ending in question marks, the colon stays there, regardless. And of course, it shouldn't. Can you please look into this?
PS: I've already asked Marija in another ongoing ticket. I decided to open a new one as the subject is different.
Hello Jack
The colon is added programmatically, and changing it would require changing the code.
JS files are modified (minimized) in public version of plugin (in our development environment is accessible), but unfortunately I can not send you our source code because that is the policy of our company.
All those files that have extension .vue are compressed and minimized in JS files that is very hard and not recommended modifying. So in order to add some other features you can unminify the js and customize it.
You could probably do it by editing innerHTML element, and removing the colon from there, but that would require a custom JavaScript to run on the page, target each of the custom fields, and edit their content.
Please note that customization questions like this are not included in provided support, which only refers to advice, but you can explore stack overflow, and you may be able to find some useful tips there.
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, Aleksandar
It never even crossed my mind that I would have to edit files and fix that myself. That's not my responsibility. I find it extremely intriguing that you'd suggest a way for me to fix that problem, when it's your product's flaw. Maybe you deal with programmers here and you're used to saying things in their language. But I'm just a customer who bought your product and it has a problem.
Now, are you saying that this error will stay on the page and you won't fix it?
Thank you!
Hello Jack
That's not an error, that's the feature of the plugin. You're adding custom fields, and their description is ended in a colon. Exactly like "Type of call:" in the first step:
I can see that you rethought the custom fields, so they have more sense with a colon instead of a question mark.
The suggestion that this is something customers can choose will be forwarded to our development team, so they can work on it for one of our future updates, but at the moment it is considered a custom solution, which doesn't fall under included support for the plugin, so I can't help you with it.
If our developers find a workaround for you, I will share it with you.
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, Aleksandar.
Thank you for your response. I thought it was an error because other softwares don't have this issue. Calendly (the one I was using before Amelia), has no colon. When you don't use any punctuation, it stays how you left it, with nothing. You'd have to include the colon yourself. Which makes much more sense. You can see it in the picture attached here.
Yeah, I agree with you that it would be better if users had control over this.
I have forwarded the suggestion to our development team, and they said they will work on it for 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
I was about to open a new ticket for this but I see there's one already here.
+1 for Jack's suggestion!
Looking forward to the devs removing those colons from the source code. 🙂
If you have any questions, let us know below!:
Is there anything else we should know?:
I see where they were coming from but, unfortunately, colons don't really belong after terminal punctuation (i.e. . ? ! ) and custom fields often have questions or exclamations in their titles.
Hi, Daniel. I'm glad to see other people having the same issue. That seemed so obvious to me that I started to wonder whether I was the only one seeing the problem. Let's just hope they remove it and allow us to include colons if we so desire. Thanks!
Cheers,
Jack.
+1 for Jack's suggestion!
Hello again Jack, Daniel, Hasan.
I'm glad to inform you that our developers already took a look at this, and they will add a new logic in the future.
I can't say if we'll remove the colon all-in-all, so you get to chose if you're going to include a symbol; or if we'll add an option (like a slider) to remove the colon. There are a lot of users that are perfectly fine with this, so if we completely remove it, we may end up with a hundred tickets regarding why the change was made.
Our development team is working on this, and I hope they'll manage to resolve it by the next update. If not by then, then most likely the one after that. There are other priority tasks they are working on, so I cannot guarantee anything. The only thing I can guarantee is that they've accepted the task.
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
Dear All,
I am glad to share with you all to test this plugin, it helps to remove colons out of the box. Also some more feature to help with Amelia.
It can be download from
https://github.com/piclaunch/Lazy_Amelia
Download the .zip file to install the plugin.
Hope it helps you.
Regards,
Hello piclaunch
Thank you for sharing that with everyone!
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
Thank you, Piclauch!
Unfortunately it also took away the radio buttons. :/ I was so pleased to see someone had a fix :/
I guess I'll uninstall it for now and wait for your answer. :)
Cheers!
Hi Jack,
I have update the code to support radio button and other custom fields. Let me know how it goes now.
get update zip from Here on git hub.
You are welcome to report any issue here on github.
Regards,
Piclaunch
Hi, Piclauched. I tried to submit an issue on github. But I never got the email to confirm my account. I installed your upgraded version. This time the colons remaine untouched :/
My apologies here , please get the version now. Somehow it never got update with latest code.
get update zip from Here on git hub.
You are welcome to report any issue here on github.
Regards,
Piclaunch
Awesome! It's working.
Thank you so much :)