Community
Participate
Working Groups
Due to the problem in the UI, updating Root 1.0.0 to 1.0.1 results in Bogus 1.0.1 being disabled. An attempt to enable optional feature Bogus 1.0.1 fails with a strange message that XYZ 1.0.0 feature cannot be loaded ??
See the original problem 22685.
The UI portion of the problem is in the new activity constraint that does not allow optional children to be enabled if none of their parents are enabled. Two calls to obtain feature from the feature reference were made without testing if the feature reference is optional. For missing optional feature (a valid case), core exception was allowed to pass. The fix was to add an inner try/catch block when asking for a feature. In the catch block, feature reference is tested if it is optional. If yes, exception is ignored and the feature is skipped. Otherwise, the exception is rethrown (exception cannot be allowed for non-optional children). The fix has been tested and it appears to solve the problem in this bug.
fixed