Thanks for the hint, John.
I did what you suggest and $now is 2 hours behind current time (guess it’s UTC time)
mysql date (Post Date GMT): 1455784671
mysql date (now): 1470733499
now: 2016-08-09 11:04:59
In WordPress, timezone is set to my current time (UTC + 2) as it is for the mysql server. So right now I am curious where we need to fix it.
edit: here’s the debugging for save_post
Post Status (before):publish<br/>
Post Status (after):publish<br/>
mysql date (Post Date GMT): 1455784671<br/>
mysql date (now): 1470740759<br/>
now: 2016-08-09 13:05:59
Post Status (before):publish<br/>
Post Status (after):future<br/>
mysql date (Post Date GMT): 1470747926<br/>
mysql date (now): 1470740759<br/>
now: 2016-08-09 13:05:59
Post Status (before):publish<br/>
Post Status (after):publish<br/>
mysql date (Post Date GMT): 1455784671<br/>
mysql date (now): 1470740759<br/>
now: 2016-08-09 13:05:59
Post Status (before):publish<br/>
Post Status (after):future<br/>
mysql date (Post Date GMT): 1470747926<br/>
mysql date (now): 1470740759<br/>
now: 2016-08-09 13:05:59
Post Status (before):publish<br/>
Post Status (after):publish<br/>
mysql date (Post Date GMT): 1455784671<br/>
mysql date (now): 1470740759<br/>
now: 2016-08-09 13:05:59
Update: cloned it to another server and guess what. Works perfectly.
Now I need to find out what the problem on the production server could be.
Damn 🙂
That’s what I assumed before but I couldn’t find a difference
UTC is 200 and correct. Mysql Datetime and Server time is the same.
Also, the field post_created and modified times are also correct.
What a pain in….
—
will clone it to another server
No problem.
I guess it’s a problem between ACF and the server configuration.
Whatever we do, it’s impossible to add new fields for now.
Already opened a ticket today.
We even cloned the site, completely disabled all other plugins.
Deleted the field group, imported it again and it shows up empty with an info “schedulded” next to it.
Something really doesn’t work together here.
A test on your installation/server doesn’t really help for our problem – it is definately not working as before and we try to find the source of the problem.
As stated in the main post here: we already tested with all plugins deactivated. We changed maximum numbers of input vars and we checked the theme’s functions for any filters. Nothing helped to fix the post_status problem.
Hi John. Unfortunately this is not the problem. As I wrote before we already set the max to 9000. I installed the plugin you suggested and added a single text field to the group. Saved, got the update message and it is in the db but like any other field, it’s post_status is set to “future” and that’s the reason it doesn’t show up in the backend.
After checking different possiblities I saw that everything is saved to the DB but post_status remains “future”.
Where is this set?
After changing this to public in the db, everything is there.
hi and thanks for your help! one question before I try this.
After you re-imported the field group, where you able to add/change new fields to the flexible content without any further problems?
I am curious why the new layout is not saved to the db.
Thanks again.
Same proplem here. The new fields are in the database but not showing in the backend.
Also, their post status is set to “future”
@rdourado we have exactly the same problem.
any chances you can tell us what exactly caused the problem?
Hi @James
As I wrote before, the versions are not updated until I deactivate and reactivate the license key on the wordpress page itself. This has nothing to do with the https protocol. Only 2 of 10 pages uses secure connections so it should show the correct version number on my account page here. Plus, it’s not helpful if I have to deactivate and re-activate the key all the time.
For the “no update” available problem I will open a ticket as suggested.
@billcommexis you can delete the plugin folder (via ftp) and upload it manually. but it’s a pain in the a**.
Hi James, thanks for the reply. As previously stated I have two issues.
– there is no update available under “plugins” even though I can see the update in the ACF menu
– here on acf.com, in my account I can see the activated installations and they show different versions then installed. Only after I go to the page, deactivate the licence and reactivate it, it shows the correct version number.
Sorry, I had a typo.
The latest version we use is ACF Pro 5.3.10
Not one wordpress installation informs about 5.4
Even here at the download page it sends 5.3.10
@stemlund
got the same problem. Added an API key (without referer protection because it never worked) and all I can do is add a pin but not search within the address field.
it is disabled (see source code).
Edit: after activating “Google Maps Geolocation API” and reloading the backend it seems to enable the address field search.
Try adding the post_type or the meta_key
$args['meta_query'] = array(
'post_type' => 'your_post_type',
'meta_query' => array(
'key' => 'color',
'value' => 'blue',
'compare' => '!='
)
);
return $args;
