Make WordPress Core

Opened 16 years ago

Closed 14 years ago

Last modified 2 years ago

#7650 closed enhancement (maybelater)

Multiple post authors

Reported by: radzio's profile radzio Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.7
Component: Users Keywords: dev-feedback
Focuses: Cc:

Description

I run sport blog with over 10 people. Sometimes 2 or more authors want to write post together. There is some plugins which adds this functionality but I think that Wordpress should have this built-in.

Change History (20)

#1 @Viper007Bond
16 years ago

  • Milestone set to 2.9
  • Version set to 2.7

I think an easier solution would be to allow contributors to posts. The database structure is kinda set up for just one author, but we could store contributors in the post meta.

#2 @Denis-de-Bernardy
15 years ago

  • Component changed from General to Users
  • Owner anonymous deleted

#3 follow-up: @Denis-de-Bernardy
15 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

this would require schema changes that translate into severe inefficiencies when running queries.

and you can do this with a plugin using the postmeta table, as indicated by Viper.

#4 in reply to: ↑ 3 @Viper007Bond
15 years ago

Replying to Denis-de-Bernardy:

this would require schema changes that translate into severe inefficiencies when running queries.

Couldn't there just be a new taxonomy for authors? Much like how tags or categories are applied to a post, authors could be applied the same way.

#5 @Denis-de-Bernardy
15 years ago

well, picture an NDB cluster for a sec (as I have), with a user trying to grab posts with authors A or B and tag C and D and category E or F.

you've posts join user2post join users join term_relationships join term_relationships join term_relationships with or clauses. your cluster is dead... :-)

(the taxonomy schema is dead wrong from the onset, in that the terms table should be merged into the term_taxonomy table, and the term_taxonomy field should ideally be an enum for optimization purposes, but that would be for a separate, faraway ticket.)

#6 @Denis-de-Bernardy
15 years ago

that being said, if the taxonomies do get fixed, then this ticket will make more sense -- but it's a huge workflow.

#7 @computerwiz908
14 years ago

  • Cc computerwiz908@… added
  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Version changed from 2.7 to 3.0.4

I am reopening this ticket to see if this functionality is possible at this point in time. If WordPress wants to market itself as a CMS, then it should incorporate the capability to have multiple authors for one post.

#8 @ocean90
14 years ago

  • Keywords dev-feedback added
  • Milestone set to Awaiting Review
  • Version changed from 3.0.4 to 2.7

It should be done by a plugin, Co-Authors Plus is one for example.

#9 @computerwiz908
14 years ago

  • Version changed from 2.7 to 3.0.4

However, this should be a core functionality. The inability to have multiple authors in one post inhibits, say, news organizations' abilities to tag their articles by author when there are multiple authors.

#10 @ocean90
14 years ago

  • Version changed from 3.0.4 to 2.7

Please don't change the reported version to a newer version. Then we lose the history of when the *bug* was identified.

#11 follow-up: @nacin
14 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from reopened to closed

As indicated, this is plugin material. It doesn't apply to most users and works great as a plugin.

#12 @mikeschinkel
14 years ago

  • Cc mikeschinkel@… added

#13 @ocean90
12 years ago

#23440 was marked as a duplicate.

#14 in reply to: ↑ 11 ; follow-up: @rubberduck
12 years ago

Replying to nacin:

As indicated, this is plugin material. It doesn't apply to most users and works great as a plugin.

It probably "doesn't apply to most users" because the users who need it don't bother telling WP about it - they just tell their manager/boss that WP doesn't support X, Y, and Z and they should therefore spend $xx,xxx on an enterprise CMS that does everything they need. Honestly I and my clients would pay for a Premium version of WP (if there was one) if it had some of these more advanced features. WP is in fact better than some enterprise CMS, but it does lack a few such essential features.

#15 in reply to: ↑ 14 ; follow-up: @rubberduck
12 years ago

Replying to rubberduck:

Replying to nacin:

As indicated, this is plugin material. It doesn't apply to most users and works great as a plugin.

It probably "doesn't apply to most users" because the users who need it don't bother telling WP about it - they just tell their manager/boss that WP doesn't support X, Y, and Z and they should therefore spend $xx,xxx on an enterprise CMS that does everything they need. Honestly I and my clients would pay for a Premium version of WP (if there was one) if it had some of these more advanced features. WP is in fact better than some enterprise CMS, but it does lack a few such essential features.

p.s. the Co-Authors plugin might be functional, but it hasn't been updated 2 years. If it becomes incompatible with some future version of WP or PHP and my client decides "hey why don't I upgrade my WP - it's telling me there's an update", I will be the one who will end up spending several hours trying to fix someone else's plugin. It's not the end of the world, but that is one reason why many professional users don't use WordPress.

#16 in reply to: ↑ 15 ; follow-up: @helen
12 years ago

Replying to rubberduck:

p.s. the Co-Authors plugin might be functional, but it hasn't been updated 2 years.

The plugin you were pointed to on #23440 was Co-Authors Plus, which had a new version released about a month ago, is regularly maintained, and quite actively used.

#17 in reply to: ↑ 16 @rubberduck
12 years ago

Replying to helen:

Replying to rubberduck:

p.s. the Co-Authors plugin might be functional, but it hasn't been updated 2 years.

The plugin you were pointed to on #23440 was Co-Authors Plus, which had a new version released about a month ago, is regularly maintained, and quite actively used.

Nice, thanks!

#18 @sabernhardt
3 years ago

#48023 was marked as a duplicate.

#19 @sabernhardt
3 years ago

#54242 was marked as a duplicate.

This ticket was mentioned in Slack in #core by sabernhardt. View the logs.


2 years ago

Note: See TracTickets for help on using tickets.