PHPCBF and PHPCS commands not working

[UVLabs]

I'm not sure whats wrong but running the commands do no work anymore. This worked fine before but I don't know when it stopped.

Trying to reference the phpcbf file does nothing. Checking for installed paths also does nothing:

I have checked if the files are executable and run: chmod +x vendor/bin/phpcbf but that didn't seem to make any difference.

None of the normal commands work..not even checking the version:

Any assistance in figuring out the issue is greatly appreciated.

Here is my composer file:

{
    "require-dev": {
        "dealerdirect/phpcodesniffer-composer-installer": "^1.0",
        "wp-coding-standards/wpcs": "^3.1"
    },
    "autoload":{
        "psr-4": {
            "Lpac_DPS\\" : "includes/"
        }
    },
    "require": {
        "freemius/wordpress-sdk": "^2.5",
        "nesbot/carbon": "^2.71"
    },
    "config": {
        "platform": {
            "php": "7.4.33"
        },
        "allow-plugins": {
            "dealerdirect/phpcodesniffer-composer-installer": true
        }
    },
    "scripts": {
        "lint" : "mkdir -p logs; vendor/bin/phpcs -s > ./logs/log.txt",
        "format": "vendor/bin/phpcbf -p",
        "dist":  "sh bin/dist.sh",
        "strauss": [
            "php bin/strauss.phar"
        ],
        "post-install-cmd": [
            "@strauss"
        ],
        "post-update-cmd": [
            "@strauss"
        ]
    },
    "extra": {
        "strauss": {
            "target_directory": "vendor-prefixed",
            "namespace_prefix": "SoaringLeads\\Chwazi\\",
            "classmap_prefix": "SoaringLeads_Chwazi",
            "constant_prefix": "CHWAZI_",
            "packages": [
                "nesbot/carbon"
            ],
            "update_call_sites": false,
            "override_autoload": {
            },
            "exclude_from_copy": {
                "packages": [
                ],
                "namespaces": [
                ],
                "file_patterns": [
                ]
            },
            "exclude_from_prefix": {
                "packages": [
                ],
                "namespaces": [
                ],
                "file_patterns": [
                ]
            },
            "namespace_replacement_patterns" : {
            },
            "delete_vendor_packages": false,
            "delete_vendor_files": false
        }
    }
}

[fredden]

I've been able to reproduce the non-output with the following composer.json content. If I don't include the freemius/wordpress-sdk package, then all works as expected.

{
    "require-dev": {
        "squizlabs/php_codesniffer": "3.11.2"
    },
    "require": {
        "freemius/wordpress-sdk": "2.10.1"
    }
}

At the top of start.php there's this code, which terminates the process.

	if ( ! defined( 'ABSPATH' ) ) {
		exit;
	}

This is being called with the following stack trace:

#0 vendor/composer/autoload_real.php(41): require()
#1 vendor/composer/autoload_real.php(45): {closure}()
#2 vendor/autoload.php(25): ComposerAutoloaderInit41bce37011465c3ade93ec528f45db4b::getLoader()
#3 vendor/squizlabs/php_codesniffer/autoload.php(82): include('...')
#4 vendor/squizlabs/php_codesniffer/bin/phpcs(13): PHP_CodeSniffer\Autoload::load()
#5 vendor/bin/phpcs(119): include('...')
#6 {main}

This commit seems to have introduced the bug by asking Composer to always load the start.php file when initiating the autoloader: Freemius/wordpress-sdk@770e2fc / Freemius/wordpress-sdk#756

[UVLabs]

Thanks for you reply. I tried going to the freemius lib inside the vendor folder and commented out the

if ( ! defined( 'ABSPATH' ) ) {
		exit;
}

At the top of start.php and then tried running phpcbf again and it still gave no output.

However, when I do remove the dependency altogether, phpcbf works just fine.

So it seems the issue is indeed Freemius but maybe deeper than simply that exit call...or maybe I'm missing something.

I'll submit a bug report to Freemius

[jrfnl]

Thanks @fredden for triaging this issue. I 100% concur with your analysis.

@UVLabs For when you report it to Freemius: the problem is the combination of the exit AND the file being in the Composer autoload - files directive in the composer.json file of the Freemius plugin. Files which are autoloaded like that should not contain this type of side-effects.

We've seen this issue before and as far as I can remember, it's always some WordPress plugin doing things wrong.
In most cases, changing the exit to return in the offending plugin will allow for getting round the problem, though to be fair, the plugin should not be auto-loading files this way in the first place, but that's another discussion.

[Edit]: You may also want to mention that Freemius' own CI is completely broken now as well (and has been since they merged that PR) as it runs into the same problem you were running into. All of their CI checks are currently silently exiting without running....

[jrfnl]

For the record: @UVLabs reported the issue upstream via Freemius/wordpress-sdk#780