+1
What if rather than creating a process that loops through every single post trying to cleanup old orphaned meta values, the plugin instead cleaned up values no longer in use when the post was edited/saved?
This wouldn’t give you the 1 click solution but, it would cause the database to clean and improve itself over time.
Has any new DB optimization plugin been created since the inception of this question that is capable of cleaning up these meta values? I assume not since the values aren’t orphaned… right?
How do we know what is coming in version 5.6? Does Elliot list upcoming release features somewhere?
I replied with a screen recording to the support email thread. Thanks again.
What is the feature request forum for?
The idea/spirit of this code works but, in actuality, it does not work when you first click page > add new and switch to a new template. This is because, the fields are not there as soon as you fire the .on change (it takes a second).
When that .on change event tries to append the #postdivrich, the message placholder has not yet been lazy loaded onto the page. See what I mean?
The trigger needs to happen _after_ the acf field group is loaded onto the page — NOT after the #page_template select changes.
BTW, my first crack at this was almost exactly the same code you just posted. This is why I suggested making it a feature. What we really need access to is code that fires after the fields are loaded.
I created a feature request if you’d like to pile on. I assume someone else has also created one but, I cant find it.
+1
I would love the ability to not only have “other” but, that other be permanently added to the list of future choices. This would work like post categories. There is a list of checkboxes but, there is also a link to add a new category to the list on the fly.
If there is another feature request like this, I would like to vote and follow it!
I already gave it a whirl. The problem is getting the content editor to jump around each time you change the layout/template. Things have to happen when the ACF fields are lazy loaded.
Can we move this to feature requests? Or should I create a new post?
Adding the following css to the backend seems to work for me;
.acf-image-uploader .view {
width: 150px;
height: 150px;
background-color: #dddddd;
As @eterps says…
I make no guarantees for you, as it may completely blow up your site and ruin your life forever. You’ve been warned.
Adding the following css to the backend seems to work for me;
.acf-image-uploader .view {
width: 150px;
height: 150px;
background-color: #dddddd;
I am having the same issue.
@eterps is there any chance you could post that javascript snippet you added to your function file? It would be greatly appreciated.
+1 I am also experiencing this issue.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.