I will update the README.md file with this manual 🙂
Please, keep in mind that the plug-in works best when there is a solid “prefix” for your ACF-entries in the database.
Something like ACF__logotype / ACF__reviews / ACF__4901-31A, etc…
When you do not have a consequent prefix, the plug-in is unable to find all ACF-fields available.
That’s kinda weird…
Is the plugin menu-entry nested inside the tools-sections, like this;
Or not at all?
Maybe it’s a conflict with another plugin?
The issue you describe looks a bit like this (solved) one;
https://github.com/1n3JgKl9pQ6cUMrW/acf-cleaner/issues/1
Well, technically that’s an error 🙂
The page / URL should be something like this;
https://DOMAINNAME.EXTENSION/wp-admin/tools.php?page=acf-cleaner%2Facf-cleaner-admin.php
And the page requested should be on your server (check it by (s)FTP) like this;
/public_html/wp-content/plugins/acf-cleaner/acf-cleaner.php
Of course the last part (/wp-content/…) is the most important for now.
Are you sure this has something to do with WP5.x?
I checked the plugin against a couple of WP5.x sites and the plugin did work.
Maybe something else is wrong?
Can you provide an error message or “something that did not work out as aspected” ?
Is it possible the other way around?
Imagine this set-up;
- I create a text-field in English
- I set it to be ‘required‘ *
- I duplicate the text-field to Italian
- I change my mind; the feeld is not required
- I set it (in English) to ‘not required‘
- …the Italian version must automatically sync this adjusted setting and also set to ‘not required‘
So the display-logic / conditional-logic is only changed in the ‘parent fieldgroup’ and all the translated-versions must be synced automatically with the new logic.
I noticed the exact same behavior (ACF 5.5.6 / .7 / .8 and .9).
You can not alter a “child” language, without messing it up.
No problem when altering the “parent” language – only with non-primary languages.
– update – You can now set your own record-prefix (defaults to ACF__) for the field #ID’s.
Well, I don’t care about “some” useless entries 🙂 but your database can really become huge, when not cleaning up some stuff.
I am now adding a new feature to this plug-in (so you can use it without a fixed prefix) and (as a test) deleted one ACF field… I ended up with over 60 orphaned entries…
So I am happy with the option to delete those records – when I delete a field, I also want to delete the values (I realize this is not for everyone, but I want to have the choise).
I was looking for it as well;
ACF is great, but it really meshes up your database.
It even creates empty records (two for every entry) of empty values and it’s revisions… when you save an empty value and do some revisions on the same page, your database will explode with useless entries.
The project started as a stand-alone script (outside the WP environment), than I decided to run it by cronjobs, after that I realized it was more easy to wrap it into a plug-in.
So that’s why the code is a mix of plain-vanilla PHP and some WP-API’s 🙂
The only restriction is that your field-ID’s are prefixed with “ACF__” or “acf__” because I use this as an identifier for the queries.
Feel free to port; it’s completely open source.
