Skip to content

Latest commit

 

History

History
105 lines (71 loc) · 2.97 KB

File metadata and controls

105 lines (71 loc) · 2.97 KB

Troubleshooting Guide

This guide covers common issues you might encounter when using Pxp. Each issue has its own detailed documentation page.

Quick Navigation

🔒 Security & Permissions

⚙️ Installation & Setup

🔧 Operation Issues


Most Common Issues

1. PowerShell Execution Policy Error

Symptoms:

pxp : File C:\Program Files (x86)\Pxp\pxp.ps1 cannot be loaded. The file is not digitally signed.

Quick Fix:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Unblock-File "C:\Program Files (x86)\Pxp\pxp.ps1"

➡️ Full solution guide


2. Command Not Found in Git Bash

Symptoms:

$ pxp
bash: pxp: command not found

Quick Fix: Use PowerShell or CMD instead, or add bash alias:

pxp() {
    powershell.exe -ExecutionPolicy Bypass -File "C:/Program Files (x86)/Pxp/pxp.ps1" "$@"
}

➡️ Full solution guide


3. Permission Denied When Installing

Symptoms: Access denied errors during pxp install

Quick Fix: Run PowerShell as Administrator

➡️ Full solution guide


Getting Help

If you're still experiencing issues after checking the guides above:

  1. Check the README.md for usage instructions
  2. Verify your XAMPP installation is at C:\xampp
  3. Run pxp whereami to verify installation paths
  4. Open an issue on GitHub with:
    • The exact error message
    • Output of pxp whereami
    • Output of Get-ExecutionPolicy -List (if PowerShell issue)
    • Your Windows version

Diagnostic Commands

Run these commands to gather diagnostic information:

# Check Pxp installation
pxp whereami

# Check PHP versions
pxp list

# Check PowerShell execution policy
Get-ExecutionPolicy -List

# Check if running as administrator
([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)

Related Resources