-
Notifications
You must be signed in to change notification settings - Fork 49
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
Fix get mime type #55
Conversation
@Progi1984 We need to revert my change where I modify the compatibility scope else QA will not be able to test on Also we need to provide QA a specific scenario to observe the issue so they can compare before/after the PR |
@matks Revert the compability scope. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR approved 👍 ready to go to QA but we need to find a failure scenario for QA, so they can assert that "with v5.0.0 it fails and with (future) v5.0.1 it works"
@Progi1984 I get this error: |
I have collected a reproductible scenario for QA to be able to observe and explore the bug :
by
This will now use blockreassurance as a Widget and not like a Hook.
This should be fixed by this PR |
I am sorry I dont understand this. It does not seem related to this PR, is it ? |
I found that the issue was introduced here: 37d0fb1#diff-e6316994746d2ce5be44c53e7d2527c3R190 ImageManager::getMimeType doesnt receive correct file location because str_replace returns wrong result then PS_BASE_URI = '/'. Probably it should be registered as new issue. |
@matks |
Is this a 1.7.6 shop ? |
Yes |
Thanks @sarahdib |
Hi @Progi1984 and @PierreRambaud, This bug has been fixed a few months ago, targeted for version 5.1.0... but the current version is still 5.0.0. Thank you |
@matks I have a problem with blockreassurance as well. I changed to {widget h = 'displayReassurance'}, saved the file, refreshed the cache and received a message (the one before) ContextErrorException |
@Progi1984 and when the solution? |
We need a fix. |
Hello everyone, there is a huge overload of work on teams right now and many other important items requiring focus which is why v5.1.0 is not out yet. However you can use the code from
Hello @KamikStudio look at my PR #60 it might help you. I unfortunately don't have the time to continue working on it and there was a feedback from QA I could not process. You can pick up my work and even submit it as your own if you want to push the topic forward. |
How to test ?
See "failure scenario" described at the bottom of this PR: #55 (comment)