You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-15Lines changed: 17 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,6 @@ WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-
7
7
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
8
8
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
9
9
10
-
11
-
### Reasons to start this project
12
-
13
-
* Advanced custom fields did not interface with WP-CLI
14
-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
15
-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
16
-
* Naming convention for XML files was always the same, resulting in renaming hassle.
17
-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.
18
-
19
10
## Installation
20
11
21
12
@@ -27,18 +18,27 @@ Fields can now easily be imported, exported and shared over SVN, GIT or comparab
27
18
28
19
### How to install
29
20
30
-
Install WP-CLI as described on [their website](http://wp-cli.org/"WP-CLI")
21
+
Install WP-CLI as described on [http://wp-cli.org/](http://wp-cli.org/"WP-CLI")
Copy file name to clipboardExpand all lines: readme.txt
+17-14Lines changed: 17 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,6 @@ Manage Advanced Custom Fields through WP-CLI
14
14
WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-CLI.
15
15
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
16
16
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
17
-
18
-
= Reasons to start this project =
19
-
20
-
* Advanced custom fields did not interface with WP-CLI
21
-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
22
-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
23
-
* Naming convention for XML files was always the same, resulting in renaming hassle.
24
-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.
25
17
== Installation ==
26
18
27
19
= Requirements =
@@ -31,18 +23,27 @@ Fields can now easily be imported, exported and shared over SVN, GIT or comparab
31
23
32
24
= How to install =
33
25
34
-
Install WP-CLI as described on [their website](http://wp-cli.org/ "WP-CLI")
26
+
Install WP-CLI as described on [http://wp-cli.org/](http://wp-cli.org/ "WP-CLI")
Copy file name to clipboardExpand all lines: readme/description.txt
-8Lines changed: 0 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,3 @@
5
5
WP-CLI for Advanced Custom Fields helps you manage your field-groups through WP-CLI.
6
6
The reason we started this project is to make life easier for developers working on Wordpress projects using the Advanced Custom Fields Pro plugin.
7
7
Fields can now easily be imported, exported and shared over SVN, GIT or comparable systems.
8
-
9
-
= Reasons to start this project =
10
-
11
-
* Advanced custom fields did not interface with WP-CLI
12
-
* Sharing field-groups through XML or PHP code caused problems with differences between development, test, staging and production enviroments when shared with XML.
13
-
* No direct SVN or GIT support without manually putting the exported PHP or XML into a versioned directory.
14
-
* Naming convention for XML files was always the same, resulting in renaming hassle.
15
-
* Only using the generated field-groups on runtime through PHP code in functions.php disables the editing mode (which is an awesome UI that we require). So importing should be possible.
0 commit comments