Allow Admin to define default domains in posts

Created on 17 May 2011, over 13 years ago
Updated 3 September 2024, 4 months ago

First up WONDERFUL, absolutely WONDERFUL module.

1) I run local community publishing for a few towns.

READERS want to stay on their Likal, no matter where the content was published from. SoI need people to choose "use active domain" when posting.

I want to FORCE this, or at least set this as default, (is there one?), so that Readers don't get bounced from one domain to another.

2) To help local editors control their sites I would like Admin to be able to define default "publish to" on a user by user basis. If content was automatically published to "domain I'm in" plus other domains set by me in their user account.

So Gloucester Editor publishes "Blues Festival July 2011" and by default it publishes to Gloucester (domain posted in) AND Gloucestershire (because I've made that a default for that user).

Purpose is twofold - SEO will be sent to the Gloucestershire domain and robots blocked at local level, AND all Editors will have access to the Gloucestershire domain. They can monitor content and add their domain to it if they want to show it in their domain. In the example above the other Editors would add the Blues Festival to their site because it's important.

This would NOT affect the ability of users to do normal domain selection, for example if Gloucester has posting rights in next door Cheltenham he can tick that box while creating as well.

That said, most Editors would only have publishing rights to their domain and County.

Worked example

Gloucester Editor gets on well with Cheltenham and Stroud, so has posting rights to :-

Gloucester
Gloucestershire
Cheltenham
Stroud

When he creates a post (which will always be from inside Gloucester) the defaults should be :-

Publish to

Gloucester
Gloucestershire

Source
Use Active Domain

Whilst allowing him to choose to publish to Cheltenham and/or Stroud if he wishes.

Cheers

Feature request
Status

Closed: outdated

Version

3.0

Component

Code

Created by

🇬🇧United Kingdom iandickson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

    I'll close this issue due to inactivity for 13 years and upcoming EOL of Drupal 7 in January 2025 . While the project's version for Drupal 7 will surely keep providing support for security issues and website breaking bug fixes for Drupal 7, we should try to minimize the open issues for Drupal 7 in the queue as much as possible. A big thanks around for the report and all the efforts in here. Feel free to re-open if you can provide a fix or found an additional related problem which increases the issue priority.

Production build 0.71.5 2024