Source evidence

Fatal error on latest version

Advanced Cron Manager – debug & control · support · 2024-06-01T19:44:00+00:00

Advanced Cron Manager – debug & control plugin evidence original source source API

mixedsentiment

highseverity

0.94relevance

6replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

Web Expert resolved

There is fatal error coming up when updating to the latest version. Seems the vendor folder was not uploaded on the release. [ 01 -Jun- 2024 19:36:24 UTC] PHP Fatal error: require_once(): Failed opening required ‘/home/www/wp-content/plugins/advanced-cron-manager/vendor/autoload.php’ (include_path=’.:/usr/local/share/pear’) in /home//www/wp-content/plugins/advanced-cron-manager/advanced- cron-manager.php on line 20 Same here. WP Updated to 2.5.7 and website was broken afterwards. Unfortunately, this leads to a fatal WP error. Needed to rename the plugin folder to get WP working again. Please fix asap (and ensure it doesn’t happen again) This reply was modified 1 year, 11 months ago by toxicum . Hi, thanks for the report! I just updated and installed the plugin on one of the test websites and couldn’t replicate this. You can see the mentioned file in the package downloaded from wordpress.org. How do you install the plugin? From the WordPress auto updater WP Auto-Update. When re-installing the plugin, vendor/autoload.php is there and the plugin works. So something is wrong with auto update, as the file wasn’t there on auto-update. You probably installed version 2.5.6, which had a broken package. We released the patch immediately. Sorry for the issue.

Commercial Context

Opportunity

hosting operations and site health

Cron site-health operations for keeping hosted WordPress sites healthy across caching, updates, backups, and support handoffs

Buyer: site owners, agencies, and maintenance teams

Wedge: monitor cron health, updates, cache state, cron jobs, and maintenance exceptions

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Fatal error on latest version: users show bugs, compatibility, support pain that may indicate a product gap.

Evidence quote: Fatal error on latest version There is fatal error coming up when updating to the latest version.

Affected feature: bugs

bugs compatibility support setup

Plugin

API

Advanced Cron Manager – debug & control

30.0K active installs · 831.8K downloads · rating 94.0

cron cron manager crontrol manager wpcron

Comments

6 shown

toxicum 2024-06-03T07:12:00+00:00

Same here. WP Updated to 2.5.7 and website was broken afterwards. Unfortunately, this leads to a fatal WP error. Needed to rename the plugin folder to get WP working again. Please fix asap (and ensure it doesn’t happen again) This reply was modified 1 year, 11 months ago by toxicum .

Kuba Mikita 2024-06-03T08:32:00+00:00

Hi, thanks for the report! I just updated and installed the plugin on one of the test websites and couldn’t replicate this. You can see the mentioned file in the package downloaded from wordpress.org. How do you install the plugin?

Web Expert 2024-06-03T08:35:00+00:00

From the WordPress auto updater

toxicum 2024-06-03T08:35:00+00:00

WP Auto-Update.

toxicum 2024-06-03T09:20:00+00:00

When re-installing the plugin, vendor/autoload.php is there and the plugin works. So something is wrong with auto update, as the file wasn’t there on auto-update.

Kuba Mikita 2024-06-03T14:55:00+00:00

You probably installed version 2.5.6, which had a broken package. We released the patch immediately. Sorry for the issue.