Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot get it working on Sylius v1.1.x #71

Open
stefandoorn opened this issue Jun 1, 2018 · 6 comments
Open

Cannot get it working on Sylius v1.1.x #71

stefandoorn opened this issue Jun 1, 2018 · 6 comments

Comments

@stefandoorn
Copy link
Contributor

@michalmarcinkowski I have a weird error that I didn't have on Sylius 1.0.x. Have been researching it, but can't get a clear clue on why it errors yet.. :(

        W: > Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::prepareDeploymentTarget
        W: PHP Fatal error:  Uncaught Doctrine\Common\Persistence\Mapping\MappingException: File mapping drivers must have a valid directory path, however the given path [/app/vendor/lakion/cms-plugin/src/Resources/config/doctrine/model] seems to be incorrect! in /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/MappingException.php:61
        W: Stack trace:
        W: #0 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/SymfonyFileLocator.php(174): Doctrine\Common\Persistence\Mapping\MappingException::fileMappingDriversRequireConfiguredDirectoryPath('[/app/vendor/la...')
        W: #1 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/FileDriver.php(151): Doctrine\Common\Persistence\Mapping\Driver\SymfonyFileLocator->getAllClassNames(NULL)
        W: #2 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/MappingDriverChain.php(128): Doctrine\Common\Persistence\Mapping\Driver\FileDriver->getAllClassNames()
        W: #3 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMe in /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/MappingException.php on line 61
        
        Fatal error: Uncaught Doctrine\Common\Persistence\Mapping\MappingException: File mapping drivers must have a valid directory path, however the given path [/app/vendor/lakion/cms-plugin/src/Resources/config/doctrine/model] seems to be incorrect! in /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/MappingException.php:61
        Stack trace:
        #0 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/SymfonyFileLocator.php(174): Doctrine\Common\Persistence\Mapping\MappingException::fileMappingDriversRequireConfiguredDirectoryPath('[/app/vendor/la...')
        #1 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/FileDriver.php(151): Doctrine\Common\Persistence\Mapping\Driver\SymfonyFileLocator->getAllClassNames(NULL)
        #2 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/Driver/MappingDriverChain.php(128): Doctrine\Common\Persistence\Mapping\Driver\FileDriver->getAllClassNames()
        #3 /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/AbstractClassMe in /app/vendor/doctrine/common/lib/Doctrine/Common/Persistence/Mapping/MappingException.php on line 61

cc @pamil

@stefandoorn
Copy link
Contributor Author

I get this fixed by adding an empty /vendor/lakion/cms-plugin/src/Resources/config/doctrine/model folder & an empty /vendor/lakion/cms-plugin/src/Entity.

But, that seems a rather ugly fix to me..

@michalmarcinkowski
Copy link
Member

michalmarcinkowski commented Jun 1, 2018

Hi @stefandoorn, we're not going to support or further develop this plugin, but maybe @pamil have a clue what can be wrong. The recommended CMS plugin is https://github.com/BitBagCommerce/SyliusCmsPlugin.

However if you still want/need to use it I'm fine with donating the repository or just giving you a write access 😉

@stefandoorn
Copy link
Contributor Author

I'm ok with getting write access for some simple maintenance (but won't be taking over lead or whatsoever), if we in the meanwhile deprecate the plugin on Packagist + make it clear from the README. I'm not sure about it, but maybe even good to release a new beta version that is restricted to Sylius 1.0 version and that will be the final official release?

@michalmarcinkowski
Copy link
Member

I don't think many people use this package, so it depends on your preference. Granted you a write access, let me know if you need anything more from me.

@stefandoorn
Copy link
Contributor Author

Great, thanks. Would you be ok with deprecating it on packagist?

@michalmarcinkowski
Copy link
Member

Done 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants