Hi @arysom, thank you for providing a patch. Our team is already working on the issue and the same will be fixed in the next release itself.
I will update here once the module is published. Thanks
Hi @gisele, my intention was not to ignore your comment or any of your insights on the issue at hand. I also appreciate you providing the relevant links and detailed information on the subject.
I will go through all the provided information(links as well as the detailed text) in order to get a better understanding. But before that, I will make the required changes to eradicate the complete feedback process from the module so that there is no export of the data during the entire process.
hi @apaderno @gisle, we have made the required changes in the 3.0.6 version of the module.
We have handled this in the module in the following manner:
1) Informing the people of what data will be sent if they choose to submit the feedback during uninstallation on that same form itself.
2) We have also added the option to avoid sending any data via the skip feedback option.
Let us know in case any further changes are required.
@Nathan, thank you for pointing out the issue. Please note that this has been handled & fixed in version 3.0.3. It would be great if you could also test once and confirm the same.
This issue has been fixed in 3.0.3
@z3cka, no, we haven't decided on which of the modules will be discontinued in the future
Hi @skutova.mir, thank you for pointing out the issue. I have made the said fixes and released an update of the module. As I am not able to reproduce the exact issue on my end, can you please test it out once just to confirm if the issue is resolved?
Hi @Shane, thanks for sharing the error trace. I just checked the code and it seems like there is an additional line before the php tag for the .install file. As I am not able to reproduce the issue on my environment, can you please test the latest module (version: 2.0.7) and let me know if the issue still persists.
Thanks in advance.
Hi @phonkala, I have made some changes to fix the issue in the latest version of the module (version: 2.0.6). Can you please test the latest version of the module and let me know if the issue still persists?
Also, if you do not wish to upgrade to the latest version of the module, please run the drush updb command and hopefully your issue will get resolved. I hope this helps.
Hi there, I just tried to reproduce the error using the steps you mentioned but everything seemed to be working fine on my end. Can you please install the latest version of the module(2.0.5) and test again? Please let me know whether the issue persists
Hi, sure, I will be happy to assist you.
Can you please drop an email at drupalsupport@xecurify.com so that I can set up a meeting and help you with the required configurations? Thanks.