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

[Translatable] After Bundle Upgrade: ReflectionException Property Namespace\MyBundle\Entity\CategoryTranslation::$id does not exist #154

Closed
giovkanata opened this issue Oct 20, 2014 · 15 comments
Labels
bug

Comments

@giovkanata
Copy link

@giovkanata giovkanata commented Oct 20, 2014

All worked as expected but after the upgrade:

  • Removing knplabs/doctrine-behaviors (dev-master b7083e9)
  • Installing knplabs/doctrine-behaviors (dev-master 2ff5031)

I get the error in the title.

What do I need to write in composer.json to do the downgrade?

PS: I use Standard Symfony 2.5.5 with upgraded components. What do I need to show to get you able to reproduce that error?

Thanks!

@kuczek

This comment has been minimized.

Copy link
Contributor

@kuczek kuczek commented Oct 20, 2014

i've the same problem (if this is a problem)

@giovkanata

This comment has been minimized.

Copy link
Author

@giovkanata giovkanata commented Oct 20, 2014

@kuczek do you know how to do the downgrade?

@giovkanata

This comment has been minimized.

Copy link
Author

@giovkanata giovkanata commented Oct 20, 2014

I downgraded the bundle to the previous version (from a backup) and everything works correctly again.

@kuczek

This comment has been minimized.

Copy link
Contributor

@kuczek kuczek commented Oct 20, 2014

@giovkanata Which version do you have now?

@giovkanata

This comment has been minimized.

Copy link
Author

@giovkanata giovkanata commented Oct 20, 2014

@kuczek dev-master b7083e9
PS: is the version that I had before the upgrade

@kuczek

This comment has been minimized.

Copy link
Contributor

@kuczek kuczek commented Oct 20, 2014

I think this exception should be thrown right now.

75e1187 changes old behavior to the current.

@docteurklein It's how it should work right now?

@docteurklein

This comment has been minimized.

Copy link
Contributor

@docteurklein docteurklein commented Oct 20, 2014

oops, that's definitely a regression. you can corce a specific commit in composer.json using #ade21f or something, while we fix this.

@giovkanata

This comment has been minimized.

Copy link
Author

@giovkanata giovkanata commented Oct 20, 2014

Ok thx!

@docteurklein

This comment has been minimized.

Copy link
Contributor

@docteurklein docteurklein commented Oct 20, 2014

another way is to define manually an id property, but not map it. this lib will map it to an auto id automatically

@jordigracia

This comment has been minimized.

Copy link

@jordigracia jordigracia commented Oct 27, 2014

I downgraded the budle to "knplabs/doctrine-behaviors": "dev-master#b7083e9" and works fine.
Symfony v 2.3.19

@smarques

This comment has been minimized.

Copy link

@smarques smarques commented Nov 1, 2014

same error here

@webspin

This comment has been minimized.

Copy link

@webspin webspin commented Feb 6, 2015

issue still present in dev-master...

@Einenlum Einenlum added the bug label Sep 14, 2017
@Einenlum

This comment has been minimized.

Copy link

@Einenlum Einenlum commented Sep 14, 2017

Do you still experience this issue in the last versions, or was it fixed by #158 ?

@giovkanata

This comment has been minimized.

Copy link
Author

@giovkanata giovkanata commented Nov 23, 2017

Sorry @Einenlum for the late reply but I was away for some time. The project from which I started this issue is finished long time ago (and now it's followed by others), but soon I should start another one using Symfony4.

@TomasVotruba

This comment has been minimized.

Copy link
Collaborator

@TomasVotruba TomasVotruba commented Dec 10, 2019

I'm going through the old issues/PRs and closing most of them so we can focus on now.
This one is missing any feedback or reasoning so I cannot deduce anything from it.

Thanks for you though, but closing for reasons above.

If the bug still remains, please send failing test case to verify it. Only with test we'll be albe to help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.