-
Notifications
You must be signed in to change notification settings - Fork 125
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
String could not be parsed as XML #113
Comments
@J-Mose some help ? |
Try run |
I had the same error. The problem was that two commands used the same shortcut. In my case it was "-s", used by PageBundle/Command/CloneSiteCommand, and FrameworkBundle/Console/Application. Good luck |
The bundle internally run the native Symfony command If you have some deprecated command definition in your project, deprecated warning will turn the XML parsing into an error. See https://github.com/symfony/symfony/blob/3.4/UPGRADE-3.4.md#httpkernel for more informations about how to fix it in your project. If you can't fix the deprecation warning (command in an external bundle for example), you can silence it by excluding the event channel in the console handler.
|
php bin/console list --format=xml - dont throw error, but i still get String could not be parsed as XML |
See what fixed it for me here: #133 (comment) |
Symfony 3.4
/command-scheduler/detail/new
After i try to add first scheduled command.
`
AppKernel:
new JMose\CommandSchedulerBundle\JMoseCommandSchedulerBundle(),
Routing:
Config:
Composer:
"jmose/command-scheduler-bundle": "2.0.0",
The text was updated successfully, but these errors were encountered: