Closed craigh closed 9 years ago
Could this be caused by existing data (persisted in your database)?
I think the problem is that PostCalendar_Entity_EventCategory
extends Zikula_Doctrine2_Entity_EntityCategory
which needs to be changed to Zikula\Core\Doctrine\Entity\AbstractEntityCategory
.
This would be a BC problem then. Since it should still work.
I doubt that it is possible to have a Doctrine join to two different classes. So unless there is a volunteer for this issue I don't see a way to solve it.
Also I don't mind about a few bc breaks in a new major version. Avoiding all of these slows down development significantly and raises difficulty.
Also I don't mind about a few bc breaks in a new major version
I sincerely disagree, unless by "new version" you mean 2.0.0. Semver requires all breaking changes to occur only in major versions (e.g. 2.x.x). While Zikula has certainly almost never adhered to this principal, I think we should start. We should work diligently to avoid BC breaks as much as possible.
I agree in general. But introducing namespaces is more sweeping than simple functional changes, isn't it?
It certainly is. The Namespaced portions of the core are intended as either "silent" changes (non-Api breaking and completely BC) or part of a Forward Compatibility layer, such that anything that worked in 1.3 should still work with no changes.
Certainly a case could be made for naming 1.4 as 2.0 but that ship has long since sailed and there is no need to rehash that again. My priority is simply this: maintain BC as much as humanly possible until 2.0.0.
Sure. But I still doubt that this issue can be fixed with ease. Maybe it would be possible to let Zikula_Doctrine2_Entity_EntityCategory
inherit from Zikula\Core\Doctrine\Entity\AbstractEntityCategory
so the type hint would be satisfied. Can't imagine the side effects of such a change though.
agreed. it will be a challenge. I have already worked on most of the category stuff and solved it with regard to BC issues. I will take a look at this when I have time.
I just tested this again and did not have the problem anymore!
This might be an edge case. I hooked Dizkus to PC and got this.