## Blocks: GroupDocs Signature

block_groupdocs_signature
Maintained by Marketplace Team
GroupDocs Signature plugin for Moodle lets you embed documents into your website and invite your clients, colleagues and partners to sign them electronically, directly from their browsers.
8
5
Moodle 1.9

If you need to have a document signed, you don’t need to go through the trouble of faxing or mailing it to your partner any more. GroupDocs Signature service lets you collect signatures online.

All you need to do is to upload the document to your GroupDocs account and create fields that should be filled by the recipients, like Name, Initials, Date, etc. Then let the GroupDocs Signature plugin embed the document into your Moodle website. After that your partners will be able to view and sign the document directly on your website with a usual web browser. No more downloading, printing, scanning and sending documents back and forth.

What is most important, every signature obtained through GroupDocs Signature plugin will be absolutely legally binding, just like a conventional manual signature on a printed document.

### Contributors

• Fri, May 17, 2013, 9:35 PM
Please ping us with whot is wrong with this file or please change his status
With best regards GroupDocs Marketplace team
• Mon, May 20, 2013, 1:57 PM
Hi Marketplace Team,
from the trace that Anthony has put in his comment, i can see it is a moodle 2.4 installation (m24). The one that version 2013120600 supports. Please set your debug mode to developer to see notices. To see the notices, install with moodle 2.4 minimum requirements.

I've also noticed that the bug tracker url is incorrect. It is the same link as the repository url. It needs to be the url that will be looked at for any issues that will allow its maintenance in future.

Looking at the repository url, it is impossible to look at the source code. The repository contains a zip of the source files it seems instead of the source files themselves.

optional_param() and required_param() are in lib/moodlelib.php and its a good security practise to use those instead of directly accessing the $_SERVER ( or$_POST or $_GET) variable. This security issue is a blocker to approving this entry. I would recommend participating in the moodle.org/forums and asking for opinions and questions there for more feedback on your plugin(s) if you haven't already to get a better feel for moodle coding standards. • Wed, May 22, 2013, 2:38 PM Hi Aparup Banerjee, We have fixed all issues. PLease review. Also we do not directly accessing to the$_POST, we use strip_tags(stripslashes(trim($_POST()))); to validate POST variable. With best regards GroupDocs Marketplace team. • Mon, Jul 1, 2013, 10:52 AM Thanks for your work on fixing things up and sorry for the delayed response as I was on holiday. A couple of things that would help me continue reviewing the plugin. First, I had asked about the posibility of renaming the Github.com repository to moodle-block_groupdocs_signature. This is optional but recommended. Second, I would encourage you to use optional_param and required_param for validating user input. You can read about these in the comments for the function which is defined in lib/moodlelib.php. It's really pretty straight forward but if you have questions just let me know. Also, if you could make sure to tag the download versions with the version of Moodle that they are designed to work for that would be very help. I'm currently running Ubuntu 13.04 with the standard LAMP settings. I turn debugging on to show ALL errors so it could be that you did not have debugging on. In any case, I am going to mark this as needing more work at least until we get the download versions specifiying for what version of Moodle they are intended for. Please do not hesitate to let me know if there is anything I can do to be supportive of your efforts. Peace - Anthony • Mon, Jul 1, 2013, 6:51 PM Hi Anthony, we have some standarts in repos naming, and we had not any issues with other plugins before. So we would like to leave the repo's name as is. But if it will be requred, we will be able to rename the repo according to requirements. Also we changed from$_POST to optional_param and required_param. For version issue we fixed version in version.php file. Please review.
• Wed, Jul 3, 2013, 7:25 AM
No worries about the Github repository name. I will review the code but noticed that the latest versions added on July 1st are still not indicating for which version of Moodle they are intended. Could you please provide that when adding the versions. Peace - Anthony
• Wed, Jul 3, 2013, 1:36 PM
Hi Anthony, we have fixed version issue. Please review
• Fri, Jul 5, 2013, 5:16 AM
Thanks for updating the versions. I have removed the 2.0 and 2.1 from the latest version as there was a conflict with the $plugin->requires variable. In any case, I still see the use of POST but these can be easily removed. For example, in the instance_config_save function you declare the default value for$height and then check if there is a post and if there is a height variable submitted in that post. All of this can be handled simply by declaring the $height = optional_param('height', '650', PARAM_INT). These variables and the use of optional_param and required_param occur first (like initializing the variables). Then you do not need to check for POST being empty or not. If height was supplied the value of the$height variable will be what was provided. If not, it will be the default. There seems to be a discrepancy of whether you want height to be 600 or 650. We are getting close, let's just finish getting rid of these references to $_POST before we approve this. Peace - Anthony • Fri, Jul 5, 2013, 6:22 PM Hi Anthony, we fixed all your notices, please review • Wed, Jul 17, 2013, 12:18 PM Thanks for your continued work. You really do not need the checks on$height and \$width since you have declared the default value in the optional_param statement. I'm testing the install now. Peace - Anthony
• Wed, Jul 17, 2013, 12:38 PM
Note, I was not able to test the actual functionality of this block without having access to the service; however, I give the benefit of the doubt to companies since you have a vested interested in making sure it works for your clients. As such, I am going to approve this now that the previously mentioned issues have been resolved. Many thanks for your patience while working through this process. Peace - Anthony
• Wed, Jul 17, 2013, 12:44 PM
While approving, I received the following notice from AMOS: No updatable strings found in the package. Maybe it is not the latest version or the plugin is misconfigured. I am presuming this is because of the unnecessary /lang/en/block_simplehtml.php file. Go ahead and remove and then let's try approving it again. I've marked it as needing more work until we get rid of that unneeded file. Peace - Anthony
• Wed, Jul 17, 2013, 2:32 PM
We removed /lang/en/block_simplehtml.php also if you can please delete all plugin packages except 2013070609 and 2013070512 all rest packages are with version mistake
With best regardes GroupDOcs MArketplace team
• Mon, Jul 29, 2013, 10:28 AM
I've hidden the rest of the packages. You can also hide or show them. Please verify then send us a message to delete the hidden ones.
• Wed, Dec 31, 2014, 9:58 AM
Hi Anthony thanks for the great article!

We've been using the WP E-Signature Wordpress plugin by ApproveMe to sign our documents for a while and loving it!

It has a UETA/ESIGN compliant document signing technology like Docusign or Adobe EchoSign but for WordPress.
http://www.approveme.me/wp-digital-e-signature/
Have you heard of it?