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

Notice: Trying to access array offset on value of type null #339

Closed
davidmpaz opened this issue Oct 12, 2020 · 3 comments
Closed

Notice: Trying to access array offset on value of type null #339

davidmpaz opened this issue Oct 12, 2020 · 3 comments
Assignees
Labels

Comments

@davidmpaz
Copy link
Contributor

davidmpaz commented Oct 12, 2020

Hello,

thanks for taking care of this project.

Describe the bug

It seems SolidInvoice is using a version with buggy behaviour of doctrine/annotations see doctrine/annotations#273 this same bug is also the root cause of #326

in DocParser.php line 1002
at DocParser->Identifier()in DocParser.php line 687
at DocParser->Annotation()in DocParser.php line 663
at DocParser->Annotations()in DocParser.php line 354
at DocParser->parse('/** * @Orm\Table(name="security_token") * @Orm\Entity */', 'class SolidInvoice\PaymentBundle\Entity\SecurityToken')in AnnotationReader.php line 405
at AnnotationReader->collectParsingMetadata(object(ReflectionClass))in AnnotationReader.php line 338
at AnnotationReader->getClassImports(object(ReflectionClass))in AnnotationReader.php line 218

To Reproduce
After install i tried to update invoices view files to solve #338.
After visiting invoice route i get the layout but no invoice block rendered.
After setting SOLIDINVOICE_DEBUG=1, the exception is shown.

Expected behaviour
Changes in templates are shown without dependencies problems

Desktop (please complete the following information):

  • OS: ubuntu 18.04
  • php 7.4

Additional context
Changes are only aesthetics. I am not changing any important functionality, only displaying other variables in templates in titles and headers.

thanks in advance and best regards,
David

@pierredup
Copy link
Member

Thanks, @davidmpaz, but this should already be fixed in the master branch. Which branch are you using when you get this error?

@davidmpaz
Copy link
Contributor Author

Hi, thanks for answering. I was using the release tag v2.0.4. I will try master today evening. I will provide feedback then.

@davidmpaz
Copy link
Contributor Author

Hi, you were right. I clone the master branch and the problems is gone. More likely that the linked issue in this thread can be closed also.

Thanks
Best regards,
David

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

No branches or pull requests

2 participants