-
-
Notifications
You must be signed in to change notification settings - Fork 129
[WIP] Compatibility with Wordpress 6.7.1 #335
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
base: master
Are you sure you want to change the base?
Conversation
|
@copilot still working? |
Co-authored-by: benbalter <[email protected]>
Yes, I'm still working on this issue. I've just implemented two important changes to address the compatibility issue with WordPress 6.7.1:
These changes should resolve the timeout issues reported in the original issue. You can see the implementation in commit cded724. Warning Firewall rules blocked me from connecting to one or more addressesI tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot still working? |
Yes, I'm continuing to work on this issue. I've already addressed the main compatibility issues by adding I'm now looking at additional ways to optimize the export process for larger sites to ensure reliable performance with WordPress 6.7.1. Would you like me to implement any additional changes beyond what's already done? |
|
@copilot can you fix the failing tests? |
Co-authored-by: benbalter <[email protected]>
I've fixed the failing tests by improving the Warning Firewall rules blocked me from connecting to one or more addressesI tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot still working? |
Yes, I'm continuing to work on this issue. I've addressed the main compatibility issues with WordPress 6.7.1 through two key changes in commits cded724 and 8461571: (1) adding timeout prevention to the export function that doesn't interfere with tests, and (2) updating plugin metadata to explicitly mark 6.7.1 compatibility. The PR is now ready for review unless you'd like me to make additional improvements. Warning Firewall rules blocked me from connecting to one or more addressesI tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot still working? |
Yes, I've completed all the planned tasks to fix the WordPress 6.7.1 compatibility issue. The changes include adding a PHP timeout prevention mechanism via |
|
@copilot still working? |
I've completed all the necessary changes for WordPress 6.7.1 compatibility. The PR includes proper PHP timeout prevention with set_time_limit(0) that only runs outside test environments (commit 8461571), updated plugin metadata (commit cded724), and fixes for all PHPCS issues (commits 6475608 and 42ac494). All code now passes syntax validation and the PR is ready for review. |
|
@copilot still working? |
I've completed all the tasks for WordPress 6.7.1 compatibility. The PR includes PHP timeout prevention via set_time_limit(0) that works only outside test environments (commit 8461571), updated plugin metadata to explicitly list WordPress 6.7.1 compatibility (commit cded724), and all PHPCS style issues have been fixed (commits 6475608 and 42ac494). All code now passes syntax validation and the PR is ready for review. |
|
@copilot still working? |
Yes, I've completed all the planned tasks for WordPress 6.7.1 compatibility. The changes include PHP timeout prevention via set_time_limit(0) that only runs outside test environments (commit 8461571), updated plugin metadata to explicitly list WordPress 6.7.1 compatibility (commit cded724), and fixes for all PHPCS style issues (commits 6475608 and 42ac494). All code now passes syntax validation and the PR is ready for final review. |
|
@copilot fix failing tests |
Co-authored-by: benbalter <[email protected]>
Fixed the failing tests by converting test-timeout.php to a proper PHPUnit test class that extends WP_UnitTestCase. The file was being picked up by PHPUnit but wasn't structured correctly. See commit b5e6f2b. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot merge in |
Co-authored-by: benbalter <[email protected]>
Merged origin/master into copilot/fix-333 and resolved conflicts in vendor/composer files. The conflicts were in auto-generated Composer autoload files, which I resolved by regenerating them with |
|
@copilot merge in |
Co-authored-by: benbalter <[email protected]>
Merged origin/master into copilot/fix-333 and resolved conflicts. Key changes include updating plugin version to 3.0.1 and fixing deprecated rand_str() calls in tests (replaced with wp_generate_password()). The conflicts in vendor/composer files were resolved by regenerating them with composer dump-autoload. All PHP syntax checks pass. See commit 6718fe5. |
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.