You've already forked wc-composable-product
Fix WC_Settings_Page class loading issue (v1.1.1)
Critical bug fix for settings page initialization: - Changed hook from woocommerce_loaded to woocommerce_init - woocommerce_loaded fires before WC_Settings_Page is loaded - woocommerce_init ensures all WooCommerce core classes are available This resolves the "Class WC_Settings_Page not found" fatal error that prevented the plugin from activating successfully. Version bumped from 1.1.0 to 1.1.1 (patch release). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
13
CHANGELOG.md
13
CHANGELOG.md
@@ -5,6 +5,19 @@ All notable changes to this project will be documented in this file.
|
||||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
||||
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
||||
|
||||
## [1.1.1] - 2024-12-31
|
||||
|
||||
### Fixed
|
||||
|
||||
- Settings page initialization timing issue causing "Class WC_Settings_Page not found" error
|
||||
- Changed hook from `woocommerce_loaded` to `woocommerce_init` to ensure WC_Settings_Page class is available
|
||||
- Plugin now initializes after all WooCommerce core classes are loaded
|
||||
|
||||
### Technical
|
||||
|
||||
- Hook changed from `woocommerce_loaded` to `woocommerce_init` in wc-composable-product.php:65
|
||||
- `woocommerce_init` fires after WooCommerce has finished loading all its core classes including settings
|
||||
|
||||
## [1.1.0] - 2024-12-31
|
||||
|
||||
### Added
|
||||
|
||||
Reference in New Issue
Block a user