Once you run more than one membership site, the same job turns up again and again: upload the new set to site one, then to site two, then edit the page on site three. Every site keeps its own copy of the files, the copies drift apart, and a correction made in one place has to be repeated everywhere else. Storage use grows with every site you add.
A central content library turns this around. Content lives in one place, and each members area asks that library for the content it should show. The piece that makes this work on each website is usually called a connector. This guide explains what a connector does, what it should and shouldn't change on your sites, and how to set one up with confidence.
What a connector does
A connector is a small set of files placed in a website's members area. When a member opens a page, the connector asks the central library for the content that belongs on that site, then shows it using the site's own page design. It typically handles:
- Fetching the list of galleries, videos or stories for the site.
- Showing an individual gallery, video or story when a member opens it.
- Producing safe links to the media files so members can view them.
- Recognising which member is logged in, using whatever login the site already has.
The important point is what the connector leaves alone. Your billing processor, sign-up pages and member accounts stay exactly as they are. The connector only replaces the job of keeping content on each site up to date.
Why not just copy the files to every site?
Copying feels simple, but it gets harder with every site and every set:
| Copying files to each site | Central library with connectors | |
|---|---|---|
| Storage | One copy per site | One copy in total |
| Fixing a title or photo | Repeat on every site | Change once, every site follows |
| Adding a new site | Upload the whole back catalogue again | Register the site and set its categories |
| Removing content | Find and delete each copy | Unpublish once |
| Knowing what is where | Check each site by hand | The library shows which sites each item reaches |
Deciding what each site shows
With one library feeding many sites, each site needs rules for what it receives. The usual approach is categories: a cooking site might ask for Baking and Desserts, while a travel site asks for Beaches and City Breaks. Content tagged with the right categories appears on the right sites automatically, and anything tagged with a category a site excludes never appears there. Our guide to Match ALL, ANY and Preferred + Filler explains the different ways those rules can work.
It also helps if only finished content goes out. Drafts and work in progress should stay in the library until they are ready, so a half-edited set never shows up in a members area by accident.
Keeping the connection secure
Because the connector talks to the library over the internet, the conversation between them needs protecting. Look for these basics:
- Separate credentials for each website, so one compromised site cannot pretend to be another.
- Signed requests, so the library can check every request really came from that website and was not altered on the way.
- A short time window, so a captured request cannot be replayed later. This is also why the clocks on both servers need to be roughly right.
- Media links that are protected, so a file address copied out of a members area does not work forever. Our guide on serving member media from the same server or a different one covers the options.
Setting up a connector step by step
- Register the website in the central library and choose its categories and content types.
- Download the connector for that site, with its settings already filled in.
- Copy it into the site's members folder using SFTP or your hosting file manager.
- Open the connector's self-check page and fix anything it flags.
- Log in as a member and browse the new pages to check content and design.
- Adjust the design to match the rest of the site, then link the new pages from your members menu.
Take a moment over login recognition. The connector has to know how your site protects its members area, whether by a password folder, a session or something else. Our guide to members area login methods explains each choice.
How Members CMS handles this
In Members CMS, go to Members Areas > Connector Management and download a ready-configured connector for each website, with its settings file already filled in. Copy it into the site's members folder. It includes a members home page, galleries list, gallery, movies list, movie, stories list and story page. The default design lives in the templates/ folder, with theme.php for your logo and colours, and your templates are never overwritten by updates.
The self-check page at members/mcms/check.php tests the PHP version, the settings file, the cache folder, the connection and clock, whether the member login is recognised and whether content is available. The connector needs PHP 7.2 or newer and can sit on the same server as Members CMS or a different one. Nothing is copied to the websites, every request is signed with HMAC-SHA256 within a 5-minute window, each website has its own credentials, and only Published content that matches the site's category rules is shown.
Frequently asked questions
Do the media files get copied to each website?
No. The files stay on the central server. Each website shows them through links that expire, or straight from the storage folder if the site is on the same server.
Does the website need the same PHP version as the CMS?
No. The connector needs PHP 7.2 or newer, so older paysite servers can still use it.
How do I check the connection works?
Open the connector's self-check page. It tests the PHP version, the settings file, the cache folder, the connection and clocks, the member login and whether there is content to show.
