I’ve just pushed an update to github containing a fix for this cache issue.
Can you please update to the latest nightly build and let me know how it goes?
I’ve just pushed an update to github containing a fix for this cache issue.
Can you please update to the latest nightly build and let me know how it goes?
I’ve just pushed an update to github containing a fix for this cache issue.
Can you please update to the latest nightly build and let me know how it goes?
Hi guys.
I think the issue here is that some servers don’t understand the ‘$found’ parameter as it has not yet been created.
Can you do a search for all ‘$found’ and replace with ‘$found = false’
$found is in these files:
– api.php
– field_group.php
– _functions.php
Does this fix the issue?
Hi @Torcs
Seems like you have a good understanding of the task ahead of you. How can I help?
Hi @pasnon
I wonder if this issue has only started since updating to v4.1.7
A few other users are experiencing an issue similar to this and I will be publishing a fix soon
Hi @Wally
Your code suggests that the previous developer has a custom function to register custom fields. That or their are using another plugin to ACF as some of the parameters are missing / different.
I think some debugging is required from your end to see how the fields are registered with ACF
Hi guys.
Thanks for the info.
A few other topics today have highlighted an issue with the new cahce parameters I introduced in the 4.1.7 build.
These new parameters were to better handle cache detection but seem to be causing PHP errors!
Can you please turn on DEBUG MODE in your wp-config.php and try to load a page? I think the php error is causing the save function to fail, or the load function to fail… on or the other.
I’ll do some more testing today and find a fix
Hi @emcniece
Thanks for the feedback, Its great!
I would highly recommend using the tab field. This field will break the content into separate tabs, removing the long scroll
Hi guys.
Thanks for the bug report. This error is coming from the most recent update which used some new parameters in the cache functions.
It seems that some servers are allowing a new variable to be create on the fly and others are not.
This also explains why some people are experiencing data loss.
I’ll look into this today and release a fix
Hi @thinkwell
Yes, I need to find a solution to simple remove the update script for then developers to distribute in their themes.
If you want, you can remove the update code which contains the activation code
Hi @milan.stosic
ACF contains an export page under ‘Custom Fields’.
You can export to either .xml or .php
Hi @madsynn
You can format the date value into any format you with thanks to the great PHP date / time functions.
I have written up some code here:
http://www.advancedcustomfields.com/resources/field-types/date-picker/
And have extended it a little bit for you below:
All you need to do is change the format_out and you can do that by finding the format string here:
http://www.php.net/manual/en/function.date.php
<?php
/*
* Create PHP DateTime object from Date Piker Value
* this example expects the value to be saved in the format: yymmdd (JS) = Ymd (PHP)
*/
$format_in = 'Ymd'; // the format your value is saved in (set in the field options)
$format_out = 'd-m-Y'; // the format you want to end up with
$date = DateTime::createFromFormat($format_in, get_field('date_picker'));
echo $date->format( $format_out );
?>
Hi @scottnath
It is not possible for ACF to run the ‘the_content’ filter on it’s WYSIWYG values as it will cause massive issues such as:
1. A bbPress forum will render twice
2. A shopping cart will render twice
I would advise you to not modify the core functionality, but to just run the_content on the value you get back from the API.
That way, the code is within your theme, not within ACF.
You could even just use this filter in your functions.php file to always run the_content on all WYSIWYG values:
<?php
add_filter('acf/format_value_for_api/type=wysiwyg', 'format_value_for_api_wysiwyg', 10, 3);
function format_value_for_api_wysiwyg( $value, $post_id, $field )
{
$value = apply_filters( 'the_content', $value );
return $value;
}
?>
Hi @Cloud Media Lab
Thanks for the bug report. This is happening on a few installs and I will find a fix shortly.
One avenue I am perusing is an issue with the cache name. Are you using a caching plugin on the site?
Hi @Hube2
Currently, this is not possible. However, it is very possible to create your own custom location rule!
You could create a rule to look at the taxonomy term’s parent and then return true / false depending on the result.
You can read how to create a custom location rule here:
http://www.advancedcustomfields.com/resources/tutorials/custom-location-rules/
Hi @Cloud9
The issue will be 1 of 2 things:
1. The field name is incorrect. Please double check it
2. The global $post object is not correct. This is more likely the case and to help you further I will need to know:
Where is the data saved?
What template are you loading the data from?
Hi @AmandaB
Thanks for the request. Your right, this would be a great feature and I’ll add it to the to-do
Cheers
Elliot
Hi @roger
My first question is to ask where the user is editing the post.
If the users are logging into the WP backend and editing posts via the normal wp-admin interface, then you could create a custom location rule!
A custom location rule will allow you to look at the current logged in user and compare it to the post’s author. If they match, return true, if not, return false.
This will show / hide the field group on a user basis!
You can read how to create custom location rules here:
http://www.advancedcustomfields.com/resources/tutorials/custom-location-rules/
Hi @jimmy.aat10
Check out a plugin called ‘codepress admin columns’
http://www.advancedcustomfields.com/resources/getting-started/compatible-plugins/
Hi @SMillerNL
Would you mind posting a screenshot of the issue?
ACF uses a filter called acf/update_value to save the value into the database. I have set it up as a filter so you can hook in and modify the value before save, or use the value in another way.
Please read the docs about this filter to understand it with more clarity.
You would hook in using the field name or key, then use the value that was posted to do what ever you want.
in your case, you would explode the string to get the day, month and year in an array. Then save the month and array to the database using WP save functions
Is there anything in particular you don’t understand?
Hi @ashkas
Thanks for the reply. I’m not sure why this would be causing any issues with ACF. It doesn’t seem to change any core functionality at all…
Is it possible that there is a Syntax error which is breaking the admin_enqueue_scripts action?
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 Privacy Policy. If you continue to use this site, you consent to our use of cookies.