• 0
Sign in to follow this  
Followers 0

Another problem with upgrade to 2.1.4

Question

Posted · Report post

Any idea what is causing this problem after installing 2.1.4? ... when I call Meta/Special up, I get this right away. Tried removing Google+ but it did not help. Fatal error: Call to a member function option_engine() on a non-object in /home/cayugan/public_html/wp-content/themes/pagelines/admin/class.options.metapanel.php on line 402

Share this post


Link to post
Share on other sites

11 answers to this question

  • 0

Posted · Report post

Hi, Can you disable all active plug-ins and see if this resolves the issue.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

I disabled all plugins. This did not have any affect on the problem. Also rebooted and refreshed and cleaned cache to be sure.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

[img]http://outdooramusementbusiness.com/metaproblem.png[/img]

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

Do you get this error when you click on a different meta option (i.e. something other than Google+)?

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

2.1.5 will fix this, sorry! It will be live very soon.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

If you need a temporary fix until the 2.1.5 update is released, you can disable Vanilla/MediaWiki from WP -> PageLines -> Store -> Integrations

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

^^ Just disable any plugins/integrations that add a tab to that menu ie: vanilla, bbpress etc etc.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

I'm having the same problem. Is there an ETA for 2.1.5?

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

My Meta section was not working. What I did was to disable de BBpress plugin and it started to work!!, so there's a bug in the 2.1.4 upgrade.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

Thank you. Will wait for 2.1.5 and go from there.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

Resolved with 2.1.5 upgrade

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0