Fix unserialization error when saving dataflow advanced profile. #1484
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (*)
For advanced profile,
gui_data
in tabledataflow_profile
is alwaysnull
. So, in_afterload()
,magento-lts/app/code/core/Mage/Dataflow/Model/Profile.php
Lines 81 to 95 in 0e2f81d
gui_data
is set to empty string.Now, in
_afterSave()
, we havemagento-lts/app/code/core/Mage/Dataflow/Model/Profile.php
Lines 147 to 157 in 0e2f81d
It will try to unserialize the empty string
gui_data
and throw the following:which is logged in ./var/log/exception.log
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)