Conflict with WPSSO Plugin

Viewing 6 replies - 1 through 6 (of 6 total)
  • JS Morisset

    (@jsmoriss)

    9 years, 3 months ago

    It looks like Telegram Bot might be using the custom post type table incorrectly – those SSO columns should be at the end (WPSSO uses the standard https://codex.ww.wp.xz.cn/Plugin_API/Filter_Reference/manage_$post_type_posts_columns filter), and column widths should self-adjust, not overlay like that – so there’s probably an issue with the CSS for that table as well…

    You can disable the SSO columns, if you prefer – although that won’t solve the underlying issue. Have a look at the “Interface and General Usage” section in the WPSSO Setup Guide. 😉

    js.

    • This reply was modified 9 years, 3 months ago by JS Morisset.
    • This reply was modified 9 years, 3 months ago by JS Morisset. Reason: Added link to codex
    JS Morisset

    (@jsmoriss)

    9 years, 3 months ago

    FYI – I’ve delayed the running of some init methods in WPSSO v3.40.1-2, which might help with this (maybe). 😉

    js.

    Thread Starter AmirHossein

    (@aghorbanmehr)

    9 years, 3 months ago

    @jsmoriss Thanks for your reply.

    Thread Starter AmirHossein

    (@aghorbanmehr)

    9 years, 3 months ago

    @jsmoriss I have checked the WPSSO, actually WPSSO is very standard and neat in code. I think it can be modified in the next version of Telegram Bot. The main issue is with the standard usage of post types in WordPress and a bit of modification in CSS 🙂

    • This reply was modified 9 years, 3 months ago by AmirHossein.
    Thread Starter AmirHossein

    (@aghorbanmehr)

    9 years, 3 months ago

    @jsmoriss I’ve just found the reason, It’s not because of CSS or using the custom post type table incorrectly!
    It’s because of this code:
    if ( defined(‘WP_DEBUG’) && false === WP_DEBUG) {
    unset($columns[‘title’]);

    JS Morisset

    (@jsmoriss)

    9 years, 3 months ago

    Cool! I’m glad to hear you got things worked out. 😉

    js.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Conflict with WPSSO Plugin’ is closed to new replies.