While working on a customised portal I encountered a problem with showing objects that have a field of type AttributeLinkedSet where the target class is an abstract base class, e.g. PhysicalDevice.
I was able to reproduce this behaviour with the attached minimal extension, where I just want a brick that shows all objects of class Brand.
The list ist shown properly, but whenever I klick one of the objects I end up with
Oops! An error has occured.
Cannot instantiate abstract class PhysicalDevice
And with 'log_level_min' => LogAPI::LEVEL_TRACE, in the configurations I get the following message in error.log
I did a fresh install of iTop version 3.1.0-2-11973 built on 2023-08-02 14:25:30 in "demo mode", and then installed my minimal extension attached here (only changes are in datamodel.sample-extension.xml).
How to reproduce
* Install iTop
* Install the attached extension
* Switch to the portal with user Admin
* Click on the Brick "Brands"
* Click on one of the shown brands
Right now I'm not sure if I'm doing something wrong or if there might be a problem in the code of iTop.
as I haven't seen any branch related to 7024, I assume this issue is in backlog and not being worked on currently?
Don't wanna pressure anyone, It's just about getting a rough idea at which date I might be able to move to 3.1 and how to plan my tasks (not) related on the move.
Cheers,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, your issue will be resolved when upgrading to iTop 3.2.0+.
The link you are refering to is the list of the regressions introduced during the development of the 3.2.0 versions that had to be solved before the final relese.
You'll find your ticket in the change log of the 3.2.0 here :)
Take care,
Guillaume
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While working on a customised portal I encountered a problem with showing objects that have a field of type
AttributeLinkedSet
where the target class is an abstract base class, e.g.PhysicalDevice
.I was able to reproduce this behaviour with the attached minimal extension, where I just want a brick that shows all objects of class
Brand
.The list ist shown properly, but whenever I klick one of the objects I end up with
And with
'log_level_min' => LogAPI::LEVEL_TRACE,
in the configurations I get the following message inerror.log
I did a fresh install of
iTop version 3.1.0-2-11973 built on 2023-08-02 14:25:30
in "demo mode", and then installed my minimal extension attached here (only changes are indatamodel.sample-extension.xml
).How to reproduce
* Install iTop
* Install the attached extension
* Switch to the portal with user
Admin
* Click on the Brick "Brands"
* Click on one of the shown brands
Right now I'm not sure if I'm doing something wrong or if there might be a problem in the code of iTop.
Hello Markus,
That's a very detailed explanation, thanks! We'll look into it.
Guillaume
Thanks for your swift reaction, Guillaume.
If you need more information, feel free to ask.
Dear Guillaume,
it has been a while.
Are there any news on this?
Hello Markus,
I wrote this message back then but never it send, sorry!
Bug is tracked in our internal bug tracker under N°7024.
I don't know when it will be fix, but it will be reviewed next week.
Take care,
Guillaume
Dear Guillaume,
I'll do the same thing from time to time ;).
Thanks for the update!
Dear Guillaume,
as I haven't seen any branch related to 7024, I assume this issue is in backlog and not being worked on currently?
Don't wanna pressure anyone, It's just about getting a rough idea at which date I might be able to move to 3.1 and how to plan my tasks (not) related on the move.
Cheers,
Markus
Hello,
We're not sure for now of the solution. The bug will be worked on on next 3.1.2 version, at least to evaluate and decide what to do.
Thx for the update, Pierre!
Dear all,
just to be on the safe side:
I've seen the commit message
and said commit is part of the branch
tags/3.2.0
.In addition I do not find any reference to my issue in https://www.itophub.io/wiki/page?id=3_2_0:release:beta-known-issues .
Can I expect that this will work as expected once I upgrade to 3.2.0 (or higher) ?
Cheers,
Markus
Hello Markus,
Yes, your issue will be resolved when upgrading to iTop 3.2.0+.
The link you are refering to is the list of the regressions introduced during the development of the 3.2.0 versions that had to be solved before the final relese.
You'll find your ticket in the change log of the 3.2.0 here :)
Take care,
Guillaume
Thanks!
Thanks!
Fixed in 3.2.0, released today.
Thanks for the info Romain!
I was finally able to look into it again, an the issue is fixed for me now.
Not sure how to set this thread to SOLVED though.
All the best
Markus