profile
viewpoint

HelloFax/dataducketl-fork 0

Our DataDuck 0.7.0 Fork

hellosign/logstash-reindexer 0

A framework for reindexing historic LogStash generated ElasticSearch snaphots. Most useful when preparing an archive for an ElasticSearch 1.x to 2.x upgrade, or 2.x to 5.x

imperialwicket/spinnaker-jib 0

Tiny project to demonstrate blue ocean pipelines and spinnaker

sysadmin1139/ConOnRails 0

An application for managing convention operations

sysadmin1139/oncall-handbook 0

Tips and tricks for getting through on-call

sysadmin1139/puppet-gluster 0

puppet module for gluster

sysadmin1139/puppet-influxdb 0

Manage Influxdb server using Puppet

sysadmin1139/puppetlabs-apache 0

Puppet Labs Apache module

sysadmin1139/spinnaker-jib 0

Tiny project to demonstrate blue ocean pipelines and spinnaker

sysadmin1139/wkhtmltopdf 0

Convert HTML to PDF using Webkit (QtWebKit)

issue commenthellosign/hellosign-php-sdk

Add ability to configure HTTP / Guzzle Client

Hi @algorozco. Yes, I saw that it was merged some time ago and we've been using it. Thanks for the follow-up!

nrutman

comment created time in 21 days

issue closedhellosign/hellosign-php-sdk

Unable to check 409 response status from getFiles

The API documentation mentions that calling signature_request/files/[requestid] may return 409 if the signed PDFs are not available yet.

There doesn't seem to be a way to get the status as client->getFiles() swallows up the guzzle response, and the rest call response is only the getBody() portion.

The closest I can think is to try

$client->rest->getStatus();

or

$client->checkStatus();

But both of these solutions are blocked by protected status.

closed time in 21 days

markkimsal

issue commenthellosign/hellosign-php-sdk

Unable to check 409 response status from getFiles

Hi @markkimsal

This is Hazem from API support.

Have you tried using getSignatureRequest function to get the current status for each signer. Also, we highly recommend user to take advantage of our callbacks and wait for the signature_request_all_signed event to POST before downloading the signed document using the Get Files endpoint. This callback event fires off once everyone has signed and the document is ready for download.

If you need any further help, please feel free to send a ticket to apisupport@hellosign.com.

markkimsal

comment created time in 21 days

issue commenthellosign/hellosign-php-sdk

Facebook Advert issue with SDK?

Hello,

The documentation directed me to post this on Github ... so I did.

The issue is resolved now, thank you.

Kind regards, Ian

On Fri, 6 Nov 2020 at 00:45, Ana notifications@github.com wrote:

Hi Ian,

Apologies we missed this before. For help with troubleshooting it works better if you contact to us at apisupport@hellosign.com. Could you please reach out there if you are still experiencing any issues?

API Support Team

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hellosign/hellosign-php-sdk/issues/94#issuecomment-722731730, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANUR6JTF7TVGZP7UHJDECRLSONBLPANCNFSM4JHJEPVQ .

IanMapp

comment created time in 22 days

PR closed hellosign/hellosign-php-sdk

Add setTimeout() method for setting the timeout for Guzzle HTTP requests (should also help with issue #61)

Before this PR, the timeout for Guzzle HTTP requests could not be set manually (the default timeout is hardcoded to 30 seconds in the constructor of the REST class). This PR allows setting the timeout via a new setTimout($seconds) method in the HelloSign\Client class. Also helpful for slower connections and/or handling larger files as described in issue #61.

Usage example:

$client = new HelloSign\Client("API_KEY");
$client->setTimeout(120); // This sets the timout to 120 seconds
+21 -0

2 comments

2 changed files

mr-nash

pr closed time in 22 days

pull request commenthellosign/hellosign-php-sdk

Add setTimeout() method for setting the timeout for Guzzle HTTP requests (should also help with issue #61)

This functionality should be achievable after having merged PR #89.

mr-nash

comment created time in 22 days

issue closedhellosign/hellosign-php-sdk

Add ability to configure HTTP / Guzzle Client

I am using the HelloSign SDK and realized it lacks the ability to send its requests through a web proxy. Since it utilizes Guzzle under the hood, this is easily achievable by accepting a set of Guzzle options at instantiation.

I have included a PR that does this (https://github.com/hellosign/hellosign-php-sdk/pull/89).

As an added benefit, this gives developers additional access to configure the underlying HTTP (Guzzle) client according to their use case. For example, I think this would also satisfy https://github.com/hellosign/hellosign-php-sdk/pull/65.

closed time in 22 days

nrutman

issue commenthellosign/hellosign-php-sdk

Add ability to configure HTTP / Guzzle Client

Hi Nate! Sorry we didn't get back to you before, PR #89 was merged some time ago. Please let us know if you are facing any issues.

API Support Team

nrutman

comment created time in 22 days

issue closedhellosign/hellosign-php-sdk

Facebook Advert issue with SDK?

Hello,

We deployed HS to one of our domains and the moment the new WordPress plugin was installed to the site, FaceBook 'disallowed' the domain for advertising on the basis that it breached their "community guidelines". They will not give us any additional information, but the moment the plugin was deleted we were able to get the domain approved again.

The only clue we have is that the use of Eval() can be considered suspicious and this statement appears in several files in the SDK.

Do you think this could be the issue? If so, is there any alternative?

Thanks, Ian

closed time in 22 days

IanMapp

issue commenthellosign/hellosign-php-sdk

Facebook Advert issue with SDK?

Hi Ian,

Apologies we missed this before. For help with troubleshooting it works better if you contact to us at apisupport@hellosign.com. Could you please reach out there if you are still experiencing any issues?

API Support Team

IanMapp

comment created time in 22 days

issue closedhellosign/hellosign-php-sdk

Add function deactivateAllowAddCCs

in the Template class the function deactivateAllowAddCCs is missing (as desctribed in the API reference guide: https://app.hellosign.com/api/reference#create_embedded_template_draft) Similar call to $templateRequest->disableAllowReassign(); and $templateRequest->disableAllowDecline();

closed time in 22 days

dimsamaras

issue openedhellosign/hellosign-php-sdk

Unable to check 409 response status from getFiles

The API documentation mentions that calling signature_request/files/[requestid] may return 409 if the signed PDFs are not available yet.

There doesn't seem to be a way to get the status as client->getFiles() swallows up the guzzle response, and the rest call response is only the getBody() portion.

The closest I can think is to try

$client->rest->getStatus();

or

$client->checkStatus();

But both of these solutions are blocked by protected status.

created time in 24 days

create barnchhellosign/hellosign-php-sdk

branch : query_string_support

created branch time in a month

push eventhellosign/hellosign-php-sdk

Westin Shafer

commit sha 7706a2022b6c61f879f50bb0991d06b1f883c7a3

Upgrades dependency for Guzzle to include ^7.0|^6.2

view details

Ana

commit sha 4fc357b737e5a9eeeec9a35183fbf46b9397611e

Merge pull request #107 from wshafer/v3 Upgrades dependency for Guzzle to use ^7.0|^6.2

view details

push time in a month

push eventhellosign/hellosign-php-sdk

Ana

commit sha 411f4a88e8cd0da0f6f8600ce1ef45093d132a45

Update Client.php

view details

push time in a month

push eventhellosign/hellosign-php-sdk

Ana

commit sha f00e511b2777f52730590a46f1f1201ff84cb2b7

Revert "Revert "Updated Client::getSignatureRequests() to accept page size, and search query""

view details

Ana

commit sha 65dfb50609f74e6ddb0339cd4d8ac5c88c6661cd

Merge pull request #110 from hellosign/revert-109-revert-93-v3 Revert "Revert "Updated Client::getSignatureRequests() to accept page size, and search query""

view details

push time in a month

PR opened hellosign/hellosign-php-sdk

Revert "Revert "Updated Client::getSignatureRequests() to accept page size, and search query""

Reverts hellosign/hellosign-php-sdk#109 (re-merging #93)

+8 -3

0 comment

1 changed file

pr created time in a month

create barnchhellosign/hellosign-php-sdk

branch : revert-109-revert-93-v3

created branch time in a month

push eventhellosign/hellosign-php-sdk

Ana

commit sha 6f3952ae13827523e6eef7b77350c9ac8ff0cd60

Revert "Updated Client::getSignatureRequests() to accept page size, and search query"

view details

Ana

commit sha 2430e329d8f322ebbef7d1624535d1b836a40a49

Merge pull request #109 from hellosign/revert-93-v3 Revert "Updated Client::getSignatureRequests() to accept page size, and search query"

view details

push time in a month

create barnchhellosign/hellosign-php-sdk

branch : revert-93-v3

created branch time in a month

push eventhellosign/hellosign-php-sdk

Eric Schmiedel

commit sha 55b0a4f312e3d4c5b2250deded01d37fe10c6a4e

Updated Client::getSignatureRequests() to accept page size, and search query

view details

Ana

commit sha 5771ed4b57d8d9637e9cc973232f607e9fed93bd

Merge pull request #93 from djhype/v3 Updated Client::getSignatureRequests() to accept page size, and search query

view details

push time in a month

PR merged hellosign/hellosign-php-sdk

Updated Client::getSignatureRequests() to accept page size, and search query

This should be backwards compatible with existing implementations. I can also add logic flows to only add query to the $params array if $query has a non-null value if that is desired. I can also change the docblock to use Integer instead of int if this will be a consistency concern.

+8 -3

2 comments

1 changed file

djhype

pr closed time in a month

issue openedhellosign/hellosign-php-sdk

Call out time_out error when the script is taking too long to process the request

Currently, if you passed a large file to generate a signature request, the timeout error that PHP enviroment calls out is getting logged in HS API dashoard as well as the callback event as the following: { "error": { "error_msg": "No client id provided", "error_name": "bad_request" } }

In this case, and unitl the fix is out. We recommend the following:

Split the file into smaller chunks so HelloSign can handle converting those files faster than one one big file. Increase your timeout limit in yourphp.ini file. Something like: Look for max_execution_time directive. ; Maximum execution time of each script, in seconds ; http://php.net/max-execution-time ; Note: This directive is hardcoded to 0 for the CLI SAPI max_execution_time = 30 Set the value for max_execution_time in seconds. max_execution_time = 300

Internal case ZD # 11387288

created time in 2 months

more