dbais
Forum Replies Created
-
I just encountered the same issue.
It turned out that the command I had created to run the server cron task was using an older version of PHP than WordPress itself was using.
Updating the PHP that cron was using resolved the issue.
Hope that’s useful
Forum: Plugins
In reply to: [The Events Calendar] PHP Fatal Error reported by cron after ugrade to v6.0.9Resolved
Forum: Plugins
In reply to: [The Events Calendar] PHP Fatal Error reported by cron after ugrade to v6.0.9This has been fixed following the update to v6.0.11
Thank you!
Forum: Plugins
In reply to: [The Events Calendar] PHP Fatal Error reported by cron after ugrade to v6.0.9Scheduled Actions is available.There’s a bunch of entries. The most recent is about 5 days ago. I don’t have the oldest alerts emails. So I can’t tell if the timing of the alerts starting corresponds to the last entry date in the log. It is roughly in the same timeframe though based on dates in this thread
Forum: Plugins
In reply to: [The Events Calendar] PHP Fatal Error reported by cron after ugrade to v6.0.9The site is running WordPress 6.1.1 with PHP 7.4.33. It uses a custom theme. I’ve just updated the plugin to v6.0.10. I’d not run the process to import events into the new format. It was reporting errors with some old events relating to them being recurring. I’ve now deleted those old messages and successfully run the process.
cron is now showing a different message: Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}
Forum: Plugins
In reply to: [FG Magento to WooCommerce] CMS Pages not importedI’ve rechecked this.
While it’s true that the AW Blog extension in Magento has been used to create 13 Blog posts which haven’t been imported for the reason you gave, the site has a further 32 Magento CMS pages which I would have expected to have been imported by your standard plugin.
Any idea why these weren’t imported?
Forum: Plugins
In reply to: [FG Magento to WooCommerce] CMS Pages not importedHere they are:
=== START test_database 2022-01-26 15:30:25 === Connected with success to the Magento database Magento data found: 1 CMS page 45 product categories 189 products [WARNING] Your Magento database contains several customers. You need the Premium version to import them. [WARNING] Your Magento database contains AW Blog data. You need the Premium version and the AW Blog add-on to import them. === END test_database 2022-01-26 15:30:26 === === START save 2022-01-26 15:31:10 === Settings saved === END save 2022-01-26 15:31:10 === === START import 2022-01-26 15:31:21 === Connected with success to the Magento database Magento data found: 1 CMS page 45 product categories 189 products [WARNING] Your Magento database contains several customers. You need the Premium version to import them. [WARNING] Your Magento database contains some custom order statuses. To import them, you need the WooCommerce Order Status Manager plugin and the Custom Order Statuses add-on. [WARNING] Your Magento database contains wish lists. You need the Premium version and the Wish Lists add-on to import them. [WARNING] Your Magento database contains AW Blog data. You need the Premium version and the AW Blog add-on to import them. Importing articles... 1 article imported Importing product categories... 45 product categories imported Importing products... 189 products imported 355 medias imported IMPORT COMPLETED === END import 2022-01-26 15:41:05 === ### BEGIN DEBUG INFO ### WordPress info: Plugin URL: https://delta-wp.local/wp-admin/admin.php?import=fgm2wc Site URL: https://delta-wp.local Home URL: https://delta-wp.local WP version: 5.9 WP Memory limit: 40M Multisite: no Permalink structure: /%category%/%postname%/ Media in year/month folders: yes Active theme: Twenty Twenty-Two 1.0 Active plugins: FG Magento to WooCommerce 3.23.0 Google Listings and Ads 1.10.0 Mailchimp for WooCommerce 2.5.4 WooCommerce 6.1.1 PHP info: PHP version: 7.4.12 Web server info: Apache/2.4.46 (Unix) OpenSSL/1.0.2u mod_fastcgi/mod_fastcgi-SNAP-0910052141 mod_wsgi/3.5 Python/2.7.13 mod_perl/2.0.11 Perl/v5.30.1 memory_limit: 256M max_execution_time: 7200 max_input_time: 60 post_max_size: 8M upload_max_filesize: 32M allow_url_fopen: 1 PDO: mysql, sqlite, pgsql MySQL info: MySQL version: 5.7.32 max_allowed_packet: 128.00 MB wait_timeout: 28800 Plugin info: FG Magento to WooCommerce 3.23.0 Add-ons: Options: automatic_empty: url: <DELETED FOR PRIVACY> hostname: localhost port: 3306 database: delta_mag01_import username: root password: *** prefix: skip_media: first_image: as_is_and_featured skip_thumbnails: import_external: import_duplicates: force_media_import: first_image_not_in_gallery: timeout: 20 price: without_tax sale_price: special stock_management: import_as_pages: logger_autorefresh: 1 ### END DEBUG INFO ###Forum: Plugins
In reply to: [Pods - Custom Content Types and Fields] Can’t disable Pods pluginI followed up on that and disabled the entry in required plugins in the theme.
Having done that I’ve been able to deactivate and delete the plugin.
So – problem solved
Forum: Plugins
In reply to: [Pods - Custom Content Types and Fields] Can’t disable Pods pluginThis is a standalone site and Pods isn’t network activated. (Not sure what that even means.)
As far as I know Pods has never been actually used in the site.
It may only be there because the theme recommended installation. If so could whatever triggered the recommendation also be block removal? And if so how do I override that?
I’ll get the demo link to you asap.
Meanwhile, now I’ve found the workaround of disabling the crop I’ll probably stick to that!
Thanks for your quick replies on this.
I am using a retina monitor.
I understand what you’re saying. But I’m not sure it explains why the images are fuzzy when the Image Crop is turned on and sharp when it’s turned off.
I’ll send you a demo link.
Forum: Plugins
In reply to: [WP Activity Log] AuditLog – Can’t use function return value in write contextThat has fixed the problem. Thanks.
If you wanted to retain the trim() you could use:
$trimmed = trim( $this->page_args->search_term );
$is_search_view = class_exists( ‘WSAL_SearchExtension’ ) && ( ! empty( $this->page_args->search_filters ) || ! empty( $trimmed ) );Forum: Plugins
In reply to: [WP Activity Log] AuditLog – Can’t use function return value in write contextAs I thought, it is an issue with line 459 of AuditLog.php where this bit of the if statement is triggering the error:
empty( trim( $this->page_args->search_term ) )
If I evaluate that and assign it to a variable and use that in the if statement instead, then it all works fine.
Forum: Plugins
In reply to: [WP Activity Log] AuditLog – Can’t use function return value in write contextInfo on its way.
Meanwhile in attempt to try to replicate the issue I ran a test on a development site which I updated to the latest versions of WordPress and all installed plugins.
WP Security Audit Log wasn’t activated on the dev site. After the updates were completed I attempted to activate the WP Security Audit Log plugin and had this error message displayed in WordPress:
Fatal error: Can’t use function return value in write context in <server path>/wp-content/plugins/wp-security-audit-log/classes/Views/AuditLog.php on line 459
Call Stack
# Time Memory Function Location
1 0.0019 412616 {main}( ) …/plugins.php:0
2 1.3972 84728896 plugin_sandbox_scrape( ) …/plugins.php:175
3 1.3994 85070568 include( ‘<server path>/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php’ ) …/plugin.php:2050
4 1.4661 90983200 WpSecurityAuditLog::GetInstance( ) …/wp-security-audit-log.php:1641
5 1.4661 90983416 WpSecurityAuditLog->__construct( ) …/wp-security-audit-log.php:158
6 1.4663 90986816 WpSecurityAuditLog->includes( ) …/wp-security-audit-log.php:169So that’s the same error I reported before – this time with a stack trace.
The dev environment runs the same version of PHP as the live site.
When I switched the dev site to use PHP 5.6.40 the plugin activated normally
That does seem to point towards something in the code at the location indicated which is incompatible with the older version of PHP that was introduced in a recent update of the plugin.
Forum: Plugins
In reply to: [WP Activity Log] AuditLog – Can’t use function return value in write contextSite is running PHP v5.4.45
Front end is working OK. But the back end was generating a 500 server error for all the URLs I tried. So I removed the wp-security-audit-log plugin folder and the back end is now working normally.