Pods Plugin Conflict

  • jtkwilliams

    (@jtkwilliams)


    6 years, 10 months ago

    When I try to broadcast a post from my main domain to a subdomain or second multisite website within WordPress, I’m hit with an error that suggests there is a conflict between the Broadcast plugin and the Pods plugin we are using.

    I would like to be able to Broadcast posts across multisite and retain the featured image in the post on the secondary site.

    Do you have any guidance as to how to address the Pods issue and improve the interoperability of your plugin with this one? The error just says:

    Pod Not Found

    Thanks for any help.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author edward_plainview

    (@edward_plainview)

    6 years, 10 months ago

    Is this with the Pods Broadcast add-on enabled?

    Thread Starter jtkwilliams

    (@jtkwilliams)

    6 years, 10 months ago

    No – I didn’t realize I needed it. Is there no way to purchase this add-on individually? It’s really the only thing I need to make it work.

    Plugin Author edward_plainview

    (@edward_plainview)

    6 years, 10 months ago

    Unfortunately not. Packaging the add-ons individually would take a lot of time and they would lose the ability to self-update.

    The premium pack consists of over 100 add-ons. I’d rather not think about splitting them out individually…

    Scott Kingsley Clark

    (@sc0ttkclark)

    6 years, 10 months ago

    Is there a reason this needs to be a premium add-on for compatibility? Is there something we could do to integrate within Pods itself?

    Thread Starter jtkwilliams

    (@jtkwilliams)

    6 years, 10 months ago

    Understood, but $100 is a lot of money just to gain basic functionality. I agree with @sc0ttkclark — any way to handle this from the Pods side?

    • This reply was modified 6 years, 10 months ago by jtkwilliams.
    Plugin Author edward_plainview

    (@edward_plainview)

    6 years, 10 months ago

    Yes and no.

    The BC Pods add-on does two things:

    1. It disables Pods during broadcasting. This is what causes the “Pod not found” error. What the Pods people could do would be to detect a broadcast and disable their save_post action.

    2. It detects certain fields (post type picks) and translates the pick to the correct post ID on the child blog. The pods people would have to hook into various Broadcast hooks, and ask Broadcast for the correct equivalent / linked post on each child blog that is being broadcasted to. Then resave that new relationship.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Pods Plugin Conflict’ is closed to new replies.