PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Bug Report: New PageLines Framework issue

  1. Hey there, I just switched one of my new builds over to the new PL Framework which was supposed to be "an easy switch", not so much. They failed to mention some known conflicts such as this one as stated by their forum mod: "Do you have PageLines Store add-ons installed? There is one add-on (I can't remember which) that conflicts with Gravity Forms because of a Gravitry Forms error."

    The forms displayed fine on the original PL platform with Base child theme. Now, the forms are not displaying at all.

    Have you all been alerted to this conflict and, if so, is there a bug fix in the very near future? Like maybe this week? That would be fabulous, if possible! Thanks!

    Posted 4 years ago on Tuesday March 6, 2012 | Permalink
  2. This issue is being caused by a WordPress bug related to the use of add_object_page.

    It's a highly unique bug and the only situation we've ever encountered this issue out of the thousands of themes that are out there... is Pagelines.

    There is a WordPress support ticket related to this bug here:

    We are going to take a look and see how we can work around this bug without changing Gravity Forms menu location behavior for all users. We may end up having to handle adding the menu differently if the user is using a PageLines theme, which is highly annoying from a code standpoint to have to do so... having to implement an IF statement for a specific theme isn't very efficient.

    We'll look into this and i'll update this thread once we have more information. I will get back to you this week one way or the other with at the very least a way for PageLines users to fix the issue using a hook.

    Posted 4 years ago on Tuesday March 13, 2012 | Permalink
  3. nphaskins

    This is not a bug with PageLines. The crew and I just sat down and have replicated your bug together with Wordpress Custom Post Types.

    Again, this is nothing to do with our framework, and everything to do with Custom Post Types. Here is our proof.

    Here we used simple custom post type plugins for reference, and we created 3 of them. As you can see, this first screenshot shows our Custom Post Types "One", "Two", and "Three." Gravity Forms is NOT activated, nor is PageLines.

    Now, we activate Gravity Forms, and look what happens. The Custom Post Type "one" is now missing. PageLines is NOT activated.

    This test proves that your bug is conflicing with Custom Post Types, not PageLines.PageLines is getting blamed because we're one of the few themes using Custom Post Types in our framework.

    I think it would be most prudent for you guys to update your code, as it's proven to be a bug within Wordpress when using Custom Post Types.

    I hope this message finally eliminates the blame game.


    Designer - PageLines

    Posted 4 years ago on Friday March 30, 2012 | Permalink
  4. @nphaskins Where in my post above did I claim it was a bug in PageLines? My post above speaks for itself.

    Let's see EXACTLY what I said in my post above...

    This issue is being caused by a WordPress bug related to the use of add_object_page.

    So before you point the finger and try to claim we are playing a blame game maybe you should get your facts straight.

    But I will say it's about damn time someone from PageLines actually reached out to us considering up to this point the only thing PageLines has done is point the finger at Gravity Forms repeatedly without even knowing what the issue is. DESPITE the fact i've reached out to PageLines on numerous occasions to discuss the matter.

    And no, this does not eliminate the blame game because quite simply you STILL don't understand what the issue is and what is causing it.

    If you DID know what the issue was you would know it's a WordPress bug related to the use of add_object_page and not a bug in Gravity Forms or PageLines.

    I want to also add that there is no compatibility issue with Gravity Forms and using custom post types. The issue is how the plugin you happened to use to create the custom post types is adding the menu items for those post types. When I use standard PHP to create a custom post type in WordPress, it works just fine. See this screenshot:

    There is an Add-On for Gravity Forms SPECIFICALLY for using Custom Post Types in the plugin repository with almost 12,000 downloads. If there is an issue with Gravity Forms working with custom post types... you can be sure all the users of that Add-On would be slamming us with support. That is not the case.

    As I stated in my post above, this is a WordPress bug related to the use of add_object_page.

    In the future, I would appreciate it if you keep your own finger pointing off of the support forums. If you have an issue with Gravity Forms related to your product... contact us developer to developer and we'd be glad to discuss the issue.

    Until then, don't put words in my mouth because I stated exactly what the cause is in the post above.

    Posted 4 years ago on Friday March 30, 2012 | Permalink
  5. nphaskins

    I hope we can resolve this issue please take a minute to review the three links posted below.

    All using default wordpress theme with no plugins apart from gravity forms and 'simple custom post types'

    Our lead developer Simon has patched your bug, and has already emailed it to you. The patch counts active custom post types and if present it uses an alternative menu method.

    Your forms menu is still kept high up the list and not added to the bottom.

    I hope this helps to resolve this issue once and for all.

    2011 with 3 custom post types.

    2011 with 3 custom post types and gravity forms enabled.

    2011 with 3 custom post types and patched gravity forms


    P.S - Your screen shot only shows 1 post type. I've explained that in order to duplicate the error you need to have more than 1 custom post type.

    Posted 4 years ago on Monday April 2, 2012 | Permalink


Support Tickets

Open A New Support Ticket
 Open A New Priority Support Ticket *

* Developer license holders only