Open
Description
Preconditions (*)
- Magento 2.3.3
Steps to reproduce (*)
- Login into the admin panel
- Go to Stores - Settings - Configuration.
- Open tab Catalog - Catalog. Fieldset "Product Image Placeholders".
- Select the placeholder image for field "Base"
- Click to button "Save"
You can try another setting with type "file"
Expected result (*)
Error message: Invalid parameter given. A valid $fileId[tmp_name] is expected.
Actual result (*)
- File uploaded and the configuration saved without errors
Issue reason
The reason for this issue is additional validation - function validateFileId
In this function we have check is uploaded file located in "correnct" tmp dicartory.
sys_get_temp_dir() get folder /tmp
$_FILES["file"]["tmp_name"] located in folder /chroot/home/tmp/xxxxxxx
Nexcess support said: "This actually makes sense, because /tmp is a symbolic link to /chroot/home/tmp on our servers."
Possible fixes
- [Correct way] Configure upload_tmp_dir to an allowed folder:
- "var/tmp" (or another based on sys_get_temp_dir() value)
- "<magento_root>/pub/media"
- "<magento_root>/var"
- "<magento_root>/var/tmp"
- "<magento_root>/pub/media/upload"
But it can be not so easy (impossible). For example, we have issue on Nexcess server. Server support responce:
sys_get_temp_dir: /tmp
$_FILES["file"]["tmp_name"]: /chroot/home/tmp/phpPEOxFn
This actually makes sense, because /tmp is a symbolic link to /chroot/home/tmp on our servers.
Metadata
Metadata
Assignees
Labels
Gate 2 Passed. Manual verification of the issue description passedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 1 Passed. Automatic verification of issue format passedMay be fixed according to the position in the backlog.Indicates original Magento version for the Issue report.The issue has been reproduced on latest 2.4-develop branchAffects non-critical data or functionality and does not force users to employ a workaround.Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Type
Projects
Milestone
Relationships
Participants
Activity
m2-assistant commentedon Nov 29, 2019
Hi @OleksiyOleksiyovych. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.3-develop instance- upcoming 2.3.x releaseFor more details, please, review the Magento Contributor Assistant documentation.
@OleksiyOleksiyovych do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
omaxmo commentedon Nov 29, 2019
@magento give me 2.3-develop instance
magento-engcom-team commentedon Nov 29, 2019
Hi @omaxmo. Thank you for your request. I'm working on Magento 2.3-develop instance for you
magento-engcom-team commentedon Nov 29, 2019
Hi @omaxmo, here is your Magento instance.
Admin access: https://i-25835-2-3-develop.instances.magento-community.engineering/admin
Login:
adminPassword:123123qInstance will be terminated in up to 3 hours.
OleksiyOleksiyovych commentedon Nov 29, 2019
I can not reproduce it on vanilla Magento instance which Magneto provides to test, but it's reproducible on vanilla Magento on other servers (for example, Nexcess).
Can someone provide steps for server configuration?
m2-assistant commentedon Nov 29, 2019
Hi @engcom-Charlie. 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: 👇
1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the labelIssue: Format is validwill be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is validappears.2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Descriptionlabel to the issue by yourself.3. Add
Component: XXXXXlabel(s) to the ticket, indicating the components it may be related to.4. Verify that the issue is reproducible on
2.3-developbranchDetails
- Add the comment@magento give me 2.3-develop instanceto deploy test instance on Magento infrastructure.- If the issue is reproducible on
2.3-developbranch, please, add the labelReproduced on 2.3.x.- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
5. Add label
Issue: Confirmedonce verification is complete.6. Make sure that automatic system confirms that report has been added to the backlog.
magento-engcom-team commentedon Nov 29, 2019
✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets
MC-29272were createdIssue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
45 remaining items
github-jira-sync-bot commentedon Jan 19, 2023
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s):
Reproduced on 2.4.x,^Area:.*Once all required labels are present, please add
Issue: Confirmedlabel again.github-jira-sync-bot commentedon Jan 19, 2023
✅ Jira issue https://jira.corp.adobe.com/browse/AC-7733 is successfully created for this GitHub issue.
m2-assistant commentedon Jan 19, 2023
✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.