Create Custom Bible Reading Plan Plugin not working

Try the new version 1.5 which you can download from the link at
https://u.pcloud.link/publink/show?code=XZtDE55ZeOX5Xd6TQk81UmIo6N1tX7cEnIUk

Let me know whether or not this works.

Thanks for the quick response. I upgrade from 1.4 to 1.5, but I am getting a new error now when trying to save changes.

Fatal error: Uncaught Error: Call to undefined function is_json() in /var/www/wordpress/wp-content/plugins/create-bible-reading-plans/create-bible-reading-plans-class.inc.php:227 Stack trace: #0 /var/www/wordpress/wp-includes/class-wp-hook.php(326): CreateBibleReadingPlans->validateAndCreateBibleReadingPlanArray() #1 /var/www/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters() #2 /var/www/wordpress/wp-includes/formatting.php(5100): apply_filters() #3 /var/www/wordpress/wp-includes/option.php(878): sanitize_option() #4 /var/www/wordpress/wp-admin/options.php(344): update_option() #5 {main} thrown in /var/www/wordpress/wp-content/plugins/create-bible-reading-plans/create-bible-reading-plans-class.inc.php on line 227

There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

It might have to do with the fact that the SSL certificate for app.sellwire.net expired on December 22.

I believe you are correct. You can renew that license at Sellwire for a reduced rate.

There is, in fact, a bug that I had been working to resolve before some health issues sidelined me. But one should not encounter that bug unless one’s license had expired.

Please let me know whether or not renewing your license clears your problem.

My license shouldn’t expire until December 31.
I notice that even when I go to app.sellwire.net to renew my license for another year it says, “Not secure” and shows that the SSL certificate for the site is expired. I wonder if that is causing the license validation to fail since it uses https to do the check?

I went ahead and renewed my license a few days early but I am still getting the same error.

sorry. I’ll get busy trying to fix that bug.

My colleague, @sophoservices, has found what we believe was causing the problem, but we cannot yet be certain because, unhappily, our testing is impeded by the fact that SellWire’s site’s SSL certificate has expired. So we must wait until they correct that before we can confirm that the bug is fixed.

Thank you for the update.

Yes, I am getting the same problem and the same errors as @ogbcashdown

It looks like the sellwire SSL is the problem as @drmikegreen says.

Any updates on this? I need to edit my 2025 reading plan! Thanks.

I’m sorry. Sell Wire still have not renewed their SSL certificate. We are, therefore working on a solution which does not require their service. Hopefully we will have have that ready within a couple of days.

Can you try this version, we’re testing a new method.

https://brp.sophoservices.com/create-bible-reading-plans.zip

I installed the version you linked to above, but I am still getting a fatal error.

Fatal error: Uncaught Error: Call to undefined function is_json() in /var/www/wordpress/wp-content/plugins/create-bible-reading-plans/create-bible-reading-plans-class.inc.php:227 Stack trace: #0 /var/www/wordpress/wp-includes/class-wp-hook.php(326): CreateBibleReadingPlans->validateAndCreateBibleReadingPlanArray() #1 /var/www/wordpress/wp-includes/plugin.php(205): WP_Hook->apply_filters() #2 /var/www/wordpress/wp-includes/formatting.php(5100): apply_filters() #3 /var/www/wordpress/wp-includes/option.php(878): sanitize_option() #4 /var/www/wordpress/wp-admin/options.php(344): update_option() #5 {main} thrown in?/var/www/wordpress/wp-content/plugins/create-bible-reading-plans/create-bible-reading-plans-class.inc.php?on line?227

For some reason, Chrome blocked the download the first time. Once I got it downloaded, I got this error when trying to activate the plugin.

Plugin could not be activated because it triggered a?fatal error.

Then I noticed that it installed the plugin as a new instance, so I deactivated 1.50 and then was able to activate 1.5.1, and it seems to be working.