[MAGNOLIA-4745] When uploading image to the component, image name is incorrectly used as a title of parent component Created: 18/Dec/12  Updated: 08/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.5.7
Fix Version/s: 4.5.8

Type: Bug Priority: Neutral
Reporter: Jan Christian Haddorp Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

http://demo.magnolia-cms.com/demo-project.html


Attachments: PNG File home_props.png     Zip Archive info.zip     PNG File intro.png    
Issue Links:
causality
dependency
relation
is related to MGNLDMS-260 Move setting of 'title' from info.mag... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When uploading a logo image (no DMS image) then the image name is used as headline.
Even when changing the headline text it is reset to the image name.

Can be reproduced on the STK test instance.



 Comments   
Comment by Leo Lozes [ 15/Jan/13 ]

We just spent 3h with this.

It seems like quality department did not do a great job on this update.
It's a shame because it's the first time that a "small" update is so painful, previously all the 4.4 updates we did worked great.

We just spent two days migrating our test environment facing problems, and this one is blocking, we can't update the production environment (the processed JS thing was fixable, this is not).

Please release a correction (4.5.8?) as soon as possible.

Comment by Roman Kovařík [ 15/Jan/13 ]

Hello Leo,
you can avoid this issue manually by adding fixed class to your WEB-INF folder. Extract attached info.zip into your apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/classes folder. The resulting structure of folders will be WEB-INF/classes/info/magnolia/module/admininterface/SaveHandlerImpl.class.

Best regards,
Roman

Comment by Antti Hietala [ 16/Jan/13 ]

Just adding that this bug is not limited to the page properties and logo. It also occurs in the intro area (stkSectionIntro, stkArticleIntro etc).

Comment by Jan Haderka [ 25/Jan/13 ]

@Antti, yeah it would happen anywhere where there is DMS image used.

Comment by Jan Haderka [ 25/Jan/13 ]

Since it's DMS specific, shouldn't this be solved in info.magnolia.module.dms.DocumentDialog only?

Comment by Jan Haderka [ 07/Feb/13 ]

Why do you make save handler protected? There should be no need to break encapsulation and expose it like this, or if there is one, it should be described in the issue itself.

Comment by Roman Kovařík [ 07/Feb/13 ]

There is currently no need to have save handler protected, this change was reverted.

Generated at Mon Feb 12 03:58:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.