We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The class EventExecutionService try to access method getModuleName() on a null value returned by method getModule() by model Event.
getModuleName()
getModule()
Expected behaviour
No exception should be triggered.
To Reproduce
Used versions: TYPO3: v12.4.20 Extension version: 7f2542c (@dev-fix/downloaded-temp-filename)
Additional context
The exception is triggered in class EventExecutionService at line 535
crossmedia_fourallportal/Classes/Service/EventExecutionService.php
Line 535 in 7f2542c
The model Event defines the return value of method getModule() as of type Module or null.
crossmedia_fourallportal/Classes/Domain/Model/Event.php
Line 115 in 7f2542c
Since the return value of null is valid, this should take into account, when work with the result.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The class EventExecutionService try to access method
getModuleName()
on a null value returned by methodgetModule()
by model Event.Expected behaviour
No exception should be triggered.
To Reproduce
Used versions:
TYPO3: v12.4.20
Extension version: 7f2542c (@dev-fix/downloaded-temp-filename)
Additional context
The exception is triggered in class EventExecutionService at line 535
crossmedia_fourallportal/Classes/Service/EventExecutionService.php
Line 535 in 7f2542c
The model Event defines the return value of method
getModule()
as of type Module or null.crossmedia_fourallportal/Classes/Domain/Model/Event.php
Line 115 in 7f2542c
Since the return value of null is valid, this should take into account, when work with the result.
The text was updated successfully, but these errors were encountered: