Changeset 44894
- Timestamp:
- 03/13/2019 07:31:49 PM (6 years ago)
- Location:
- trunk/src/wp-includes
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/wp-includes/cache.php
r44601 r44894 647 647 * Sets the data contents into the cache. 648 648 * 649 * The cache contents isgrouped by the $group parameter followed by the649 * The cache contents are grouped by the $group parameter followed by the 650 650 * $key. This allows for duplicate ids in unique groups. Therefore, naming of 651 651 * the group should be used with care and should follow normal function -
trunk/src/wp-includes/class-json.php
r43325 r44894 806 806 (($this->strlen8($this->substr8($chrs, 0, $c)) - $this->strlen8(rtrim($this->substr8($chrs, 0, $c), '\\'))) % 2 != 1)) { 807 807 // found a quote, we're in a string, and it's not escaped 808 // we know that it's not escaped beca se there is _not_ an808 // we know that it's not escaped because there is _not_ an 809 809 // odd number of backslashes at the end of the string so far 810 810 array_pop($stk); -
trunk/src/wp-includes/class-smtp.php
r39759 r44894 565 565 * Send an SMTP DATA command. 566 566 * Issues a data command and sends the msg_data to the server, 567 * fin ializing the mail transaction. $msg_data is the message567 * finalizing the mail transaction. $msg_data is the message 568 568 * that is to be send with the headers. Each header needs to be 569 569 * on a single line followed by a <CRLF> with the message headers 570 * and the message body being separated by an dadditional <CRLF>.570 * and the message body being separated by an additional <CRLF>. 571 571 * Implements rfc 821: DATA <CRLF> 572 572 * @param string $msg_data Message data to send -
trunk/src/wp-includes/comment-template.php
r44659 r44894 103 103 * 104 104 * Care should be taken to protect the email address and assure that email 105 * harvesters do not capture your comment ors'email address. Most assume that105 * harvesters do not capture your commenter's email address. Most assume that 106 106 * their email address will not appear in raw form on the site. Doing so will 107 107 * enable anyone, including those that people don't want to get the email … … 134 134 * 135 135 * Care should be taken to protect the email address and assure that email 136 * harvesters do not capture your comment ors'email address. Most assume that136 * harvesters do not capture your commenter's email address. Most assume that 137 137 * their email address will not appear in raw form on the site. Doing so will 138 138 * enable anyone, including those that people don't want to get the email … … 158 158 * 159 159 * Care should be taken to protect the email address and assure that email 160 * harvesters do not capture your comment ors'email address. Most assume that160 * harvesters do not capture your commenter's email address. Most assume that 161 161 * their email address will not appear in raw form on the site. Doing so will 162 162 * enable anyone, including those that people don't want to get the email -
trunk/src/wp-includes/taxonomy.php
r44755 r44894 2667 2667 * hierarchical and has a parent, it will append that parent to the $slug. 2668 2668 * 2669 * If that still doesn't return a n unique slug, then it tryto append a number2669 * If that still doesn't return a unique slug, then it tries to append a number 2670 2670 * until it finds a number that is truly unique. 2671 2671 * … … 4128 4128 * @param int $term_id Term ID. 4129 4129 * @return bool Returns false if a term is not shared between multiple taxonomies or 4130 * if splitt ng shared taxonomy terms is finished.4130 * if splitting shared taxonomy terms is finished. 4131 4131 */ 4132 4132 function wp_term_is_shared( $term_id ) { -
trunk/src/wp-includes/theme.php
r44613 r44894 3058 3058 * changesets by default get garbage collected due to the auto-draft status. 3059 3059 * When a changeset post is published, however, it would no longer get cleaned 3060 * out. Th s is a problem when the changeset posts are never displayed anywhere,3060 * out. This is a problem when the changeset posts are never displayed anywhere, 3061 3061 * since they would just be endlessly piling up. So here we use the revisions 3062 3062 * feature to indicate whether or not a published changeset should get trashed
Note: See TracChangeset
for help on using the changeset viewer.