Rather than attempt this with ACF, I would do this with CSS. You can wrap the field in a div, like this:
<div class="my-wysiwyg">
<?php the_field('my_wysiwyg');?>
</div>
Then just apply the styling to the last <p> tag with CSS:
.my-wysiwyg p:last-child {
font-size: 30px;
}
Does that help?
This is awesome! Between this and the new block layout for flex fields, I’m very happy today!
You should consider SearchWP – it can index custom fields and integrates very well with ACF. You can even expand relationship fields within your search index – pretty neat!
https://searchwp.com/docs/hooks/searchwp_custom_fields/
Thank you! I appreciate it.
Agreed – I would love an easier way to lay out custom fields in the admin. A simple example is when a post type has “start date” and “end date” fields. I’d love to easily display those side by side with a ‘left_half” and “right_half” class. I can handle adding the CSS to the WP admin, but it’s so hard to target specific fields based on their IDs.
This raises a good question – I would like to downgrade to 5.0.4 temporarily, but I can’t find a release archive. Does anyone know where to find previous versions of the plugin?
I can verify that I’m using both (latest versions) together successfully. There may be a third plugin or a theme issue causing the conflict. I would recommend the following steps:
Disable all of your plugins except Gravity & ACF. Switch over to the default theme. Can you create a new form now?
If so, switch to your custom theme and try again. Then, enable your plugins one by one until you find the culprit.
Hope that helps!
Dalton
Sorry, this looks like a duplicate of http://support.advancedcustomfields.com/forums/topic/cant-use-conditional-fields-after-last-update/ and http://support.advancedcustomfields.com/forums/topic/conditional-logic-not-working/
Let’s try to consolidate this to one thread.
I’m having the same problem with any new fields I try to create. My previously created conditional fields still work.
Version 5.0.1 Pro, trying to create a conditional field based on the value of a select field above.
Adding my report to this thread, I just noticed this behavior too! Lovely update otherwise.
Cheers,
Dalton
This is really interesting: https://uproot.us/addons/revisions/
I believe Custom Field Suite is a fork of an older version of ACF, so it may be possible to port this add-on over to ACF.
FYI, it looks like this might make it into WP Core at some point, but who knows how long that will take…
http://core.trac.wordpress.org/ticket/20564
I’m also having the problem with custom fields not being saved to revisions when the post content is not changed. As soon as I modify the main post content, the changes to the custom fields are also saved.
WP 3.6 & ACF 4.2.2.
I’ve only been able to reproduce this in WP Engine, not on a local site with Super Cache enabled.
I think the key is that the feature is called “Transient/Object Cache”. Elliot, do you use transients to store any temporary data when editing fields?
I’d say that it’s worth posting a support ticket about it. If they get enough of them, they may do something about it.
@Full Circle Design: That seems to be correct – you need to disable the Object/Transient Cache fully to modify the fields, otherwise it takes changes a few minutes to show up in the admin.
I didn’t know WP Engine was caching wp-admin, this seems like it would create more problems than it’s worth, in my opinion.
@Full Circle Design: Christian at WPEngine just did a “reset permissions” for my account and it seems to have fixed the problem. The function is available under the “WPEngine” tab on your WordPress dashboard. Hope that helps!
I have a ticket open with WP Engine, #124043
We loaded the site up on a staging server and didn’t experience any problems, so it looks like something’s up with WP Engine’s admin caching. I’ll let you know when I have more info.
I’m not running any cache plugins, but the site is on WP Engine, which does cache the front-end aggressively. I didn’t know they cache on the back-end too.
I have a local copy of the site I’m working on and just checked – it looks like ACF is working as it should on the local site, but not on the WP Engine site. So I guess this might be a WP Engine issue, I’ll check in with them.
I think it’s just a matter of taste. Sometimes removing the metabox looks cleaner, especially if you’re hiding most of the built-in WP metaboxes and creating a long list of fields. But you shouldn’t have any problem using them in either configuration.
It sounds like you’re using a field group with the “No Metabox” style. If you temporarily change the field group to use the standard WordPress metabox, you can then drag it out of the sidebar. Once it’s in the normal position, you can change the metabox option back.
I’ve experienced this many times – once you’ve loaded a page with a set of fields, the order and position of those fields is fixed, even if you try to change it in the ACF admin. You need to enable the metabox handles to drag and drop them into the order you want.
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.