回答編集履歴
2
追記
answer
CHANGED
|
@@ -6,8 +6,9 @@
|
|
|
6
6
|
> 1, get_header hook would be gone;
|
|
7
7
|
2, compatibility with fetching different headers by name ("header-{$name}.php") would be gone;
|
|
8
8
|
3, usage of locate_template() would be gone, which likely would destroy compatibility with child themes.
|
|
9
|
-
4, You can always look at source to see what exactly function does.
|
|
10
9
|
|
|
10
|
+
> You can always look at source to see what exactly function does.
|
|
11
|
+
|
|
11
12
|
> WordPress uses own function not just-because. It is usually for concrete compatibility or functionality reasons.
|
|
12
13
|
|
|
13
14
|
一部修正してます。
|
1
追記
answer
CHANGED
|
@@ -3,9 +3,11 @@
|
|
|
3
3
|
|
|
4
4
|
> Using generic function means throwing out layer of WP API:
|
|
5
5
|
|
|
6
|
-
>
|
|
6
|
+
> 1, get_header hook would be gone;
|
|
7
|
-
|
|
7
|
+
2, compatibility with fetching different headers by name ("header-{$name}.php") would be gone;
|
|
8
|
-
|
|
8
|
+
3, usage of locate_template() would be gone, which likely would destroy compatibility with child themes.
|
|
9
|
-
|
|
9
|
+
4, You can always look at source to see what exactly function does.
|
|
10
10
|
|
|
11
|
-
> WordPress uses own function not just-because. It is usually for concrete compatibility or functionality reasons.
|
|
11
|
+
> WordPress uses own function not just-because. It is usually for concrete compatibility or functionality reasons.
|
|
12
|
+
|
|
13
|
+
一部修正してます。
|