WPIntell

Source evidence

Might be ok

Maintenance · review · 2024-10-10T07:40:00+00:00

Maintenance plugin evidence original source source API
mixedsentiment
highseverity
1.0relevance
7replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

3 / 25 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 3 stars
Julian unresolved
When I installed the plugin, I have gotten a 500 server error, which happened twice. So I decided to just write my own plugin. This plugin might be working fine, I did not use it however. This topic was modified 1 year, 7 months ago by Julian . Hi, Sorry to hear about the issue but that Nilambar namespace is not used by Maintenace. As far as I can find it seems to be used by a theme or the dev of that theme and it’s mentioned in this other thread as well: https://wordpress.org/support/topic/deprecated-creation-of-dynamic-property-12/ Activating Maintenace probably just enabled the logging of that warning as otherwise error logging might have been supressed by something. Well, I just tested it on my dev test system, with only storefront installed and woocommerce. When activating your plugin, I get these error messages. I don’t see how… there’s no “Nilambar” anywhere in our code 🙁 Can you post the full trace please? The text after “Deprecated: Creation of dynamic property Nilambar\Welcome\Welcome::$product_name is deprecated in ” … so I can see where it’s finding that? Sorry, it could have been the other Maintenance plugin I tried. Either way, when I install the plugin, I first get a 500 error, happened twice now. OK, well you can post the 500/Fatal error trace and I can check that out if it’s actually from our plugin. Third time around I couldn’t recreate the error. I have changed my review to relfect a better rating. In the end, I wrote my own plugin. Thank you for the quick responses! OK, thank you 🙂

Comments

7 shown
Alexandru Tapuleasa 2024-10-10T08:51:00+00:00

Hi, Sorry to hear about the issue but that Nilambar namespace is not used by Maintenace. As far as I can find it seems to be used by a theme or the dev of that theme and it’s mentioned in this other thread as well: https://wordpress.org/support/topic/deprecated-creation-of-dynamic-property-12/ Activating Maintenace probably just enabled the logging of that warning as otherwise error logging might have been supressed by something.

Julian 2024-10-10T08:59:00+00:00

Well, I just tested it on my dev test system, with only storefront installed and woocommerce. When activating your plugin, I get these error messages.

Alexandru Tapuleasa 2024-10-10T09:17:00+00:00

I don’t see how… there’s no “Nilambar” anywhere in our code 🙁 Can you post the full trace please? The text after “Deprecated: Creation of dynamic property Nilambar\Welcome\Welcome::$product_name is deprecated in ” … so I can see where it’s finding that?

Julian 2024-10-10T09:26:00+00:00

Sorry, it could have been the other Maintenance plugin I tried. Either way, when I install the plugin, I first get a 500 error, happened twice now.

Alexandru Tapuleasa 2024-10-10T09:30:00+00:00

OK, well you can post the 500/Fatal error trace and I can check that out if it’s actually from our plugin.

Julian 2024-10-10T10:18:00+00:00

Third time around I couldn’t recreate the error. I have changed my review to relfect a better rating. In the end, I wrote my own plugin. Thank you for the quick responses!

Alexandru Tapuleasa 2024-10-10T18:28:00+00:00

OK, thank you 🙂