Opened 7 months ago

Closed 4 weeks ago

#22140 closed enhancement (fixed)

fetch_feed parameter is documented incorrectly

Reported by: tlovett1 Owned by: nacin
Priority: normal Milestone: 3.6
Component: Inline Docs Version: 2.8
Severity: normal Keywords: has-patch commit
Cc: td@…

Description

The fetch_feed function in wp-includes/feed.php is documented to allow one parameter of type string. fetch_feed passes that parameter to the set_feed_url method of a newly created SimplePie object. However, set_feed_url can accept a URL string or an array of URL's. Therefore, fetch_feed should be documented as having one parameter of mixed type (string OR array).

Attachments (4)

fetch_feed_mixed_params.diff (1.1 KB) - added by tlovett1 7 months ago.
A patch that updates the documentation for the fetch_feed method as well as renames the parameter.
22140.1.diff (1.2 KB) - added by JustinSainton 3 months ago.
22140.2.diff (1.5 KB) - added by JustinSainton 7 weeks ago.
22140.3.diff (1.3 KB) - added by JustinSainton 6 weeks ago.

Download all attachments as: .zip

Change History (21)

A patch that updates the documentation for the fetch_feed method as well as renames the parameter.

  • Summary changed from fetch_feed parameter is misdocumented to fetch_feed parameter is documented incorrectly
  • Cc td@… added
  • Component changed from Feeds to Inline Docs
  • Version changed from trunk to 2.8
  • Milestone changed from Awaiting Review to 3.6

Thinking URLs doesn't need the apostrophe here?

comment:7 follow-up: ↓ 8   SergeyBiryukov2 months ago

Not sure if we should advertise that $url can be an array here. See http://simplepie.org/wiki/faq/typical_multifeed_gotchas.

comment:8 in reply to: ↑ 7   nacin2 months ago

Replying to SergeyBiryukov:

Not sure if we should advertise that $url can be an array here. See http://simplepie.org/wiki/faq/typical_multifeed_gotchas.

I'd be inclined to agree as well.

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

-1 on wontfix. Multifeeds are used so popularly that they're basically the main way to use SimplePie.

The only real gotchas with using them are that the feed-level accessors don't make sense, since you're operating on a group rather than on a single feed. For the next version of SimplePie, I'm working on making this clearer to users, but it's fairly obvious when you try and use them anyway.

comment:11 follow-up: ↓ 14   nacin7 weeks ago

Okay, but let's tweak it a bit. Maybe something like:

@param mixed $url URL of feed to retrieve. If an array of URLs, the feeds are merged using SimplePie's multifeed feature. See also {@link http://simplepie.org/wiki/faq/typical_multifeed_gotchas}.

The "see also" is optional.

Refreshed with nacin's suggestions.

  • Milestone set to 3.6
  • Resolution wontfix deleted
  • Status changed from closed to reopened

comment:14 in reply to: ↑ 11   rmccue6 weeks ago

Replying to nacin:

Okay, but let's tweak it a bit. Maybe something like:

@param mixed $url URL of feed to retrieve. If an array of URLs, the feeds are merged using SimplePie's multifeed feature. See also {@link http://simplepie.org/wiki/faq/typical_multifeed_gotchas}.

The "see also" is optional.

Sounds good.

Patch looks OK, but $url is used in the documentation, whereas $urls is used in the prototype. The see also has to also be on the same line (from memory).

  • Keywords dev-feedback added
  • Keywords commit added; dev-feedback removed
  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from reopened to closed

In 24054:

Document that fetch_feed() can accept multiple URLs, thus leveraging SimplePie's multifeed feature. props JustinSainton, fixes #22140.

Note: See TracTickets for help on using tickets.