Change default transport to 'null' which does not require any dependencies after install #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In Magento 2.3.4 version, It is giving below error on bin/magento run: Unknown transport: "" Please let me know what may be the issue? |
|
@rjshnautiyal, I have no idea. You probably should take a debugger and figure it out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right after installation, any console command shows an exception (not only enqueue's, just
php bin/magentowould be enough):It's incorrect behavior after module installation, especially in case you didn't want to use AMQP at all.
That's why I'm adding a null transport which could be declared without any dependencies and could be switched to a real one when its configuration would be provided and dependencies are installed.