WPIntell

Source evidence

ArgumentCountError thrown

Custom 404 Pro · support · 2019-03-14T06:01:00+00:00

mixedsentiment
mediumseverity
0.84relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 25 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.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
filout resolved
Hi, after updating WP to v5.1.1 i get the error ArgumentCountError thrown Too few arguments to function AdminClass::custom_404_pro_upgrader(), 1 passed in /.../class-wp-hook.php on line 288 and exactly 2 expected Regards, Filout This topic was modified 7 years, 2 months ago by filout . @filout thanks for the bug report! This should be fixed for customers in 3.0.5 You can delete the plugin, re-install it and it should be fine. Let me know if it works! Hi Kunal, must i re-install the plugin? Just now i updated on v3.0.5 and got the same error. Or is it enough to deactivate and activate the plugin again? Regards, Filout @filout re-installing the plugin gets you to a fresh start and re-initializes all the tables. This error has been fixed in 3.0.5 so going forward (in future updates) you’ll not see it – that’s just how the WordPress Upgrader method works unfortunately. Technically speaking, you should not see this error when doing a fresh install. Let me know if you do. I re-installed the plugin and everything seems to be okay. No error was shown. Thank you for your support! 🙂

Comments

4 shown
Kunal 2019-03-14T06:32:00+00:00

@filout thanks for the bug report! This should be fixed for customers in 3.0.5 You can delete the plugin, re-install it and it should be fine. Let me know if it works!

filout 2019-03-15T05:28:00+00:00

Hi Kunal, must i re-install the plugin? Just now i updated on v3.0.5 and got the same error. Or is it enough to deactivate and activate the plugin again? Regards, Filout

Kunal 2019-03-15T07:04:00+00:00

@filout re-installing the plugin gets you to a fresh start and re-initializes all the tables. This error has been fixed in 3.0.5 so going forward (in future updates) you’ll not see it – that’s just how the WordPress Upgrader method works unfortunately. Technically speaking, you should not see this error when doing a fresh install. Let me know if you do.

filout 2019-03-18T07:11:00+00:00

I re-installed the plugin and everything seems to be okay. No error was shown. Thank you for your support! 🙂