Fatal error: Class 'DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions' not found

[karolymarton]

Dear Devs,

Composer can't load the subject class.
Please generate separate php files per namespaces/classes in under proper directory path.

<?php
require 'vendor/autoload.php';

$options = new DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions();
// results: Fatal error: Uncaught Error: Class 'DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions' not found in ...

The class in the file src/Api/EnvelopesApi.php instead of src/Api/EnvelopesApi/ListStatusChangesOptions.php regarding to its namespace.
Relating docs to your psr-4 composer setting: http://www.php-fig.org/psr/psr-4

Best regards,
Karoly

[theBull]

after the require statement, try:

use DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions;

and then replace:
$options = new DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions();
to:
$options = new ListStatusChangesOptions();

[karolymarton]

Dear @theBull,
Have you tried this? Is it work for you?

I made the steps in the readme but got the same fatal error:

1. composer require docusign/esign-client
2. create a test.php with content

<?php
require 'vendor/autoload.php';
use DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions;
$options = new ListStatusChangesOptions();

I receive these messages:
PHP 5.6.19: Fatal error: Class 'DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions' not found in bug.php on line 4
PHP 7.1.2: Fatal error: Uncaught Error: Class 'DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions' not found in bug.php:4 Stack trace: #0 {main} thrown in bug.php on line 4

[gsnavin]

@mdesign83 Please use the following and it should work. You can find working example in the unit test cases. Hope that helps.
$options = new \DocuSign\eSign\Api\EnvelopesApi\ListStatusChangesOptions();

[karolymarton]

The main problem is the generated php source is not PSR-4 compatible:
http://www.php-fig.org/psr/psr-4

The subdirectory name MUST match the case of the sub-namespace names.

But neither EnvelopesApi directory exists, nor ListStatusChangesOptions is a separate file.

If I split EnvelopesApi.php file to separate classes in EnvelopesApi directory, everything is fine.

[moromete]

The problem is still there. Please split the classes in separate files.

[yohio]

The issue still persists.

[alxvgt]

I see this issue is already closed but i encountered the same problem with an integration in Symfony.

Attempted to load class "ListTemplatesOptions" from namespace "DocuSign\eSign\Api\TemplatesApi".
Did you forget a "use" statement for another namespace?

Here is my code block :

        $options = new \DocuSign\eSign\Api\TemplatesApi\ListTemplatesOptions();
        $options->setInclude(DocuSignClient::OPTION_CUSTOM_FIELDS);

        $dsTemplateApi = new \DocuSign\eSign\Api\TemplatesApi($this->docuSignClient);
        $templates = $dsTemplateApi->listTemplates($this->docuSignClient->getAccountId(), $options);

It seems that the psr4 autoload rules is not respected. The filename need to be the same than the class name as the path need to match the namespace.
@gsnavin Could you reopen this issue ?

[alxvgt]

A workaround can be used if you edit your composer.json as shown beelow. You can add a "classmap" entry to generate an additional autoload mapping.

    "autoload": {
        "psr-4": {
            "App\\": "src/"
        },
        "classmap": [
            "vendor/docusign/esign-client/src"
        ]
    },

[adrienfr]

@LarryKlugerDS is it possible to re-open this issue or should we create another one?

The issue is still here, psr-4 autoload is not respected in DocuSign\eSign\Api\TemplatesApi.php and DocuSign\eSign\Api\EnvelopesApi.php, there should be only one file for each class.

[LarryKlugerDS]

@adrienfr -- Thank you for your comment. I've re-opened the issue and notified the product manager. He'll work with our engineering group on the issue.

[hcker2000]

I also just ran into this issue just now. Any updates on this?

[adrienfr]

@LarryKlugerDS any news regarding this issue?

Because of the current behavior, we can't use the API to re-send an envelope and have to manually do this through our Docusign account, not very time effective :/

[adrienfr]

@harsharahul, could we please have your input on this issue?