Skip to content
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.

Sign up for GitHub

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

Jump to bottom

PHP 8.2.15 removed FTP extension #39083

Closed
1 of 3 tasks
rafaelstz opened this issue Aug 21, 2024 · 8 comments · Fixed by #39084 · May be fixed by magento/magento-cloud-docker#367
Closed
1 of 3 tasks

PHP 8.2.15 removed FTP extension #39083

rafaelstz opened this issue Aug 21, 2024 · 8 comments · Fixed by #39084 · May be fixed by magento/magento-cloud-docker#367
Assignees
@rafaelstz
Labels
Area: Framework Component: Backend Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.7 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@rafaelstz
Copy link
Member

rafaelstz commented Aug 21, 2024 •
edited by github-jira-sync-bot
Loading

Preconditions and environment

  • Magento version >= 2.4.7
  • PHP >= 8.2.15
  • Configuring the FTP CSV it gives you the error below
details error :  Call to undefined function Magento\Framework\System\ftp_connect()

Steps to reproduce

Configure CSV import via FTP using admin panel.

Expected result

The connection is established, and we started working on importing the CSV via FTP.

Actual result

An exception is thrown, logging the error below.

details error :  Call to undefined function Magento\Framework\System\ftp_connect()

Additional information

No response

Release note

No response

Triage and priority

  • < ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • [ > Severity: S4 - Affects aesthetics, professional look and feel, "quality" or "usability".
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Aug 21, 2024

Hi @rafaelstz. 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:

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

@rafaelstz
Copy link
Member Author

@magento I am working on this

This was referenced Aug 21, 2024
Merged
Open
Merged
@engcom-Bravo engcom-Bravo added the Reported on 2.4.7 Indicates original Magento version for the Issue report. label Aug 22, 2024
@m2-community-project m2-community-project bot added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Aug 22, 2024
@engcom-Hotel engcom-Hotel moved this to Ready for Confirmation in Issue Confirmation and Triage Board Aug 26, 2024
@engcom-Bravo engcom-Bravo added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Aug 26, 2024
@engcom-November engcom-November self-assigned this Aug 29, 2024
@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Aug 29, 2024

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: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-November
Copy link
Contributor

Hello @rafaelstz,

Thank you for the report and collaboration!

This might be an issue if the vendor of the php does not include ftp as a extension by default, hence confirming the issue.

@engcom-November engcom-November added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: Backend Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Area: Framework labels Aug 29, 2024
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12857 is successfully created for this GitHub issue.

@m2-assistant M2 Assistant
Copy link

m2-assistant bot commented Aug 29, 2024

✅ 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.

@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Confirmed in Issue Confirmation and Triage Board Sep 2, 2024
@engcom-Bravo
Copy link
Contributor

Hello,

Internal team has started to work on it

Thanks.

@github-jira-sync-bot github-jira-sync-bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: dev in progress labels Oct 10, 2024
@m2-community-project m2-community-project bot added Progress: done and removed Progress: PR Created Indicates that Pull Request has been created to fix issue Progress: PR in progress labels Oct 19, 2024
@engcom-Bravo
Copy link
Contributor

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-12857 by the internal team
Related commits: https://github.com/search?q=repo%3Amagento%2Fmagento2+AC-12857-v2.0&type=commits

Based on the Jira ticket, the target version is 2.4.8-beta2.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafaelstz rafaelstz

Labels
Area: Framework Component: Backend Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.7 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Milestone
No milestone
4 participants
@rafaelstz @engcom-Bravo @engcom-November @github-jira-sync-bot