Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • I am still receiving the daily mails with the “Your Site is Experiencing a Technical Issue” subject… So @wpforchurch still has a bug that seems to be related to Jetpack. So far, our site does not appear to suffer any issues, so the email is just an annoyance:

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.5
    Current theme: High Responsive (version 2.1.1)
    Current plugin: Sermon Manager for WordPress (version 2.16.1)
    PHP version 7.3.21

    Error Details
    =============
    An error of type E_ERROR was caused in line 560 of the file /…/wp-content/plugins/sermon-manager-for-wordpress/sermons.php. Error message: Uncaught Error: Call to undefined function sm_get_screen_ids() in /…/wp-content/plugins/sermon-manager-for-wordpress/sermons.php:560
    Stack trace:
    #0 /…/wp-includes/class-wp-hook.php(287): SermonManager->{closure}(Object(WP_Screen))
    #1 /…/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
    #2 /…/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /…/wp-admin/includes/class-wp-screen.php(421): do_action(‘current_screen’, Object(WP_Screen))
    #4 /…/wp-admin/includes/screen.php(240): WP_Screen->set_current_screen()
    #5 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(370): set_current_screen(‘sync’)
    #6 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(463): Automattic\Jetpack\Sync\Sender->get_items_to_send(Object(Automattic\Jetpack\

    I have been receiving these automated emails from my site on a daily basis since the update to v2.16.1 — I have re-installed using both the dropbox and the standard WordPress methods and these mail keep coming once a day between 4:00 and 4:30pm. This is not the same as the fatal error I had when I tried updating to 2.16.1 the very first time, this is something different and subtle because the site seems OK, but these emails keep coming every day:

    Subject: […] Your Site is Experiencing a Technical Issue

    First, visit your website (https://…/) and check for any visible issues. Next, visit the page where the error was caught (https://…/wp-cron.php?doing_wp_cron=1598396643.9682788848876953125000) and check for any visible issues.

    WordPress version 5.5
    Current theme: High Responsive (version 2.1.1)
    Current plugin: Sermon Manager for WordPress (version 2.16.1)
    PHP version 7.3.21

    Error Details
    =============
    An error of type E_ERROR was caused in line 560 of the file /…/wp-content/plugins/sermon-manager-for-wordpress/sermons.php. Error message: Uncaught Error: Call to undefined function sm_get_screen_ids() in /home3/mtolive9/public_html/wp-content/plugins/sermon-manager-for-wordpress/sermons.php:560
    Stack trace:
    #0 /…/wp-includes/class-wp-hook.php(287): SermonManager->{closure}(Object(WP_Screen))
    #1 /…/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
    #2 /…/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /…/wp-admin/includes/class-wp-screen.php(421): do_action(‘current_screen’, Object(WP_Screen))
    #4 /…/wp-admin/includes/screen.php(240): WP_Screen->set_current_screen()
    #5 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(370): set_current_screen(‘sync’)
    #6 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(463): Automattic\Jetpack\Sync\Sender->get_items_to_send(Object(Automattic\Jetpack\

    I do not see any visible issues with the site, I am able to login to the Dashboard, so everything seems OK, but perhaps there is something subtly wrong that I am not seeing. We do use Jetpack version 8.8.2 but are not seeing any issues with the features we use from it. So at least for now, I am staying on Sermon Manager version 2.16.1 but it would be nice to understand why the mail happened and get the issue fixed.

    Hi @abouttheinn, I see the function defined in includes/admin/sm-admin-functions.php on line 16:

    function sm_get_screen_ids() {

    But I’m not seeing how sermons.php includes that. But maybe that’s enough hints for @wpforchurch to get to the bottom of it.

    After updating yesterday to version 2.16.1, I received an automated email hours later with this:

    Subject: […] Your Site is Experiencing a Technical Issue

    First, visit your website (https://…/) and check for any visible issues. Next, visit the page where the error was caught (https://…/wp-cron.php?doing_wp_cron=1598396643.9682788848876953125000) and check for any visible issues.

    WordPress version 5.5
    Current theme: High Responsive (version 2.1.1)
    Current plugin: Sermon Manager for WordPress (version 2.16.1)
    PHP version 7.3.21

    Error Details
    =============
    An error of type E_ERROR was caused in line 560 of the file /…/wp-content/plugins/sermon-manager-for-wordpress/sermons.php. Error message: Uncaught Error: Call to undefined function sm_get_screen_ids() in /home3/mtolive9/public_html/wp-content/plugins/sermon-manager-for-wordpress/sermons.php:560
    Stack trace:
    #0 /…/wp-includes/class-wp-hook.php(287): SermonManager->{closure}(Object(WP_Screen))
    #1 /…/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
    #2 /…/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #3 /…/wp-admin/includes/class-wp-screen.php(421): do_action(‘current_screen’, Object(WP_Screen))
    #4 /…/wp-admin/includes/screen.php(240): WP_Screen->set_current_screen()
    #5 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(370): set_current_screen(‘sync’)
    #6 /…/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-sender.php(463): Automattic\Jetpack\Sync\Sender->get_items_to_send(Object(Automattic\Jetpack\

    I do not see any visible issues with the site, I am able to login to the Dashboard, so everything seems OK, but perhaps there is something subtly wrong that I am not seeing. We do use Jetpack version 8.8.2 but are not seeing any issues with the features we use from it. So at least for now, I am staying on Sermon Manager version 2.16.1 but it would be nice to understand why the mail happened and get the issue fixed.

    Just a suggestion, how about instead of publishing immediately, set the “Publish” date to the date you want the podcast to become available. That way the time it becomes visible on the site (and in your podcast feed) are controlled by that, not the Date Preached field in the sermon.

    Thanks @wpforchurch – I appreciate all you’re doing! After having issues with the 2.16.1 update yesterday and reverting back to 2.16.0, I did the update today and it seems to be good now. FYI, we are on WordPress 5.5 with the High Responsive theme and so far, other than some slight interface differences probably due to the WordPress 5.5 compatibility, it is working fine.

    Thank you!

    Look on the right side of the page under the Document section, there you should see the Preacher, Series, Topics and Books fields – need to open them by clicking on their names. This is slightly different than before, but they are working for me.

    The interface seems to have changed slightly in version 2.16.1, the Title field looks like the standard Post and there is a text Block below that which does not seem to be useful – we use the Description field for sermon notes, so I will just ignore that first text Block at the top. Maybe it works on other themes.

    That said, I am able to select Preacher by going to the Document section on the right, scrolling down past the URL slug and other bits and by typing a few letters in the Preacher field, then selecting the name. Same for Series, Topics and Books.

    We are running the High Responsive theme on WordPress 5.5 and so far, so good with this new version (that is after the mishap yesterday morning which is resolved now).

    Same issue here. Thanks for @almcnicoll for the work-around, it worked for me just as you said and I was able to login to my site. However, after doing the edits, I tried to add a new sermon and that interface was not working – no Save Draft option, the very top of the page had what looked like a standard Post interface with the title and content above the normal sermon fields. So in the end, I reverted to the previous version (2.16.0) from last night’s backup.

    Hopefully the @wpforchurch folks are listening and release an update soon that fixes this issue. I did notice that they say that they have tested up to WordPress 5.4.2 but my site automatically updated to WordPress 5.5 a while back, so it may be that there are some compatibility issues still to be resolved. For now, I’ll stick to 2.16.0 as it seems to be working for me.

    • This reply was modified 1 year, 1 month ago by beryrinaldo. Reason: added more details

    I have seen this recently, too. Most of the time, posts are expiring properly – we typically expire to Draft, but sometimes they do not. I have yet to find a pattern.

    We’re on WP version 5.4 with PHP 7.3.13.

    Thread Starter beryrinaldo

    (@beryrinaldo)

    Thanks for the follow-up. There is something specific about this one post that seems to bring out the issue. So far, no other posts have shown this.

    I must add that this plugin has come in very handy. Thanks for all your work keeping it alive and investigating issues as they come along. I appreciate it!

    Thread Starter beryrinaldo

    (@beryrinaldo)

    My apologies, that page changes weekly and you caught it with no posts. Here is a test page that shows the issue:

    http://mt-olive.org/display-posts-test-multiple-instances/

    The text of the page looks like this:

    <section class=”first”>
    [display-posts id=”5488″ include_date=”false” date_format=”F j, Y g:ia” image_size=”small” include_content=”true” content_class=”the-olive-press-content” wrapper=”div” wrapper_class=”the-olive-press-layout” include_link=”true”]
    </section>
    <section class=”second”>
    [display-posts id=”5488″ include_date=”false” date_format=”F j, Y g:ia” image_size=”small” include_content=”true” content_class=”the-olive-press-content” wrapper=”div” wrapper_class=”the-olive-press-layout” include_link=”true”]
    </section>

    The first section has the issue, the second is correct.

Viewing 12 replies - 1 through 12 (of 12 total)