Open Nuranto opened 5 months ago
Hi @Nuranto. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
Hi @engcom-Delta. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. Hello @Nuranto,
Thank you for the report and collaboration!
Tried to verify this on 2.4.7, but the issue is not reproducible. Created a UI listing without filter element, moved the column to another position, and the bookmark is being saved. Please take a look at the screeshot below:
Here I have moved the content column to first position, on page refresh the new configuration is retained.
Please find the custom module used to reproduce this, and let us know if we are missing anything. I38722V.zip
Thank you.
Can you check the mui/bookmark/save
xhr response code ? Is it 200 or 500 ?
mui/bookmark/save
xhr code is 200
Alright, I can reproduce the issue with your module on two distinct environments, there must be an extra condition, but I don't know which one.
I encountered the same error after updating an existing 2.4.6 project to 2.4.7. It seems that updating the ui_bookmark table does not work always as expected.
I removed the records in that table for my admin account, and after this action: the sales grid was working just fine.
(I did not have time to investigate this further, but perhaps it may give you some clue to the origin of this issue ?)
Hello @ekomurz, Thank you for the input.
We were able to reproduce this issue after updating 2.4.6 instance to 2.4.7. After updating to 2.4.7, rearranged columns are saved with error code 500.
Please take a look at the screenshot below:
And here is the exception message:
"exception":"[object] (Exception(code: 0): Warning: Undefined array key \"filters\" in <magentoInstance>/vendor/magento/module-ui/Controller/Adminhtml/Bookmark/Save.php on line 250 at <magentoInstance>/vendor/magento/framework/App/ErrorHandler.php:62)"} []
This issue is reproduced using the custom module attached here.
Hence confirming the issue.
Thank you.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12062 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
:x: You don't have permission to export this issue.
maybe fix with https://github.com/magento/magento2/pull/38784
Is there any work around for this currently?
Issue present on Magento 2.4.7-p1. I'm looking for a fix as well.
For now, I extended the bookmark save file
<preference for="Magento\Ui\Controller\Adminhtml\Bookmark\Save" type="Vendor\Module\Controller\Adminhtml\Bookmark\Save" />
And in extended file, changed code at line#250 onwards,
if ($existingConfig && $currentConfig) {
/*
* Default Magento code commented out
if ($existingConfig['filters'] === $currentConfig['filters']
&& $existingConfig['positions'] !== $currentConfig['positions']
*/
//Below check added
if ( (isset($existingConfig['filters']) && isset($currentConfig['filters']))
&& ($existingConfig['filters'] === $currentConfig['filters'])
&& ($existingConfig['positions'] !== $currentConfig['positions'])
//e.o. Below code added
) {
$bookmarkConfig['views'][$bookmark->getIdentifier()]['data'] = $data[self::CURRENT_IDENTIFIER];
$bookmark->setConfig($this->serializer->serialize($bookmarkConfig));
$this->bookmarkRepository->save($bookmark);
}
}
This fixed my problem.
+1 Also got
Warning: Undefined array key \"positions\" in vendor/magento/module-ui/Controller/Adminhtml/Bookmark/Save.php on line 251
Magento 2.4.7-p3
Preconditions and environment
Steps to reproduce
Expected result
Bookmark is saved
Actual result
500 error :
Exception #0 (Exception): Warning: Undefined array key "filters" in /var/www/html/vendor/magento/module-ui/Controller/Adminhtml/Bookmark/Save.php on line 250
Additional information
No response
Release note
No response
Triage and priority