Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Jeff Starr

    (@specialk)

    If so, it wasn’t from the plugin side of things (that I know of). Maybe there is a way to reach the user who posted about it, maybe check their user profile and see if any social media or contact links. Or if you have any further questions feel free to post them here. Thank you.

    Thread Starter jamesstcrice

    (@jamesstcrice)

    Thanks for the quick reply, Jeff.
    I am doing some more testing and it doesn’t happen when you leave “disable everywhere” checked. However, it seems to happen if you start adjusting per role. Still working to narrow down.
    I own the paid version of the other plugins, so I submitted a ticket there as well.

    Plugin Author Jeff Starr

    (@specialk)

    Okay let me know if I can provide any infos about the plugin. Glad to help however possible.

    Thread Starter jamesstcrice

    (@jamesstcrice)

    So based on the testing I did, this is what happens.
    With “Disable Gutenberg everywhere” checked, I don’t get the problem.

    If I uncheck “Disable Gutenberg everywhere” and check all the roles and all the post types, I still do not get the problem.

    If I just uncheck “Disable for Administrator” (my role), then I get the error.

    Going to add this info to my other thread as well.

    Does that provide any clues as to what might be happening?

    Plugin Author Jeff Starr

    (@specialk)

    Not sure, I will take a look. Thanks for the information.

    Maya

    (@tdgu)

    Hi,
    I’m the developer of Post Types Order and Category Order and Taxonomy Terms Order.
    I checked into the problem and found the cause. This is located in your /inc/plugin-core.php at function disable_gutenberg_disable_post_type() Appears you change the $typenow superglobal variable, that the WordPress core uses ( along other areas ) in admin.php at lines 177-201. When the loaded interface is Posts, this superglobal is expected to be empty or the slug for any of the core components ( e.g. edit-tags.php ) Still, in your code you set that to post which conclude the problem.

    Can you check it out on your side?

    Thanks

    Thread Starter jamesstcrice

    (@jamesstcrice)

    Hi Jeff,

    Have you had a chance to look into this?

    Thanks

    Plugin Author Jeff Starr

    (@specialk)

    @jamesstcrice

    Not yet, it’s on the radar though.

    Plugin Author Jeff Starr

    (@specialk)

    Just to follow up on this. I think the issue is resolved in the next version of DG. Please test and let me know, thank you.

    Related/reference: https://www.ads-software.com/support/topic/bug-globla-typenow-forced-to-post-on-edit-php-admin-pages/

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘cannot load to-interface-post’ is closed to new replies.