Hey there, Awesome Customers!
Just a heads up: We'll be taking a breather to celebrate International Workers' Day (May 1st and 2nd - Wednesday and Thursday) and Orthodox Easter from Good Friday (May 3rd) through Easter Monday (May 6th). So, from May 1st to May 6th, our team will be off enjoying some well-deserved downtime.
During this time, our customer support will be running on a smaller crew, but don't worry! We'll still be around to help with any urgent matters, though it might take us a bit longer than usual to get back to you.
We'll be back in action at full throttle on May 7th (Tuesday), ready to tackle your questions and requests with gusto!
In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find loads of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel). These gems might just have the answers you're looking for while we're kicking back.
Thanks a bunch for your understanding and support!
Catch you on the flip side!
Warm regards,
TMS
When my Gravity Form has the Rich Text Editor enabled, on the wpDataTables side, when adding or editing a record I cannot switch back and forth between 'Visual' and 'Text' on that column/field. Can you please help?
Actually, if the text editor was the same as it is when selecting 'HTML editor' as the Editor input type (which I'm not able to do with Gravity Forms wpDataTable), that would be sufficient.
You can see in the attached screenshots, that the Gravity Forms datatable text editor has only a few of the buttons/options... whereas the HTML editor has everything we are looking for. How can we made the Gravity Forms editor match the HTML editor?
Attached files: Screenshot 2023-05-24 180226 - Gravity Forms DT w Rich Text Editor.png
Screenshot 2023-05-24 180026 - HTML Editor input type.png
Hi, Brenda.
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
-
I am sorry to disappoint you, but at the moment, these are some of the limitations we currently have for the integration with Gravity Forms.
We have pointed out the limitations on this documentation.
I will just point out the two which are relevant for editing :
If you wish to see an improvement on this,
please feel free to search on our suggestions page,
to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there, and as more people vote, the feature will move higher on the priority list.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Kind Regards,
Miloš Jovanović
[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
Gravity Forms certainly does have a more robust editor but what I am referring to is not using gravity forms 'own forms' - I was able to get the HTML Editor input type desired by making the following change to your code:
**********************************************************
at line 103 of file /wp-content/plugins/wdt-gravity-integration/assets/js/gf_editing.js
change this:
if (modalBody.find('.wp-editor-area')) {
modalBody.find('.wp-editor-area').each(function() {
tinymce.execCommand('mceRemoveEditor', true, $(this).attr('id'));
tinymce.init({
selector: '#' + $(this).attr('id'),
menubar: false
});
});
}
to this:
if (modalBody.find('.wp-editor-area')) {
modalBody.find('.wp-editor-area').each(function() {
tinymce.execCommand('mceRemoveEditor', true, $(this).attr('id'));
tinymce.init({
selector: '#' + $(this).attr('id'),
menubar: false,
plugins: 'link image media lists hr colorpicker fullscreen textcolor code',
toolbar: 'undo redo formatselect bold italic underline strikethrough subscript superscript | alignleft aligncenter alignright alignjustify | bullist numlist outdent indent blockquote | hr fullscreen | link unlink image | forecolor backcolor removeformat | code'
});
});
}
**********************************************************
So seems to me this could easily be made standard in the plugin (as this would get overwritten when the plugin is updated).
Hi, Brenda.
Thank you very much for sharing this code workaround with us.
I am passing it to our developers, they will test this and they will do their best to add this to the Plugin's Core in one of the future updates.
Until they add it, as you correctly pointed out, this code edit needs to be done at each Update.
I can't say an exact ETA, but
you can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
Thanks again for this great suggestion.
Kind Regards,
Miloš Jovanović
[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