sankari

Hello @katzw

It could take a while until the developers look into this issue (as mentioned here). But I found a workaround that works for us and I would like to share it with you. It’s by adding and using a custom time span.

In our case, we use the EM Events widget and its filter was set to “future events”. The problem was that events of today disappeared before the end of the day.

I found this tutorial on custom time spans (“scope”):
https://wp-events-plugin.com/tutorials/create-your-own-event-scope/

…and used the WPCode plugin:
https://wordpress.org/plugins/insert-headers-and-footers/

…to add a custom time span that displays events of today plus 200 days.

Here is how to do it:

1. Install and activate the WPCode plugin.
2. In the WordPress main menu select Code Snippets.
3. Add New
4. Add Your Custom Code (New Snippet): Use Snippet
5. Add a snippet title, e.g. My Events Manager Scope.
6. Select PHP Snippet as code type.
7. Enter the code below in the Code Preview field.
8. In the Basic Info box enter the tags events manager and scope and set the priority to 3.
9. At the beginning of the page change the switch from Inactive to Active and select Save Snippet.
10. If you use the EM Event widget: In that widget (Appearance > Widgets) select the custom time span and save the changes.
11. If you use a shortcode: add/change the attribute to the one you defined in the code of your code snippet, e.g. scope=”today-plus-200-days” and save the page or post.

Code Snippet:

add_filter( 'em_events_build_sql_conditions', 'my_em_scope_conditions',1,2);
function my_em_scope_conditions($conditions, $args){
    if( !empty($args['scope']) && $args['scope']=='today-plus-200-days' ){        
        $start_date = date('Y-m-d',current_time('timestamp'));
        $end_date = date('Y-m-d',strtotime("+200 days", current_time('timestamp')));
        $conditions['scope'] = " (event_start_date BETWEEN CAST('$start_date' AS DATE) AND CAST('$end_date' AS DATE)) OR (event_end_date BETWEEN CAST('$end_date' AS DATE) AND CAST('$start_date' AS DATE))";
    }
    return $conditions;}add_filter( 'em_get_scopes','my_em_scopes',1,1);

function my_em_scopes($scopes){
    $my_scopes = array(
        'today-plus-200-days' => 'Today plus 200 days'
    );
    return $scopes + $my_scopes;
}

You can modify the time span and the descriptions on these lines go with your needs:

if( !empty($args['scope']) && $args['scope']=='today-plus-200-days' ){   

$end_date = date('Y-m-d',strtotime("+200 days", current_time('timestamp')));

'today-plus-200-days' => 'Today plus 200 days'

It should work well for events that start and end today or within the specified number of days in the future. However, it doesn’t work with events that started before today and end today.

Please let me know if this works for you, too.

• This reply was modified 2 years, 9 months ago by sankari. Reason: Link to shortcodes page added

Hi @arsalantariq

Thank you for releasing the beta. I tested the installation and the wizard. When finishing the configuration settings this is the error I get:

Notice: Undefined index: fallback_smtp_password in /home/httpd/vhosts/client/domain.tld/wp-content/plugins/post-smtp/Postman/PostmanInputSanitizer.php on line 155 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/client/domain.tld/wp-content/plugins/post-smtp/Postman/PostmanInputSanitizer.php:155) in /home/httpd/vhosts/client/domain.tld/wp-includes/pluggable.php on line 1355 Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/client/domain.tld/wp-content/plugins/post-smtp/Postman/PostmanInputSanitizer.php:155) in /home/httpd/vhosts/client/domain.tld/wp-includes/pluggable.php on line 1358

Hi. I experienced something similar: On the day after the upgrade to WordPress 5.9 the plugin stopped sending. An email authentication failure appeared in the log of the plugin.

In this particular case, the email address used for authentication was a forwarding address only and without any mailbox. Before the upgrade sending worked fine using this address.

The solution was to create another email address with a mailbox and save its credentials in the settings of the plugin.

I didn’t try the wizard config.