Plugin could not be activated because it triggered a fatal error.

@ajhad
We had another plugin experiencing this and found that they were using shared hosting with on a weak server. So you may want to look into a better performance hosting package when using our plugin on your WP site.

Thanks

I am on a shared hosting server. What would you suggest requirements wise? I have 1 GB of RAM now and other stuff I don’t really understand.

I talked to GoDaddy and they can upgrade my current environment for more RAM or I can move to a dedicated server. Obviously, there are some price differences there. What do you suggest for server requirements?

@ajhad,

I recommend a dedicated server for this

Thanks

Thank you. I will switch over and report back if I have anymore trouble.

Thank you.

I upgraded to a dedicated hosting environment and I am still getting the same error.

Are there any type of requirements besides a dedicated environment?

This is due to there not being listings because the hosting can’t handle all of the API calls this older version is making. That causes the hosting to timeout on the request and this serves up no listings.

V4 has much more performant API calls, better caching, better error handling, which also means it will work on more “less than optimal” hosting plans, but there’s not a solution for V3 other than upgrading the hosting a little to get more power behind the plugin.

Where can I try V4?

I have upgraded the resources on the dedicated server and I still am not able to activate the plugin. I have 4GB of Ram dedicated to this website, 4 CPUs, and the best hosting I can get and it still does not work.

• This reply was modified 7 years, 7 months ago by ajhad.

We just spoke over the phone and found out that it was a conflicting plugin. If you can pinpoint which one it was I can document that so we can further investigate. v4 wont be out until sometime later this month.

I reactivated all plugins initially activated and the plugin now works with all plugins activated.

I narrowed it down to the YOAST SEO plugin.

But, a workaround is to deactivate YOAST and activate FLEXMLS and then reactivate YOAST and both plugins work as intended. I believe YOAST SEO is blocking the initiation of something in the plugin if it is active when trying to activate FLEXMLS.

I can replicate problem on other sites so I know it is the YOAST Plugin.

Ajhad, Thank you for figuring out the conflicting plugin – was driving me crazy for a solid hour.