Meta box not displaying

Hi @adejones,

I’m working on this issue but I’m still not able to replicate it.
Sorry, but we are only able to check into your site for members.
Are you able to replicate the issue on a fresh WordPress installation?

Also, please could you let us know what is the value for the setting Default Date/Time Offset on both General and Post Types tabs?

@andergmartins Hi, I have just made a fresh install of WordPress, no theme or plugins or anything, just installed it and then installed PublishPress Future, Created a new post (using block editor) and when I tick “Enable Future Action” the same issue occurs.

The Date/Time offset for both fields is +1 week (default).

I have also created a second fresh install on a different server of mine just in case it was related to a disabled PHP module or something on the server but the same thing happens on the 2nd install too, fresh install with no other plugins activated on a completely different server, same result.

I have also tried versions 3.1.7, 3.1.6 and 3.1.5 but no luck with any of those, same results.

And finally I have used a “rollback core” plugin to try WP version 6.3.3, 6.2.4 and 6.1.5 and no luck with any of those either.

@adejones Would you be able to set up a new WordPress installation on instawp.com ?

You can start by creating a free account and then proceed to create a new WordPress installation. Once completed, please inform us if you were able to replicate the issue there.

If successful, we’d greatly appreciate it if you could outline the steps you took to replicate the issue. We’ve been unable to reproduce it thus far.

@rizaardiyanto I have created a InstaWP account and WordPress installation using “From scratch” with all plugin options disabled and all default settings, installed the PublishPress Future plugin, edited the default “Hello World” post, enabled PublishPress and got the same issue/error.

Then created a new post and same error here too.

Out of interest I have just tried this in Chrome and it works fine, all settings appear as normal when I tick to enable.

I have just tried it in Chrome on the website that I was installing it on originally and it works on there fine too.

And I have tried both websites in Mozilla Firefox too, both absolutely fine in that.

So it looks like after all that, the actual issue is with Safari (OSX), nothing web/server related. Do you guys have a Mac you can try it on and i’m sure you’ll be able to replicate the issue in Safari then.

Don’t know if these 2 links may help you at all:

https://github.com/date-fns/date-fns/issues/2130

https://stackoverflow.com/questions/70727103/date-fns-rangeerror-invalid-time-value

@adejones I’m glad we found new information about this. Sorry I did not ask this information earlier.

Can you inform me what Safari version you are using?

I’m unable to replicate this on Macbook Air M1 2020 with Safari v17.2.1

I am using Version 15.6 (17613.3.9.1.5) though it tells me no updates are available which is odd.

Can also now confirm that the plugin works on mobile (iPhone) because the client wants to use an iPad to do his posts so have advised him to go ahead as it should be fine, just seems to be my version of Safari?

• This reply was modified 1 year, 1 month ago by adejones.
• This reply was modified 1 year, 1 month ago by adejones.

@adejones Yes, it seems this issue only happen on older version of Safari.

It appears that this issue is limited to older versions of Safari. Updates for Safari are typically bundled with MacBook releases. Therefore, to access the newer Safari release, upgrading to a newer MacBook is necessary.

In this case, I would recommend to use Google Chrome instead to edit the post.

The Macbook is only around 2-3 years old, I think this is the 2000 pro model. However, there is an OS update pending to macOS Sonoma as I often put these off, so installing that may also update the Safari version. Although 3 people to date have had the issue, i’m surprised there haven’t been more considering the number of Mac users and not everybody will have a newer mac than 2000.

Anyway thanks for your time, I will do the OS update maybe tonight and see how that goes.

@adejones Ah yeah sorry, I mean Safari version is usually bundled with OS version, not the Macbook itself.

Yeah I do feel the issue will be solved if you update the OS (which automatically update the Safari)

Feel free to let us know if the issue persists after you update the OS.

@rizaardiyanto – Hey, just to confirm that I finally updated my Mac to OS Sonoma and Safari to v17.3.1 and this is resolved, I can use the plugin fine.

I looked at the Apple update log and there had been several updates of Safari since my previous version so there must have been a bug in the browser which they fixed.

I’m glad to hear that @adejones ??

Thanks for giving us an update!