Support » Plugin: Broadcast » General Question – Pre Activation!

  • I’m hoping this is the perfect addition to my plans!!! 🙂

    I’m half way building this site – it’s a knowledge repository that clients will use. It is a multisite, where the primary is the main content – not to be edited by customers will be held. Each client will have their own subsite.

    New/edited content will be pushed across all the clients to update theirs.

    I need to have all broadcasts sent out as as posts / pages – but to redirect to the corresponding page in the main site. The client must have the ability to EDIT this page to hold their own content (and so it no longer redirects home but any links to it show their edited content). Hope that makes sense.

    I think I read the redirect in the documentation….

    however, need the broadcast pages to have the same title as the main pages (and the same URL except for the subsite bit – i.e http://primary.com/page-title-name is http://primary.com/client/page-title-name) This means that the reference links to this page (from various pages and external generated documents are valid).

    Is this the way it’s done?

    In addition, can we bulk broadcast existing pages to a specific site? This would help with generating a new site, without the need to create a template?

    Thanks

    Ashley

    The page I need help with: [log in to see the link]

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

    (@edward_plainview)

    Hope that makes sense.

    So main site has a bunch of pages.
    The pages are broadcasted to child blogs.
    Normally, the broadcasted page automatically redirects to the main site.
    IF the user chooses to edit their page, it should no longer redirect but instead the vistor should view the page on the child blog?

    That’s difficult. If you were happy to use the child blog’s version all the time, then perhaps the Protect Child Properties add-on could help. There’s an option there that will prevent the child content from being overwritten if it differs from the parent post.

    When broadcasting, the child posts keep the same slug, so page-title-name will be the same on both blogs.

    Bulk broadcasting can be done using the Send To Many and New Blog Broadcast add-ons.

    There. I think that’s all of your questions. 🙂

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Thanks for the quick response. I’m thinking New Blog Broadcast is the ticket for the second point.

    I was thinking of Redirect all Children. How is the redirect created? Is it in the page (i.e header), css or server.

    Here’s what I’m thinking. I want the client to use/edit their version of pages / posts – it’s the main point that they tailor it to their own version / needs. However, I don’t want the content on the Parent sitting in their site and I don’t want the parent to be affected – so any edits are specific to them.

    I’m trying to prevent clients from managing physical redirects in the dashboard, – infact I only want them to manage the content on the front end!

    Hope that makes sense.

    Ashley

    Plugin Author edward_plainview

    (@edward_plainview)

    The redirect is in the page header, before the user even sees the page.

    Then it definitely sounds like Protect Child Properties is what you need. It works like this:

    • Page is broadcasted the first time: xyz
    • Child1 content is xyz
    • Child2 content is xyz
    • Parent updates page if content is unchanged: z123
    • Child1 content is z123
    • Child2 content is z123
    • Child1 edits content: ABC
    • Parent updates page if content is unchanged: z234
    • Child1 content is ABC
    • Child2 content is z234, because there are local changes

    Does that sound like it will solve your problem?

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Yes – in part and that would be the result of updates on content.

    But this put all my content onto the client instance (hence why the redirect to keep MY content off their site – until they edit!). If they were to do that – they would have to duplicate the page with the same slug and delete the original page in the child, (as they won’t be able to edit the header)- and assuming the redirect is based on the page number?

    As an alternative, can I make the child pages only editable by the super admin (except duplicate / delete?)?

    Plugin Author edward_plainview

    (@edward_plainview)

    Your first option sounds very difficult to solve.

    Your second, easier: Lock Post

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Edward, Thanks very much. I’ll work through this and see if we can get this to work. Last question – for the moment, can we bulk broadcast on the redirect all children?

    Thanks!

    Plugin Author edward_plainview

    (@edward_plainview)

    Bulk broadcast on the children? Don’t follow you.

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Hang on….Am I being a little stupid?

    If I use lock posts, it gives them the ability to edit some of the content but restrict all other editing / deleting etc. and if I remove an ability to export, they won’t be able to extract content that’s generated from the parent….that would work….I think!

    I just need to then think of a way to export only content they’ve generated!

    Plugin Author edward_plainview

    (@edward_plainview)

    Locking the post will prevent it from being edited at all, so that’s no solution.

    Hm. I can’t really think of a turnkey solution for you. Half you what you want is possible, but not together with the other half.

    Not without custom code, at least.

    The Redirect All Children add-on can be overriden using a WordPress filter, but it will require custom code to help decide whether or not to redirect.

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    OK – I’m conscious of taking up all your time.

    I read this https://broadcast.plainviewplugins.com/2017/04/02/franchising-with-wordpress-and-broadcast/

    So if I can create new blog, and follow the instructions in the link above that would get most of the way.

    I remove any ability to export – so they can’t extract the proprietary content (without spending hours and hours cutting and pasting from the source code). If they then want their content, we can extract get that for them!

    I think that would be the best solution.

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    so that would be:

    New Blog Broadcast
    Lock Posts
    Protect Child Properties

    Plugin Author edward_plainview

    (@edward_plainview)

    I guess?

    It’s a little difficult for me to guess without having the site in front of me. :/

    If you desire access to a demo site I can arrange that for you. Just e-mail me att edward@plainviewplugins.com and I’ll get you fixed up.

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Thanks.

    If a post is Locked – can a Super Admin still edit it as normal?

    You’ve been a great help – really appreciate it. Is there a grace period if we buy the add-ons to test on our site?

    Have a nice evening!

    A

    Plugin Author edward_plainview

    (@edward_plainview)

    Superadmin always has access to everthing.

    I allow for refunds if the add-on isn’t working as advertised and I cannot fix it.

    Thread Starter ashleyjbassett

    (@ashleyjbassett)

    Edward – great. It’s late here – I’m going to get to this early next week and do the testing. If I have any questions – I’ll let you know – but I think this will get us the functionality we need without massive customisation. If we need development on top to smooth things out – we’ll reach out, and assuming you do customisation work, we’ll contract for that.

    Cheers – have a great weekend.

    Ashley

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘General Question – Pre Activation!’ is closed to new replies.