WPIntell

Source evidence

PHP fatal error on wp-cli

WP Flow Plus · support · 2021-02-01T16:56:00+00:00

complaintsentiment
highseverity
1.0relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 26 rows with source links

15.4% 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

support
infotexsupport unresolved
I’m unable to use wp-cli ( https://wp-cli.org/ ) with this wp-imageflow2 plugin. Take the below as an example on a fresh WP 5.6 install $ wp plugin install wp-imageflow2 Installing WP Flow Plus (5.2.0) Downloading installation package from https://downloads.wordpress.org/plugin/wp-imageflow2.zip... Unpacking the package... Installing the plugin... Plugin installed successfully. Success: Installed 1 of 1 plugins. $ wp plugin activate wp-imageflow2 Plugin 'wp-imageflow2' activated. Success: Activated 1 of 1 plugins. $ wp-cli plugin list PHP Fatal error: Call to a member function getAdminOptions() on null in ...wp-content/plugins/wp-imageflow2/includes/block.php on line 40 Is this a known issue and are there any workarounds or plans to resolve this please? This is not a known issue and I am not familiar with wp-cli. The flagged line is called on the init action, and the variable should be defined and not null at that point. There is a similar discussion here: https://wordpress.org/support/topic/php-fatal-error-in-wp-cli/ Can you try to solve it by making a similar change, editing wpimageflow2.php line 176: $wpimageflow2 = new WPFlowPlus(); Change it to: $GLOBALS[‘wpimageflow2’] = $wpimageflow2 = new WPFlowPlus(); This reply was modified 5 years, 3 months ago by Spiffy Plugins . Great, that does indeed resolve the issue. Could this be added into the next release of the plugin please. I will include this in the next release. It seems like a bug in wp-cli, but I can include this as a work around. Thanks for confirming. This reply was modified 5 years, 3 months ago by Spiffy Plugins .

Comments

4 shown
Spiffy Plugins 2021-02-01T18:02:00+00:00

This is not a known issue and I am not familiar with wp-cli. The flagged line is called on the init action, and the variable should be defined and not null at that point.

Spiffy Plugins 2021-02-01T18:05:00+00:00

There is a similar discussion here: https://wordpress.org/support/topic/php-fatal-error-in-wp-cli/ Can you try to solve it by making a similar change, editing wpimageflow2.php line 176: $wpimageflow2 = new WPFlowPlus(); Change it to: $GLOBALS[‘wpimageflow2’] = $wpimageflow2 = new WPFlowPlus(); This reply was modified 5 years, 3 months ago by Spiffy Plugins .

infotexsupport 2021-02-02T14:58:00+00:00

Great, that does indeed resolve the issue. Could this be added into the next release of the plugin please.

Spiffy Plugins 2021-02-02T15:18:00+00:00

I will include this in the next release. It seems like a bug in wp-cli, but I can include this as a work around. Thanks for confirming. This reply was modified 5 years, 3 months ago by Spiffy Plugins .