mcsr

I didn’t know about the behavior of get_field(), but it makes sense to adopt this to the table field. Maybe I was a bit confused because we used it most of the time with GraphQL and there empty fields return null .

I’m fine with both false and null

The REST-API now returns false if the table is empty, that’s correct. Is there a reason why it doesn’t return null as other empty ACF fields?

Hi @jonua ,

Thanks for the update and detailed explanation! Now it’s working fine.

I’ve noticed another thing where I’m not sure if it’s intended like this: When the table is empty, the field returns false on the REST-API. Shouldn’t this be null instead of false ?

Hi there,

My client is experiencing the same issue on his Gutenberg WordPress site. I didn’t test your patch from the GDrive cause I’m not sure if this works with the Pro-Version of the plugin.

We’re using v2.10.3 of the plugin (Pro version) and had a similar issue where the browser was out of memory and the page didn’t respond anymore a few weeks ago. This was fixed with v2.10.2 but since we’re on v2.10.3 for a few days, my client is reporting issues again.

I did a rollback to version v2.10.2 and everything seems to work fine again.

@rmpel Thanks!

This allows the user to clear the cache and change settings. But in my case this doesn’t matter.

Thanks @rockfire ! Now it’s working.

Really like your plugin because it works in nearly any environment without significant changes to the configuration ??

@rizaardiyanto After clicking a few times around its working now correctly (please don’t ask why). Should the issue continue to occur, I will open up a new thread for it.

Thanks.

• This reply was modified 1 year, 5 months ago by mcsr.

Hi @rizaardiyanto

It seems like it’s working with 3.0.3.

But now I’m facing the issue that I sometimes have to enable and disable Future on a post multiple times until it shows up in the post type’s overview on the regarding post item. That means that I enable Future on a post and then go back to the overview of the post type in the WP dashboard, but the expiration isn’t showing up on the post item. It looks like that it isn’t enabled. After saving the post multiple times, it works.

I’m using the Gutenberg editor.

Hi @rizaardiyanto @stevejburge

The issue is fixed with the update to Future 3.0.2, but now I’m also experiencing the issue as others are describing in newer threads.

Some issue on my site. Any updates on this?

Same issue also on my WordPress site. Any updates already on this?

I have checked and tested this again more in detail. The problems occurred with an old plugin version (probably the one in which the problem occurred). With the current one, everything works fine.

Thanks @rizaardiyanto !

@rizaardiyanto I’m using:

WordPress 6.1.1
PHP 7.4
PublishPress Future 2.8.0

Hi @rizaardiyanto

Most of the time, the expiration is set to move the post to the trash. It’s not related to taxonomies, only to posts in custom post types.

I saw in the forum here, that some other users also reported problems such like this. Maybe, the issue happened while I was using the buggy version. So, I will keep an eye on it, if it is still happening with v2.8.0.

Hi @friendlycaptcha ,

Thanks for that information. Just subscribed to that issue, so I’m always up-to-date.

Kind regards!