From df4b849b300deac56249e397a26b33d32eb3543d Mon Sep 17 00:00:00 2001 From: Simon East Date: Fri, 23 Jun 2017 17:14:31 +1000 Subject: [PATCH] Updated README to make note of existing Neo field issue Thought it might be helpful to alert users to lack of Neo support, before they download and install it. I know that for our agency, Neo is one of the core plugins we almost always use, and it's also one of the key reasons we were looking for a way to import/export fields because they can take so long to setup. :-P --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index f796713..6fcef6a 100644 --- a/README.md +++ b/README.md @@ -77,6 +77,13 @@ Using the Import tab, you paste in your JSON file contents that you created thro ...and many more. Field Manager can handle just about any FieldType, the above are simply those that have been tested. +## Known Issues + +* **Neo Fields** - although *cloning* of Neo fields appears to work, import and export is not currently supported. [#37](https://github.com/engram-design/FieldManager/issues/37) + +Why not help out with this functionality and send a pull request? [Learn how](https://help.github.com/articles/about-pull-requests/). + + ## Bugs, feature requests, support Found a bug? Have a suggestion? [Submit an issue](https://github.com/engram-design/FieldManager/issues)