tholub

(Not the original poster but seeing probably the same behavior)

WordPress 5.5.1, WP User FrontEnd 3.4.0, all other plug-ins disabled.

When “Users can edit post?” is set to No, users are unable to edit any posts they create in WordPress, whether or not the posts were created on the WP User Frontent interface, and whether or not they want to edit them using WP User Frontend.

To reproduce:

1. Go to the WordPress dashboard->Posts
2. Create a post (works normally)
3. Save as draft (works normally)
4. Go back to Posts, choose Edit

The result is either a “404 Page not found”, or a page which says “Post Editing is disabled”.

The URL you wind up at is:
https://devnorcalapa.wpengine.com/?page_id=16064&pid=16121&_wpnonce=adf2044f35

instead of:
https://devnorcalapa.wpengine.com/wp-admin/post.php?post=16064&action=edit

If “Users can edit post?” is set to Yes, editing the draft post from WordPress Dashboard->Posts puts the user into the WP User Frontend interface, instead of the block editor.

It looks like WP User Frontend 3.4.0 is interfering with the main WordPress editor.

Looks like it works fine in 2.0.2. Thanks.

So, in includes/class-gce-feed.php, line 111:

$gmt_offset = $this->timezone_offset * 3600;

When I manually set $gmt_offset to my timezone offset (-7*3600), the feed works properly. So in line 75:

$this->timezone_offset     = get_post_meta( $this->id, 'gce_timezone_offset', true );

$this->timezone_offset is not being set properly.

The issue is that time zone offset isn’t being calculated correctly. For the specific case of wanting to show events from the current time forward, your hack will work, but it doesn’t deal with the general issue of time zone offset calculation; my situation is displaying events from specific dates in the future.

Great! That’s fixed it; I’d changed the $ to jQuery in one place but not the other. Thanks, this is going to be really cool.

Sorry, page should be visible now.

https://bacafest.com/test-page/

It does look like the code may not be running, but I’m not sure why; it’s definitely present in the page source.

The behavior still appears in 2.0.1; a date range of Oct 4-Oct 5 retrieves events from 5:00 PM on Oct 3.

Thanks. The version you sent works fine.

Certainly. Thanks.