OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

Forums OroCRM OroCRM – Installation/Technical Issues or Problems Property Oro\Bundle\ContactBundle\Entity\Contact::$picture does not exist

This topic contains 6 replies, has 2 voices, and was last updated by Andrey Yatsenko Andrey Yatsenko 2 weeks, 4 days ago.

  • Creator
    Topic
  • #40918

    Kacper
    Participant

    I have a clean installation on docker an I have an issue with ContactBundle.

    I tried to add the $picture to Contact and everything went well.. but why ORO needs it?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Author
    Replies
  • #40920
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi Kacper,

    How have you added the picture property to the Contact entity? I’m asking because it can be done from UI and also there are several ways to do this on the code level.

    #40932

    Kacper
    Participant

    I don’t remember any time I add it.. I can’t locate the place in the code so it must be database.. may I undo it somehow?

    #40933
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi Kacper,
    If you added it directly to the database, then just delete the field manually.
    Tables that are mapped to entities should not have any extra field that are not described in the code.

    #40934

    Kacper
    Participant

    Hello Andrey, thank you for your response. Where can I change it? Do you mean the oro_entity_config table? I can’t use the app, login to admin etc. because I see this error everywhere.

    #40935

    Kacper
    Participant

    Andrey, I’ve checked that, installed clean oro and when I tried to deserialize the oro_entity_config table I can find picture.. I can find it in the entity management too and the website is works fine.

    I’ve get back to my project, I still have the same problem, I have nothing like ‘picture’ in my commits.. any idea how to fix that? :)

    #40937
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    If it’s an existing field that has correct metadata, then the issue could be in the loading of metadata. First, try to remove the cache manually with the rm -rf command and warm it up again to make sure it’s not corrupted. Also running oro:platform:update command could help to fix broken metadata, please try to run it as well.
    After, please check the code changes that you have made after the last time you have a working website. There should not be work with an entity class or doctrine related services like an entity manager before the metadata were loaded, in a place like schema migrations or using of an entity class in a dependency injection compiler pass etc.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No