DaveWP196

The problem is not fixed in so far as every time you release a new version of WooCommerce, I keep finding the error is being reintroduced.

How do I ensure you integrate a version of the ActionScheduler into your code?

Is ActionScheduler part of the WooCommerce core product suite as it is in the packages folder in WooCommerce? See GitHub – woocommerce/action-scheduler: A scalable, traceable job queue for background processing large queues of tasks in WordPress. Specifically designed for distribution in WordPress plugins (and themes) – no server access required.

The code I reported an error is located in this generic module, and I merely included a reference to the MemCached Object plugin to provide a bit more context to the report.

1. It is my custom theme. I do use a number of jQuery libraries (including accordion, contextMenu, UI, slickgrid).
2. I have checked at original logic does work with the Twenty Twenty One Theme.
3. Placing a breakpoint on line 56 and looking at the DOM environment, I can see that the query-monitor-main block has not been loaded, but it is loaded when the window.load event is triggered. As the Query Monitor HTML code is served after the </html> statement, I’m not sure of the logic used to move the block into the DOM either at bottom of the page or into the dashboard area at the top of the screen. Is this a CSS defined movement?
4. This said, the change I have proposed does ensure the code on lines 51 and after line 56 does not run until the page has finished loading into the DOM and any associated CSS changes have completed.

BTW – I’m using Bing on windows 11

• This reply was modified 1 year, 9 months ago by DaveWP196.
• This reply was modified 1 year, 9 months ago by DaveWP196.

I have fixed this issue by changing line 5808 in the aioseop_class.php file to test if $aioseop_options[‘aiosp_license_key’] is set. I’m not sure if this variable is only set if there is a licence key.

I believe this is a coding issue in that line 16 reads:

DebugEcho(“pop count: $response);

However, $response is an array, and this line should be rewritten as

DebugEcho(“pop count: $response[0]);

I discovered this problem when I run the WordPress environment with the global debug mode switched on.

Warning, I have found that using the template file in https://pastebin.com/Sd39h993 and attempting to access the page https://mysite/enhanced%20category/category results in a infinite loop.

I can’t precisely remember what was done to fix the problem, but it was definitely linked to uploading images; thus it was quiet easy to reproduce. I think the problem was due to a library version compatibility issue in the ISP’s configuration of applications it offered on its hosting platform (but I don’t know the precise details of the solution; they never told me as I’m using a shared platform).

The other approach was a “masking” option whereby a cron job was created to delete the core dumps on a daily basis to get rid of the “running out of space issue”. We switched off this solution once they worked out the library compatibility problem.

It is just that I noticed that I stopped receiving the backups. I think it must have been linked to installing an upgraded version or copying a large folder to the system but I’ve explicitly excluding this folder from being included in the backup.

The key issue is that the activity log was always showing that the backups were running correctly, it is just I stopped receiving the backup copies by email.

Following your advice, I have changed the email routing for the emails holding the backup and these are now being delivered OK. It is just that whenever I validate the backup being trying to do a “decrypt”, the backup cannot be decrypted.

Apologies for the delay in responding. I had missed your reply.

Anyway. The backup was mailed to me.

A couple of points worth noting:
1. Sometime last September, the backups stopped being sent automatically to me and their size increased significantly. I have not been able to decrypt any subsequent backups I’ve attempted.
2. I’m happy to include some dignostic / tracing code in MY version of the PHP script, but I’m not sure where to start…

Regards

Dave

I have raised a ticket with the ISP, but it would be useful to provide some guidance on where to look. Is the core dump likely to be caused be a lack of allocated memory?

Is there a list of resource requirements for wordpress that I can use to check that the environment is compliant against?

Hi

I’ve just run a manual backup and attempted to decrypt the backup. When I decrypt the backup I get the following error message:

The backup could not be decrypted; the following error was encountered during decryption: Decryption failed due to CRC mismatch. The file may be corrupt, or the encryption keys invalid

I’ve checked the keys and they align.

I’ve just redone the backup and everything seems to be working OK.

The only problem I now have is the weekly backup says it is working OK, but I don’t receive the mail message. Is there a way to split the dump into say 8Mb chunks as I suspect my ISP does not support receiving email messages with more than 10Mb attachments?

I’ve posted the requested information to your mailbox. Please can you le me know if it arrives safely.

BTW

Configuration details are:

Online Backup for WordPress Plugin Version 2.2.18
WordPress Version: 3.5.1
PHP Version: 5.3.3
MySQL Server Version: 5.0.67-community-log
MySQL Client Version: 1.0
Mem: 256M; Post: 50M; Upload: 50M; Timeout: 30
End of Information

I also get the problem when I try to do a manual backup and restore image.