WPIntell

Source evidence

Installed plugin and crashed site

Organic Builder Widgets – Simple WordPress Page Builder · support · 2018-09-14T01:04:00+00:00

mixedsentiment
highseverity
0.94relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 34 rows with source links

17.6% 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
geneseemccalester resolved
Hello! I was very excited to try your widget but I did something wrong and now I can’t access my site. I got this error message: Parse error: syntax error, unexpected T_FUNCTION in /home/daverill/webapps/education/wp-content/plugins/organic-customizer-widgets/includes/class-organic-widgets.php on line 178 I am very new to this and have no idea what I’m doing so I would greatly appreciate your help! The page I need help with: [ log in to see the link] Hello, Did you get this issue resolved? Do you know what you did to produce that error? Thanks! Hello! Unfortunately, no I haven’t figured it out. It happened just when I installed the plugin and now I can’t get to the back end at all. Any suggestions? Thank you!! Hello, The line of code your error is referencing is responsible for registering the custom widgets. It’s pretty standard code, and should not have produced an error unless there was some kind of conflict — possibly with another plugin, your theme, or your hosting environment. It could be that your web server is running on an outdated version of PHP. The Organic Widgets plugin requires PHP version 5.3.29 or higher. My recommendation would be to make sure your server is running the latest version of PHP, which you should be able to upgrade with your hosting provider. My next recommendation would be to delete the plugin and see if that resolves the issue. In order to delete the plugin without accessing the WP admin, you will need to log in to your server via FTP. This can usually be done through your hosting provider, or using software like FileZilla. Then, you will need to locate the plugin folder and delete it. The path to the folder on your server should be something like this: /my-site/wp-content/plugins/organic-customizer-widgets I hope this helps. Thanks! Marking this as resolved since there has been no activity.

Comments

4 shown
Organic Themes 2018-09-18T02:08:00+00:00

Hello, Did you get this issue resolved? Do you know what you did to produce that error? Thanks!

geneseemccalester 2018-09-18T03:30:00+00:00

Hello! Unfortunately, no I haven’t figured it out. It happened just when I installed the plugin and now I can’t get to the back end at all. Any suggestions? Thank you!!

Organic Themes 2018-09-20T16:39:00+00:00

Hello, The line of code your error is referencing is responsible for registering the custom widgets. It’s pretty standard code, and should not have produced an error unless there was some kind of conflict — possibly with another plugin, your theme, or your hosting environment. It could be that your web server is running on an outdated version of PHP. The Organic Widgets plugin requires PHP version 5.3.29 or higher. My recommendation would be to make sure your server is running the latest version of PHP, which you should be able to upgrade with your hosting provider. My next recommendation would be to delete the plugin and see if that resolves the issue. In order to delete the plugin without accessing the WP admin, you will need to log in to your server via FTP. This can usually be done through your hosting provider, or using software like FileZilla. Then, you will need to locate the plugin folder and delete it. The path to the folder on your server should be something like this: /my-site/wp-content/plugins/organic-customizer-widgets I hope this helps. Thanks!

Organic Themes 2018-10-02T13:52:00+00:00

Marking this as resolved since there has been no activity.