Anthonius Alfred Andreas

Hi @alizee082

Sorry to hear that, but have you tried contacting the Elementor support team (https://www.ads-software.com/support/plugin/elementor/) and send them the error message for help?.

Thanks
Anthon

Hi @warhangel7

Apologies for the delay in replying.

We’ve managed to reproduce the issue you reported, our development team is actively working on a fix for this issue now and will include the fix in the next release of EUM. The site info and stacktrace you have given us have helped our investigation in understanding the root cause better.

Thanks
Anthon

Hi @tvspec

The overdue scheduled tasks warning indicates that the cron job you set via your hosting panel doesn’t run. Are you sure you have set up the cron cob correctly?. It could also mean that another plugin is preventing your wp-cron.php file from being accessed. Typically, security plugins have a feature that can block access to your wp-cron.php file, so if you have a security plugin installed, please look for that feature and disable it if enabled. If you’re not sure what security plugin is active in your site, you can send us your site information by fetching it via the WordPress’ Site Health tool (wp-admin/site-health.php), under the Info tab click the Copy site info to clipboard and paste it here. For now, in your wp-config.php file you can set the DISABLE_WP_CRON constant back to false, or just remove it.

As for the Unexpected response: Security check message, it means UpdraftPlus failed in verifying a cryptographic token that is being used for your logged-in session, this is usually because your WordPress login session has expired. Since this error has nothing to do with the topic you started, please create a new topic for further assistance.

Thanks
Anthon

Hi,

wget is a command line tool on the hosting side for making HTTP requests, when adding and setting up the DISABLE_WP_CRON constant to true, you disable the WP-Cron system to be triggered when a webpage loads up which is also dependent on users visiting the page, it will also ignore the ALTERNATE_WP_CRON constant regardless of the value being set. Using that command you instruct your hosting server to make a HTTP request to your website every 15 minutes, for querying the list of scheduled events that are “due now” and running the events.

Thanks
Anthon

Hi,

Usually, WP-Cron will work fine on a site with moderate traffic. In your case, it’s either you’ve got too much traffic that would make your backup time out easily or you’ve got little to no traffic that would greatly increase the chance to miss a scheduled event like a backup resumption. I’m not quite sure which one it is, but I’d like recommend you disable the built-in WP-Cron system and set up a cron job in your hosting panel and see if that resolve the issue.

To disable WP-Cron, please add the following code to your wp-config.php file, before the line where it says /* That’s all, stop editing! Happy publishing. */

define('DISABLE_WP_CRON', true) ;

To set up a new cron job, go to the Cron Jobs page in your hosting panel and add the following command and set it to run every 15 minutes:

wget -q -O - https://example.com/wp-cron.php?doing_wp_cron

Replace https://example.com with your domain name.

Thanks
Anthon

Hi,

Yes, as of EUM 8.1.0 the toggle button was removed as the logging is now always turned on. However, you can still disable logging for EUM using these two hooks/filters:

pre_update_site_option_MPSUM
pre_update_option_MPSUM

but you will need to create a PHP file in your wp-content/mu-plugins directory (e.g. wp-content/mu-plugins/eum-disable-logs.php), and add the following code in it:

<?php
function eum_disable_logs($value) {
	if (!is_array($value)) $value = array();
	if (empty($value['core']) || !is_array($value['core'])) $value['core'] = array();
	$value['core']['logs'] = 'off';
	return $value;
}
add_filter('pre_update_site_option_MPSUM', 'eum_disable_logs', 10);
add_filter('pre_update_option_MPSUM', 'eum_disable_logs', 10);

save it and go to EUM’s general settings page, click any setting you have in the Updates settings section, you don’t need to change it, just click the same option. After clicking it, you will have the Update Logs disabled, and if you want to turn it back on, just remove the file from your wp-content/mu-plugins directory.

Thanks
Anthon

Hi,

We do support AWS4 (AWS Signature Version 4) and HMAC-SHA256 (the signing algorithm). However, it’s not enabled by default as our S3 library has a mechanism in which it can automatically set the signature to version 4 only if it matches with one of the storage providers that is currently listed in our library. Unfortunately, Oracle Cloud (OCI) is not in our list yet, but we have a filter that you could try to force the use of signature version 4 for your Oracle Cloud storage, but before we give you the snippet of the code, could you let us know what S3 endpoint you use for your Oracle Cloud setting?

Thanks
Anthon

Hi Chintan Hingrajiya,

We’re really sorry about the issue you are experiencing. Unfortunately, we didn’t manage to replicate the issue. We believe this kind of issue is not ordinarily happening with our users. Could you give us more details about what you get in the Developer Console of your browser, or is there anything (notice, warning, fatal error) triggered by PHP, which is then written in the error log file after you click the Save button?. Do you have WP_DEBUG constant enabled in your wp-config.php file, could you please disable the constant by setting it to false. Also if it’s not too much to ask, could you send us your site information, which will help us in further investigation of the issue?. To fetch the site information you can go to /wp-admin/site-health.php?tab=debug, click the “Copy site info to clipboard” button and paste it here.

Thanks
Anthon

Hi,

If one of your plugins/themes currently has a new version available, could you please try to do Force Updates from within the plugin, you can find the tool under the Advanced tab. If that doesn’t work, how about performing a manual update to one of your plugins/themes, I mean after doing it do they get updated? and that you could see a related-update entry in the Update Logs page. Also, could you send us your site information, which will help us in further investigation of the issue?. To fetch the site information you can go to wp-admin/site-health.php?tab=debug, click the “Copy site info to clipboard” button and paste it here.

Thanks
Anthon

Hi,

Is the website hosted on a managed WP hosting?. If not, could you please go to the Update logs tab and look for a log entry that has information about the update of the WP Core from version 5.9.3 to 6.0, under the Stack Trace column, please click the Show Trace link text, copy the data and paste it here. Also, could you please post your site information here, to get the site info you could fetch it from the WP site health tools (/wp-admin/site-health.php?tab=debug), click the Copy site info to clipboard button and paste here.

Thanks
Anthon

Hi

Thanks for requesting the feature. I will pass this on to the development team so that we can discuss this further with our lead developer. We like your idea about the log file and we will consider this in a future release of EUM.

Anthon

Hi

Currently EUM doesn’t have such a feature, EUM doesn’t provide a log file that you could access or open via text editor. Actually, EUM premium version will handle the scenarios where your site may crash after an update due to incompability of PHP and/or WP versions or some other problems that can cause a PHP fatal error. On the premium version, there’s a Safe Mode feature that will block automatic updates to plugin and theme updates if the PHP or WP version requirement is not met. This can prevent your site crashing due to running incompatible plugins/themes. Also, a feature when a fatal error occurs after a plugin update, EUM will automatically disable the plugin so that you can still access your website and log into the WP dashboard.

Actually, without a log file you would still be able to find out what plugin or theme causes a fatal error after an update was performed, you could just look for the PHP error log file and see the recent log entry.

Thanks
Anthon

Hi @megaphonejon

Thanks for reporting. Using the same plugin (Better Messages – Live Chat for WordPress) we’re unable to reproduce the issue on our side, so yes it doesn’t happen in all scenarios. Going deeper with the issue, we believe this is due to the debug_backtrace() returning call stack entries which one of them has a function in which a Closure object/type is listed as an argument and then an exception is thrown by PHP because serialize function doesn’t allow Closure to be serialised.

Our development team is still investigating this issue, and will work on a fix for the next release.

Thanks
Anthon

Hi Kattis,

Sure, no problem. I will keep an eye on this topic.

Thanks
Anthon

Hi Kattis,

EUM had several log bugs in its previous version (9.0.12), and it looks like the log entries you provided were affected with one of the bugs. I recommend you update EUM to its current version (9.0.13), which has been released on June 7th. EUM has a better log mechanism in that new version, also there’s a tweak concerning the core updates, it deals with how EUM prevents other plugins from overriding the Manually core updates setting.

Thanks
Anthon