active-directory-integration2
active-directory-integration2 copied to clipboard
Can't include platform_check.php
Hello,
We may be doing things unconventionally but, we have most of our site versioned controlled by git.
Therefore, core, plugins and themes are in the git project for the site.
It looks like there's a .gitignore file in /wp-content/plugins/next-active-directory-integration/vendor/ that is ignoring key files that are being required by the /wp-content/plugins/next-active-directory-integration/vendor/composer/autoload_real.php
Please see how the file platform_check.php file is ultimately being called by the root index file of your plugin.
This means then when we deploy and pull our changes on to the production server, a whole branch of files are not there in production and we have to re-download and install the plugin from the repo.
[user@host][/var/www/html/wp-content/plugins/next-active-directory-integration][ master ] [19] > grep -ir 'platform_check.php' * vendor/composer/platform_check.php:// platform_check.php @generated by Composer vendor/composer/autoload_real.php: require DIR . '/platform_check.php';
[user@host][/var/www/html/wp-content/plugins/next-active-directory-integration][ master ] [20] > grep -ir 'autoload_real.php' * vendor/composer/autoload_real.php:// autoload_real.php @generated by Composer vendor/autoload.php:require_once DIR . '/composer/autoload_real.php';
[user@host][/var/www/html/wp-content/plugins/next-active-directory-integration][ master ] [21] > grep -ir 'vendor/autoload.php' * index.php:require_once(dirname(FILE)."/vendor/autoload.php");
Would it be possible the .gitignore file is removed before you send the plugin to wordpress.org?
Thank you for your consideration on this issue.
Jonathan Perlman
@jpurpleman Would removing the /vendor/.gitignore file be enough or do you also need the /.gitignore file to be removed?
With 3.0.0, the vendor no longer has any .gitignore file in it. adLDAP has been moved.
@jpurpleman Please check out one of the 3.0 release canidates and comment on this issue if the problem still exists.