[Resolved] Translated page not found on frontend

We’ve identified the cause of the issue with the link pointing to /cs/ instead of /cs/denni-rezim.
It appears that the post with ID 9155 was missing a slug (also called post_name) in the WordPress database — this is the value WordPress uses to generate the page URL.

Normally, the slug is automatically created when a post is published, but in this case it was blank — which likely caused WordPress to redirect incorrectly. Once the missing slug was added, the URL started working properly.

To check and fix this on your end:

1. Open Adminer (or phpMyAdmin) and go to your WordPress database.
2. Open the wp_posts table.
3. Find the affected post (e.g., by filtering ID = 9155).
4. Look for the column named post_name — if it’s empty, enter the correct slug (e.g. denni-rezim).
5. Save the change.
6. (Optional but recommended) Go to Settings → Permalinks in WordPress and click Save Changes to refresh permalink rules.

If you find other posts missing their post_name, you can fix them the same way.

We haven’t seen this happen under normal conditions, so it may have resulted from database corruption or an earlier translation/synchronization issue. If it occurs again when creating new posts, please let us know — we’ll escalate it as a potential bug.

Thanks for confirming! It’s good to hear the fix worked. Since you see the same issue on those other sites, applying the same database update should resolve it as well.

It seems the issue happens because the event’s title (`post_title`) is empty when WordPress tries to generate the event slug. Since the title is missing, the system creates a blank slug, which causes the process to fail.

Our 2nd-tier team identified that this behavior originates from the Events Manager plugin, specifically from how it handles the `publish_future_post` action.

We recommend reaching out to the plugin developers at hidden link to have them review and confirm this issue, and ideally, apply a proper fix in their code. Otherwise, any manual code change you make will be overwritten when the plugin is updated.

As a temporary workaround, you can comment out the following line in `/wp-content/plugins/events-manager/classes/em-event-post.php` to prevent the problematic action from triggering:

add_action('publish_future_post', array('EM_Event_Post', 'publish_future_post'), 10, 1);

If modifying that line is not possible, a more targeted workaround would be to adjust the following code:

$is_post_type = Archetypes::is_repeating( $post_type ) ? Archetypes::get_repeating_archetype( $post_type ) : $post_type;

to:

$is_post_type = Archetypes::is_repeating( $post_type ) ? Archetypes::get_repeating_archetype( $post_type ) : NULL;

This ensures the function doesn’t assign an invalid post type when the event is missing a title.