XAMPP and PHPEd debugger

Problems with the Windows version of XAMPP, questions, comments, and anything related.

XAMPP and PHPEd debugger

Postby eclerkin » 06. July 2016 16:19

In an earlier version of XAMPP, WordPress by Bitnami would install in c:\xampp\htdocs folder and PHPEd would find it to properly build a debug workspace. The current version of XAMPP has a different folder layout and now WordPress installs in c:\xampp\apps\wordpress\blahblahblah which causes problems with the PHPEd Configuration Wizard since it's expecting to find WordPress in c:\xampp\htdocs based on PHPINFO. Consequently, PHPEd fails during the installation of their debugger.

If I move the "apps" folder down to c:\xampp\htdocs folder, will that work with the current version of XAMPP or will something else hiccup after the move? Where does http://localhost/wordpress on Windows get resolved with xampp - a config file? Maybe I need to un-install WordPress by Bitnami, download it directly from WordPress.org and manually install it on c:\xampp\htdocs.
eclerkin
 
Posts: 3
Joined: 06. July 2016 15:53
XAMPP version: 5.6.21-0
Operating System: Windows 10

Re: XAMPP and PHPEd debugger

Postby Altrea » 06. July 2016 16:43

AFAIK the Bitnami Apps for XAMPP were never installing to \xampp\htdocs\ they always used \xampp\apps\.
Why don't you use the default wordpress installer from the wordpress website? With that you can install wordpress whereever you want.
Moving an already installed webapplication will commonly fail.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 11935
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: XAMPP and PHPEd debugger

Postby eclerkin » 06. July 2016 16:52

Ok, thanks. I probably manually installed it on my laptop in c:\xampp\htdocs thinking it was the Bitnami WP installation. Should I un-install XAMPP completely and start over with XAMPP THEN manually install WP into c:\xampp\htdocs? I am wondering how localhost will get resolved with WP and Apache.
eclerkin
 
Posts: 3
Joined: 06. July 2016 15:53
XAMPP version: 5.6.21-0
Operating System: Windows 10

Re: XAMPP and PHPEd debugger

Postby Altrea » 06. July 2016 17:22

eclerkin wrote:Should I un-install XAMPP completely and start over with XAMPP THEN manually install WP into c:\xampp\htdocs?

It is often a good idea to start from scratch if you are feeling lost.

eclerkin wrote:I am wondering how localhost will get resolved with WP and Apache.

Apache has a default DocumentRoot Folder where it expects scripts. This is \xampp\htdocs\.
If you install wordpress from the Bitnami App it sets an Alias in the Apache configuration pointing to the wordpress folder in \xampp\apps\
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 11935
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64

Re: XAMPP and PHPEd debugger

Postby eclerkin » 06. July 2016 19:30

Ok, I see the include at the end of httpd.conf file and the re-direct to c:\xampp\apps\wordpress\htdocs in httpd-prefix.conf. If this is DocumentRoot in Apache then wouldn't it need to be removed for a WP install in c:\xampp\htdocs?
eclerkin
 
Posts: 3
Joined: 06. July 2016 15:53
XAMPP version: 5.6.21-0
Operating System: Windows 10

Re: XAMPP and PHPEd debugger

Postby Altrea » 06. July 2016 19:49

If you want to use the Name of the Alias, then yes the Alias needs to be removed.
The Wordpress App for XAMPP from Bitnami Uninstaller should remove this Alias too, but this will sometimes fail.
We don't provide any support via personal channels like PM, email, Skype, TeamViewer!

It's like porn for programmers 8)
User avatar
Altrea
AF Moderator
 
Posts: 11935
Joined: 17. August 2009 13:05
XAMPP version: several
Operating System: Windows 11 Pro x64


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 183 guests