Multisite remember widgets – Shared widgets – Widget Clipboard

Moved to MultiSite.

Generally, no. MultiSite is intended for multiple separate sites, so this is a bit anathema to that end.

there’s no way to predict how custom widgets will save the data to the DB to be retrieved from another site

Sure there is. Read the code. By default most of them save data to blog specific options tables. Unless they are coded to save them elsewhere.

If you want global widgets change them to save in a global table.

When, when I mentioned about others not knowing how how each plugin saves to the DB I meant THAT and the other things I don’t know but imagine could be like files stored in server, folders created that could be missing by just adding the content to the DB… post info modified/added… etc.

But Andre’s anwer, explains a lot.

So the plugins COULD have their data shared if the developers so wanted it.

That means what would make me happy is a plugin that would change that.

Thanks

So the plugins COULD have their data shared if the developers so wanted it.

Yes but ??

Remember that if you save to a global table that everyone can write to, then everyone can (possibly) change settings for everyone, and often that’s not desirable.

There are plugins that will push default settings for all plugins to all blogs, but the lack of centralization is intentional ??

That means what would make me happy is a plugin that would change that.

That can;t be done.

You;d have to fork each plugin you want to save globally. There’s too many variables (for one) to be able to make a plugin that would do this for any other plugin.

Yes, I pictured that. That’s what would make me happy!
Who wouldn’t?

People who don’t use MultiSite for multiple ‘same’ sites? ??

when you have many sites, having many centralized areas is not “centralized” anymore!

This is a use-case issue, alas. Remember, MultiSite is meant for running multiple separate sites. So there’s no need to set up a plugin or a widget 100% the same for all the sites because not all sites are the same. Look at WordPress.com ?? Every site gets its own options.

Think of wordpress.com. They use multisite for literally millions of blogs. 99.99% of their users would not want an identical widget on every blog, controllable by one person.

Same as any university using multisite for student blogs, of why there are many. Thousands.

Right. Agree. Correct.

Come on!
If you knew of a plugin that could do that, just by knowing it’s a mission, and somebody took the challenge and made it possible, you’d be happy anyway, regardless of not managing a network of same sit… Hey!, actually, that plugin doesn’t have to be necessarily for “same” sites!

Let’s forget for a second that I needed “shared” pages for a network of sites.

A network always shares branding banners, company’s announcements, polls, calendars… common information which goes often in sidebars, while the content belongs to the unique site. So whether I want to share the pages as a way to reduce the points where those pages are edited has nothing to do with this topic about sharing the widgets.

So, about 99%…

I always had a good eye for statistics and for “guessing” a number of things with a single look, like Rayman, hehe, and although I agree that I’m not the most common case for a “single wordpress site”, we are talking about multisite in this forum, and 99% of multisites need branding and common information across sites. Otherwise, there wouldn’t be a reason to have them under the same umbrella. Can you name a network that doesn’t share anything across sites? Wouldn’t that info be most probably on a widget in the sidebar?

Rainman was actually Tom Cruise’s character, the ‘normal’ guy, not Dustin Hoffman’s autistic. (Yes, that bugs me when everyone and their mother get that backwards ?? )

A network always shares branding banners, company’s announcements, polls, calendars… common information which goes often in sidebars, while the content belongs to the unique site.

No. Not a NETWORK. At least not in WP terms. You’re confusing terminology that is, to be fair, confusing enough as is ??

A network means “A network of WordPress blogs, all of which run off of one WP install, creating the MultiSite Network.”

You’re thinking like Sharepoint Networks (i.e. all sites under the umbrella). Nothing wrong with that, but that isn’t how it works. And honestly, that’s a situation where I would stop to think if I need separate full-blown sites or not. You do need to stop thinking about those terms in a locked way that ‘Network == shared content’ because that’s not how WE use the term here ?? Savvy?

If you need sites to share content like ‘about pages’ then I would hard code it into the theme so they can’t remove the link, and have it all link back to the parent site. Or use a network-wide footer/header ( https://wpmututorials.com had a tute on that one). But you want to take the ability to change things away from the sites if that’s your desire, because if they can change it, they will, and you’ll spend more and more time wasted trying to lock MultiSite down, making it do what it’s not intended to do, than actually using the product.

Look into Custom Post-Types, or categories, or the possibility that maybe not every site needs to be a cookie-cutter ??

Gosh! I’ve just lost the money for “classical movies for $500” ??
I though it was Ray, not rain, also.

Well, my idea of network, you’re right, I’m thinking on “websites” to save wp framework, not just blogs…?but I can’t think of a network (I can find a different name if that bothers you or confuses the creators) that has no branding or shared items.

Now, again, this topic was about widgets sharing / saving their settings for MAY BE being used again in another site of the same network. Let’s steer away from the shared content since it’s a very specific case I pulled out to make editions easier.

I’ve already got it working with threewp broadcast, and except by the fact I can’t re-link an already unlinked page to/from its parent, it works fine. You can see one of the child sites at coverallatlanta.com (main content site dns doesn’t resolve from external http).

and 99% of multisites need branding and common information across sites.

Then put in a common header and footer.

Tip: it’s not saved in the db.

https://wpmututorials.com/plugins/how-to-hook-into-the-footer/

Widgets. Remember?
If I had the time to create custom calendars, polls, or to force other WIDGETS to work multisite, or by placing a function in the header or footer, I’d do that.

In the while, if the title of this topic didn’t say it, I’ll specify the scenario this post refers to:

• Many sites, same network
• Common WIDGETS, hard to custom program
• Although they share settings, the widget itself needs to work on child-site data/environment
• You WILL have the plugin installed, so tables will be there.
• You STILL have to go widget by widget to setting them up.
• Copying-pasting the values automatically would help, but the maintenance would be difficult.

In this scenario, not uncommon, soon with more people following the predicted future for WP, will need this feature.

You can name this feature after me ??

If you can write it, we may.

Widgets are per theme (or plugin) which are customized per site. There are no plans to change this at this time. WordPress has a bit of an 80/20 rule. If more than 20% of the MultiSite users start pushing for this, it may change, but it won’t be real soon.

I love the 80/20. That’s my bible!

Although I’ve seen people making the 100 up with something unrelated to the 80. e.g. “Lingerie is not important for human beens. Yet, it is for woman.”

In other words, saying wp is 80% single sites, not multisites, makes people who want cross-site “copy/paste” widget settings a mute voice in the ocean, but considering 99% of multi-sites will use shared content, now the 80/20 is met.

See? it depends what the 100 is made of.

I really don’t think WP is intended only for developers. Without widgets and end-user tools it wouldn’t have grown the way it did, so developing custom content in the header and footer is not the way for me. Widgets are STILL what makes WP live and grow, and helping to manage them across many sites is the future. You’ll see.

It’s not neccesary going too far trying to make all widgets cross-network when they are not ment for that. I wouldn’t even think about the crazy useless mission that would be. Remembering settings cross-site or allowing “copy settings” and pasting it in another site would make widgets more desired for multisites.