Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal error message when activating plugin other than Otter #147

Closed
rodica-andronache opened this issue Sep 4, 2024 · 2 comments
Closed
Assignees
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. Priority-High Expected resolution time - up to 2 business days.

Comments

@rodica-andronache
Copy link

Description

When you have Neve FSE, and try to activate another plugin other than Otter, you get this message "Plugin could not be activated because it triggered a fatal error."

Annotation on 2024-09-04 at 13-01-00

Step-by-step reproduction instructions

  1. Install Neve FSE
  2. Try to install and activate a plugin, other than Otter -> the message "Plugin could not be activated because it triggered a fatal error." appears even though the plugin gets activated.

Screenshots, screen recording, code snippet or Help Scout ticket

https://wordpress.org/support/topic/error-when-activating-plugin-49/

The user suggested to change this:

add_action( 'activated_plugin', 'after_otter_activation' );

to:
add_action( 'activated_plugin', array( $this, 'after_otter_activation' ) );

https://vertis.d.pr/v/CLJKaO

Environment info

No response

Is the issue you are reporting a regression

No

@rodica-andronache rodica-andronache added the bug This label could be used to identify issues that are caused by a defect in the product. label Sep 4, 2024
@pirate-bot pirate-bot added the customer report Indicates the request came from a customer. label Sep 4, 2024
@selul
Copy link
Contributor

selul commented Sep 4, 2024

@vytisbulkevicius let's prioritize this.

@HardeepAsrani HardeepAsrani self-assigned this Sep 4, 2024
@vytisbulkevicius vytisbulkevicius added the Priority-High Expected resolution time - up to 2 business days. label Sep 4, 2024
@HardeepAsrani
Copy link
Member

Thank you @rodica-andronache, I've fixed it here and made a release: #148

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This label could be used to identify issues that are caused by a defect in the product. customer report Indicates the request came from a customer. Priority-High Expected resolution time - up to 2 business days.
Projects
None yet
Development

No branches or pull requests

5 participants