Jared Cobb

@adamestafford Thanks for your patience and helping me to troubleshoot this! I created a brand new environment to match yours, and I’m able to now replicate the issue. In short, it has to do with the specific version of PHP and how I’m handling encryption. I should have an update ready in the next day or so. My apologies for the inconvenience.

@adamestafford It sounds like there is still some bad data somewhere. Can you delete all options that begin with ccb_core_ in the database? That won’t hurt anything and essentially resets the installation.

@adamestafford I believe I know the root cause of this issue. I believe the older (broken) version of the plugin has left some bad data in place. I appreciate this report, it’ll allow me to ensure this doesn’t happen for other users moving forward.

In the short term, the best way to fix this will be to either:

1. Edit your wp_options table and delete the row with the option_name of ccb_core_settings or
2. Use a plugin that allows you to edit options, for example https://www.ads-software.com/plugins/options-inspector/ and delete the ccb_core_settings option.

@adamestafford Can you confirm whether you have also deactivated/deleted the known broken version? If both plugins are activated I believe the older one will take precedence.

@adamestafford @ponderconsulting I have a major release coming soon which resolves this bug (related to newer versions of PHP and how encryption is handled).

You can download a beta version of it directly here https://github.com/jaredcobb/ccb-core/archive/master.zip

I should have it updated in the www.ads-software.com repo (and available to update within WordPress) in the next few days.

Hi Jeremy, thanks for the bug report. I just wanted to mention that I’ll be able to take a look in a couple of weeks. Sorry for the delay.

Kim, I’m also seeing some information on the web about earlier versions of Sodium using a different syntax for function calls. This could definitely be the issue…

Can you ask your provider whether they’re running Sodium 1.x or 2.x? 1.x uses namespaces whereas 2.x uses global function names (which is how the plugin expects them to exist).

Hi Kim, thanks for the bug report.

First, can you let me know who your hosting provider is?

Second, Would you mind sending the following questions/info to your hosting provider? It seems like even though Sodium is showing up in your PHP info, it may not be properly installed.

I’m using the following two Sodium functions to encrypt & decrypt the API credentials:

https://php.net/manual/en/function.sodium-crypto-secretbox.php

https://php.net/manual/en/function.sodium-crypto-secretbox-open.php

In the plugin I’m checking that they exist like so:
https://github.com/jaredcobb/ccb-core/blob/167c0233615a14f73e00dde1ed8f1185afe6785e/includes/class-ccb-core-requirements.php#L150-L151

Can you help us determine why those two Sodium functions do not exist on the hosting platform?

Kim, I’d also be happy to look into making any changes to the plugin that would make this compatible with your host. So definitely let me know what they come back with. Thanks!

Hi all, sorry for the delay in responding… There was a change to how the WordPress cron system makes certain core functions available. One of the missing functions had to do with image downloads (specifically if you are synchronizing group images in the background).

I released a fix this evening so you should be able to update to 1.0.7 to get the fix. This update also includes some performance improvements and compatibility fixes for newer versions of PHP (specifically PHP 7.2 and above).

After the upgrade, if any of you have issues with the auto sync please feel free to let me know here again and I can try to take a closer look. But I’m fairly certain this was the issue because I was able to replicate it.

That’s how I do!

@modmacro I published a new version that fixes this issue (1.0.5). When you have a chance can you confirm it’s working for you as well? Thanks again for reporting this.

Jared

Great. This actually had nothing to do with the date range starting in the past after all.

As part of the synchronization process, the plugin fetches all the existing event posts and compares them to the API response. It turns out there is a scenario where fetching the posts can result in not actually getting all of them (and then the plugin thinks those events are “missing” and needs to insert them again).

I’m also surprised this hasn’t come up before. It’s possible something has changed in a recent WordPress update with how WP_Query handles batched & looped queries (which is how I’m fetching the existing posts for performance reasons).

I have a fix in place, but I won’t be able to publish a new version until this evening.

• This reply was modified 6 years, 10 months ago by Jared Cobb.

Matt,

Disregard my last post, I’m actually able to replicate this. It seems there’s a bug if the data range starts in the past (i.e. in the settings if the “How Far Back” setting is greater than 0).

I’ll have time to debug this later today and figure out what’s wrong. I’ll be able to publish an update (hopefully today or tomorrow).

Thanks again for reporting this!

Matt,

Thanks for confirming all of that! The plugin definitely seems to be causing the issue, and for some reason I haven’t been able to replicate it on my church’s account.

Would you be able to create another API user for me and grant the user rights to the public_calendar_listing service? This way I can try to replicate the issue using the same data. (And once I get this fixed you can delete my API user).

Also, do you know what PHP version you’re running? If not you can temporarily install this plugin https://www.ads-software.com/plugins/wordpress-php-info/ and then remove it.

• This reply was modified 6 years, 10 months ago by Jared Cobb.

Thanks for the report.

To answer your bigger question, yes, I will certainly be supporting PHP 7.2 and all future versions after that.

I do currently have work started to replace this library (which uses the mcrypt extension). It should be available in the next few weeks. Hopefully you don’t need to upgrade all the way to 7.2 before then. ??