[wp-trac] [WordPress Trac] #41619: Fix documentation issues for `domain_exists()`
WordPress Trac
noreply at wordpress.org
Mon Aug 21 04:24:22 UTC 2017
#41619: Fix documentation issues for `domain_exists()`
--------------------------------------+------------------------------
Reporter: flixos90 | Owner: stevenlinx
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: 4.9
Component: Networks and Sites | Version:
Severity: normal | Resolution:
Keywords: good-first-bug has-patch | Focuses: docs, multisite
--------------------------------------+------------------------------
Comment (by DrewAPicture):
Hmm. I think introducing the new terminology actually confuses it a bit
more. You're correct that `domain_exists()` ''literally'' checks the
domain path, though "domain-path" doesn't really convey what the domain
path represents the way blogname sort-of does currently.
Rather than introduce new vernacular, I wonder if simply providing context
for what "blogname" represents in the DocBlock description wouldn't be
more consistent with the rest of core. For instance, in the `newblogname`
hook doc, the explanation of what the [blog] name represents is pretty
clear:
{{{
* Filters the new site name during registration.
*
* The name is the site's subdomain or the site's subdirectory
* path depending on the network settings.
*
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/41619#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list