Plugin could not be activated because it triggered a fatal error

10 years ago hemiad
Participant

Hello
i have UserPro 1.088 with php 5.5 when i have upload the new version of UserPRO, i can’t activate it we have error “Plugin could not be activated because it triggered a fatal error” with no php error…
Plz help

Thanks You

10 years ago UserPro Support Team
Participant

Hello hemaid ,
Could you please share what fatal error is it that you are facing .So that I can help you accordingly.
Thank you!

10 years ago hemiad
Participant

No error message in logs… just “Plugin could not be activated because it triggered a fatal error”

10 years ago hemiad
Participant

Allowed memory size of 268435456 bytes exhausted (tried to allocate 1048576 bytes) in F:\wamp1\www\bestbuzzer\wp-includes\wp-db.php on line 1618

9 years, 12 months ago hemiad
Participant

Up.

9 years, 12 months ago MJSupport UserPro
Participant

Hi, it seems to be a memory issue. Can you please add * define(‘WP_MEMORY_LIMIT’, ‘256M’); * in your WordPress wp-config.php file ? If still the same issue comes up – please increase the limit size and check again.

9 years, 11 months ago Alexander Hartmann
Participant

Same Problem here. I have increased the memory size up to 2048M and same error

9 years, 11 months ago Nate82
Participant

I also have this problem, increasing the memory does nothing.

9 years, 11 months ago Mr.J
Participant

You need last versions of UserPro and WordPress.

9 years, 11 months ago MJSupport UserPro
Participant

@Alexander Hartmann, Nate82 –

I can’t seem to be able to replicate it on our test server.
Request you to please raise the issue using the contact form on my profile page along with the site URL, this would help me to track the issue to closure. Link to contact page is – http://codecanyon.net/user/DeluxeThemes#contact Thanks.

9 years, 11 months ago Nate82
Participant

Ok thanks, I just sent you an e-mail through that link. It does come back with an error but I’m not sure it has anything to do with the Userpro problem:

Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /testsite/wp-includes/functions.php on line 3547 Notice: Constant WP_MEMORY_LIMIT already defined in /testsite/wp-config.php on line 94