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.

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

PHPStorm Xdebug configuration Server "Name" #282

Open
smccafferty opened this issue Apr 19, 2021 · 0 comments · May be fixed by #771
Open

PHPStorm Xdebug configuration Server "Name" #282

smccafferty opened this issue Apr 19, 2021 · 0 comments · May be fixed by #771
Assignees
Labels
developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now
Milestone

Comments

@smccafferty
Copy link

When performing the setup to use the zero config debugging of PHPStorm we should make a note that the server name "must match" the host name.

Recently when I was reconfiguring a project to use the zero configuration debugging, after an upgrade to Altis 6, Xdebug stopped working due to the name not using the exact host name. The current docs mention that the name should be the same as the host name but it should be explicit that it needs to match. This probably would have not been an issue on a new setup but was something I glanced over since it was working prior to the upgrade.

@roborourke roborourke added the should have Should be done, medium priority for now label Apr 28, 2021
@yumito yumito removed the cross-team label Nov 23, 2021
@missjwo missjwo added the developer advocacy Developer Advocacy related tasks label Dec 16, 2024
@missjwo missjwo added this to the Altis v22 milestone Dec 16, 2024
@mikelittle mikelittle linked a pull request Dec 18, 2024 that will close this issue
@mikelittle mikelittle self-assigned this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants