We use WP CLI to install our plugins for our self-hosted WP instances, but ever since disable-gutenberg 3.0+, the plugin throws a fatal error whenever we try to activate it via the command line:
PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function "disable_gutenberg_dismiss_notice_activate" not found or invalid function name in /.../wp-includes/class-wp-hook.php:310I believe this is because the file defining the function disable_gutenberg_dismiss_notice_activate (in inc/settings-reset.php) is being required only if is_admin() is true. This explains how we’re able to activate the plugin on the WP backend, but not via the CLI!
We’re able to replicate this on a fresh WP install with no other plugins and the default themes:
1. wp plugin install disable-gutenberg will successfully install the plugin.
2. wp plugin activate disable-gutenberg will cause the fatal error.
3. Activating the plugin in the backend works without any problems!
I was able to successfully activate the plugin with WP CLI when I moved disable-gutenberg.php:100 out of the is_admin() check.
Thanks!
]]>I just upgraded to 3.0 and I get this error when generating the static files:
[2023-07-18 21:43:47] Error: (1) Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in /var/www/html/wp-content/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php:271
Stack trace:
#0 /var/www/html/wp-content/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php(271): explode('\n', Array)
#1 /var/www/html/wp-content/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php(61): Simply_Static\Fetch_Urls_Task->find_excludable(Object(Simply_Static\Page))
#2 /var/www/html/wp-content/plugins/simply-static/src/class-ss-archive-creation-job.php(142): Simply_Static\Fetch_Urls_Task->perform()
#3 /var/www/html/wp-content/plugins/simply-static/vendor/a5hleyrich/wp-background-processing/classes/wp-background-process.php(514): Simply_Static\Archive_Creation_Job->task('fetch_urls')
#4 /var/www/html/wp-content/plugins/simply-static/vendor/a5hleyrich/wp-background-processing/classes/wp-background-process.php(335): WP_Background_Process->handle()
#5 /var/www/html/wp-includes/class-wp-hook.php(308): WP_Background_Process->maybe_handle('')
#6 /var/www/html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#7 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#8 /var/www/html/wp-admin/admin-ajax.php(203): do_action('wp_ajax_nopriv_...')
#9 {main}
thrown in /var/www/html/wp-content/plugins/simply-static/src/tasks/class-ss-fetch-urls-task.php on line 271
Thank you,
]]>Cleantalk is now using sanitize_textarea_field() function which does not work in WordPress prior to version 4.7.0
If your site goes down due to this, rolling back to 5.176, or removing Cleantalk will get you back up.
]]>Migrating Payments 0 % [>
] 0:00 / 0:00Fatal error: Uncaught Error: The script tried to modify a property on an incomplete object. Please ensure that the class definition "Wpil_Model_Link" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in /home/adambox/public_html/wp-includes/formatting.php:5010
Stack trace:
#0 /home/adambox/public_html/wp-includes/formatting.php(5005): map_deep(Object(__PHP_Incomplete_Class), 'stripslashes_fr...')
#1 /home/adambox/public_html/wp-includes/formatting.php(2799): map_deep(Array, 'stripslashes_fr...')
#2 /home/adambox/public_html/wp-includes/formatting.php(5634): stripslashes_deep(Array)
#3 /home/adambox/public_html/wp-includes/meta.php(53): wp_unslash(Array)
#4 /home/adambox/public_html/wp-content/plugins/easy-digital-downloads/includes/orders/functions/meta.php(30): add_metadata('edd_order', 236650, 'wpil_links_inbo...', Array, false)
#5 /home/adambox/public_html/wp-content/plugins/easy-digital-downloads/includes/admin/upgrades/v3/class-data-migrator.php(1295): edd_add_order_meta(236650, 'wpil_links_inbo...', Array)
#6 /home/adambox/public_html/wp-content/plugins/easy-digital-downloads/includes/class-edd-cli.php(1339): EDD\Admin\Upgrades\v3\Data_Migrator::orders(Object(stdClass))
#7 /home/adambox/public_html/wp-content/plugins/easy-digital-downloads/includes/class-edd-cli.php(833): EDD_CLI->migrate_payments(Array, Array)
#8 [internal function]: EDD_CLI->v30_migration(Array, Array)
#9 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func(Array, Array, Array)
#10 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array)
#11 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func(Object(Closure), Array, Array)
#12 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(417): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#13 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(440): WP_CLI\Runner->run_command(Array, Array)
#14 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1237): WP_CLI\Runner->run_command_and_exit()
#15 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#16 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#17 phar:///usr/local/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
#18 phar:///usr/local/bin/wp/php/boot-phar.php(11): include('phar:///usr/loc...')
#19 /usr/local/bin/wp(4): include('phar:///usr/loc...')
#20 {main}
thrown in /home/adambox/public_html/wp-includes/formatting.php on line 5010
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
WordPress version 6.0.1
PHP version 8.1
We have spent the last few weeks reading through many of your honest thoughts and reviews, and now have a better understanding of your frustrations at the change in ownership and the effect it’s had on your managed sites.
Before we dive into the specifics, we would like to note that the current banner (v3.0) is and will remain free to use indefinitely. The plugin contains all of the pre-existing features found in v2.4 in addition to enhancements such as domain scanning, automated categorization of cookies, and prior script blocking.
With that in mind, we would like to address the major frustrations seen across the forum:
1. Version 2.4 Consent Banner
The version from the previous developers (v2.4) that many of you had installed, was deprecated and no longer being supported by the time Termly assumed ownership. What this means, is that despite the banner existing on your websites, legally it is invalid for protecting you and your visitors.
It was and continues to no longer be compliant under GDPR (EU), ePrivacy Directive (EU), CCPA (California), and broader data regulations around the world which can be updated multiple times per year.
2. Page View Limitations
We hear your frustrations about the 100 visitor limit that we had originally imposed on our free plan and recognize that we should have revised our free tier before updating the plugin. To address this, we have increased the limit of consent banner views on our free tier to better reflect your needs.
3. Subscription Costs
For each visitor that interacts with your banner, their consent records must be tracked, stored, and updated on our servers so that you stay compliant with global data regulations. This means that every banner costs us some amount to maintain. We believe that the value of a managed product is the peace of mind knowing that we are constantly working to uphold the protection of your site.
That said, our free version is always available and with no limits to how long you may stay on it. Our intention is to protect all our customers regardless if they’ve paid for additional functionalities.
Looking ahead
Should you prefer to stay on the previous version (2.4), we understand and refer you to [this post] that describes the rollback process. However, we do advise against this, as indicated earlier the v2.4 consent banner does not meet the requirements for a business to comply with GDPR and other legislation.
We hope you’ll give Termly a try as we continue to develop a robust platform for peace of mind when it comes to legal compliance. We are committed to global data privacy and have hired some of the best in-house experts to keep your consent banners, legal policies, and feature sets updated to the latest regulations around the world.
Should you have additional questions or concerns about the product or us, we invite you to check out our FAQ and chat with our team at [email protected]. We will continue to monitor the situation in these support threads as well.
Thank you,
Termly
.blog #main,
.archive #main {
display: flex;
flex-wrap: wrap;
margin-left: -20px;
}
.blog .site-main article,
.archive .site-main article {
width: calc(50% - 20px);
margin-left: 20px;
}
.blog .inside-article,
.archive .inside-article {
height: 100%;
box-sizing: border-box;
}Code provided by Tom himself in this topic: https://www.ads-software.com/support/topic/why-grid-layout-is-premium/
Could you help me make it like the previous version, featured image above and title below?
]]>