fix: GitHub auto-update installation issues v1.4.3
Compare
Sorry, something went wrong.
No results found
Plugin Slug & Identification:
- Use hardcoded 'errorvault-wordpress' slug instead of dirname()
- Add 'plugin' field: 'errorvault-wordpress/errorvault.php'
- Ensures WordPress properly identifies the plugin after update
Version Handling:
- Strip 'v' prefix from GitHub tags (v1.4.3 -> 1.4.3)
- Apply ltrim() in both check_for_update and plugin_info
- Fixes version comparison issues
After Install Improvements:
- Check if destination is already correct before renaming
- Better handling of both release asset and zipball formats
- Improved folder move logic with error checking
- Set destination_name for proper WordPress recognition
Debug Logging:
- Log release asset vs zipball usage
- Log version comparison (current -> new)
- Log folder renaming operations
- Log success/failure of move operations
- Helps troubleshoot installation issues
Plugin Info Fix:
- Use release asset URL instead of always using zipball
- Consistent with check_for_update behavior
- Better download experience
These fixes ensure the GitHub release auto-updater:
1. Properly identifies the plugin slug
2. Correctly compares versions
3. Successfully installs and activates updates
4. Handles both release assets and zipball fallbacks
5. Provides debug logging for troubleshooting