Broken Plugins

Support
#1

Just an FYI. When I activate Advanced Custom Fields Pro, I get an Internal Services Error (500) when trying to build with Pro.
I understand that this is a generic error, but this is the third time that I have been unable to install plugins that are supposed to be stable but instead create errors. I do love this theme and have defended it. But I am getting frustrated that I am having to spend so much time diagnosing plugin problems and not being able to use those features. Is it that this theme is the problem and does not play nice with basic plugins? I would like to spend more time designing and less time trying to figure whats wrong with X Pro.

#2

Hi Christopher,

Thanks for writing in! I have tried to reproduce the issue on my local installation, but I couldn’t.

If you’re using a child theme, try switching to your parent theme and see if you’re getting the same error. If so, you need to check your child theme for a particular conflict.

If you’re still having issues, try disable all the other plugins and activate Advanced Custom Fields Pro plugin and see if you’re getting any error. If you’re not getting any errors, try activating other plugins one by one to see which plugin causing this issue.

The other thing you can do is to enable your error log. Edit your wp-config.php file and replace the following line define( 'WP_DEBUG', true ); with the below code.

define( 'WP_DEBUG', true ); 
if ( WP_DEBUG ) {
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
}

This will create an error log file under your wp-content directory, with the name of debug.log. You can activate your plugin that you’re having issues and then check your dubug.log file to see the actual errors.

Let us know how it goes.
Thanks!

#3

are you sure that debug.log is in wp-content? I recreated the ISE and cannot find a created debug .log.

#4

Hi,

Yes, it should create a debug.log file inside wp-content but since it’s not working try to enable display errors and you will be able to see the actual error in your browser.

define( 'WP_DEBUG', true ); 
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true);
@ini_set( 'display_errors', 1 );

https://codex.wordpress.org/Debugging_in_WordPress

This issue could be most likely due to memory limit. You can try increasing your memory limit by adding the code below in wp-config.php file

define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '1024M' );

Hope that helps.

#5

I made memory changes as you recommended. It did not fix the problem. The only thing that does fix the problem is to deactivate the Advanced Custom Fields Pro plugin.I would really like to use this plugin.
The site I am working on is just a testing site in order to learn X Pro. I would like to convert my companies website to X Pro and I really like it . The learning curve is less steep than I thought it would be, but the problems with basic plugins is troubling to me. Other themes that I have used have had far fewer compatability issues.

#6

Hi,

Can you provide the error it returned when you set debug to true. It should return an error instead of error 500.

Would you mind providing us your wordpress admin login and FTP login in Secure Note so we can take a closer look.

Thanks

#7

#8

Hi There,

When I have tried to access your site, I’m getting the following error.

Your PHP installation appears to be missing the MySQL extension which is required by WordPress.

It seems that you have switched to a different PHP version but you have not enabled mostly required PHP extensions like PDO, Mcrypt etc which I have enabled through your hosting control panel.

Then I was able to install the latest version of Advanced Custom Fields Pro plugin and activate it.

Thanks!

#9

Hello, I apologize. Perhaps I have not been clear enough.

Activating plugins has has not been the problem. They activate just fine. However, after activating them, it seems that when trying to design pages or posts in “Pro”, it is this that generates the 500 service error. So in other words, in this case, the plugin wipes out pro.

Also, where do you find the MySQL extension errors. I made changes to the config.php file as directed earlier but have not been and able to see any debug logs generated?

One other thing, I was not aware that PDO and Mcrypt extentions would not be enabled by default. I guess I wouldnt have known that you need to make additional changes and that extensions would be disabled if we change a php versions. Very confusing. I would love some direction on the proper way to change php versions.

#10

One other thing. There shows to be another update for the Advanced Custom Fields Pro plugin, but after trying to update it, I get this error.
Is this a theme issue or a plugin issue?

#11

Hi there,

It would be best to get in touch with your hosting provider about this as this is something that is beyond the scope of our support.

This should be fine since ACF Pro is a bundled plugin with X and the latest supported version is 5.6.10 while the latest version released by the plugin vendor is 5.7.2. We are still doing some testing for the latest version of ACF Pro with X and when everything is tested, we will release an update on our end and you should be able to update ACF Pro.

Hope this helps.

#12

It does help. Thanks.
I really love having this kind of support and knowledge base for X. Hands down the best experience that I have had with a theme.

#13

Thanks for your kind words, we do appreciate it.

#14

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.