WPIntell

Source evidence

PHP language error upon plugin activation

Contact Form Dashboard · support · 2018-04-25T21:02:00+00:00

complaintsentiment
highseverity
0.97relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 32 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Chris unresolved
I have the WP site set in Polish. When I activate the Contact Form 7 Dashboard plugin I get this error: Warning: is_readable(): open_basedir restriction in effect. File(/home/impreroc/domains/innova.uno/public_html/klient/wp-content/plugins/contact form-dashboard/contact-form-dashboard.php/languages/cfd-pl_PL.mo) is not within the allowed path(s): (/home/impreroc/domains/innova.uno:/tmp:/var/tmp:/home/impreroc/.tmp:/home/impreroc/.php:/usr/local/php:/opt/alt:/etc/pki/tls/certs) in /home/impreroc/domains/innova.uno/public_html/klient/wp-includes/l10n.php on line 584 Have no idea how to fix this. This topic was modified 8 years, 1 month ago by Chris . This topic was modified 8 years, 1 month ago by James Huff . I managed to dismiss the warning permanently by asking my hosting provider to disable to open_basedir option on the server side. However this is highly unreasonable since it significantly hinders the security level of all domains on my hosting account. On client production website I wouldn’t do that and rather not use the plugin, since the warning gets displayed on both backend and frontend. Any way do modify the plugin to avoid this warning?

Comments

1 shown
Chris 2018-04-26T14:00:00+00:00

I managed to dismiss the warning permanently by asking my hosting provider to disable to open_basedir option on the server side. However this is highly unreasonable since it significantly hinders the security level of all domains on my hosting account. On client production website I wouldn’t do that and rather not use the plugin, since the warning gets displayed on both backend and frontend. Any way do modify the plugin to avoid this warning?