All field groups displaying on all posts

• 

  • sirtinstudios

  • March 13, 2015 at 5:40 am

  Hello-

  I sent a support email about this but also figured I would post here in case anyone may be experiencing something similar…

  I too was experiencing the issue of disappearing taxonomy boxes with the 5.2 release. I have since updated to 5.2.1 and that issue seems to be resolved but I am now experiencing another issue in that all Field Groups are displaying on all posts despite the rules I have in place for certain ones to display for certain post types.

  Check out the attached screenshots so you can see an example of whats happening. I have tried the following:

  1) Deactivating and reactivating the plugin
  2) Re-uplaoding the plugin via FTP

  What is also weird is that I am only experiencing this issue on the site currently being worked on online (hosted with Bluehost’s Optimized WordPress hosting package) but I am NOT experiencing it on my local dev install of the site.

  The site in question is http://nashville-new.ink-n-iron.com/ and is running WordPress 4.1.1

  Separately, I was thinking about rolling back to 5.1.9 but I am getting a Not Found page when trying to access past versions via my account page.

  Thanks.

  

  Screen-Shot-....png

  

  Screen-Shot-....png

  
  
• 

  • sirtinstudios

  • March 13, 2015 at 8:09 am

  Wanted to quickly follow up on this… while trying to debug on my end I enabled WP_DEBUG in the config file on the server but did not see any errors come up and then once I disabled (set it to false) and re-uploaded the config file, the issue outlined above seemed to have fixed itself. So I guess this can be marked as resolved?
• 

  • fburatti

  • March 17, 2015 at 2:26 am

  Version 5.2.1 Still broken for me, all field groups displaying on all posts.
  For now I’m back to version 5.2.0 that works properly
• 

  

  • James

  • April 8, 2016 at 11:42 pm

  Hi @sirtinstudios and @fburatti,

  Thanks for the post.

  I could not replicate this issue on my end and thus it is safe to assume that this issue has been resolved in the latest version.

  I am going to go ahead and close this topic.