Andris

Paldies Nauriskolats!

PS. It seems it only happens with the ‘New abandoned cart saved! ??</img>’ emails.

–

Hi David,

I have decided to use S3 instead of Google Drive because it’s quicker to setup. And the initial issue was probably the fact that every site needs it’s own Google ‘Project’.

Thanks for your help.

Andris

They are indeed in the same Google Project. It’s going to take some time to create a new project for each website.

I’ll give that a go.

Thanks.

After another weekly cycle of file backups I can confirm that will all the re-authentication I did they are still not working as per my first support post. Please help.

Hi,

Here is the other log from the 27 Feb:

https://pastebin.com/0DaDHdVx

Incidentally, I am not getting the Google Authentication message on the Current Status page anymore for this site, after I re-authenticated again several days ago (which was a week after updating the Google credentials to https).

I am suspecting that the issue may simply be that when the site URL was updated in the Google credentials to the https variant, it may take some time for Google to actually implement/propagate the change – even though it shows as updated in the credentials list. Then shortly after when I had performed the Updraft plus authentication it was still authenticating with the http variant.

Now this is just a deduction from seeing that other sites which I re-authenticated recently are not having upload issues anymore.

Hi D,

Thanks for your quick response.

Here’s the success message:

Success: you have authenticated your Google Drive account. Name: Andris Dinsbergs. Your Google Drive quota usage: 1.6 % used, 10485760 MB available

but this still appears:

Have not yet obtained an access token from Google – you need to authorise or re-authorise your connection to Google Drive.

I’m using the same Project but different ‘OAuth 2.0 client IDs’ for each site of which there are about 28.

The log file:
https://pastebin.com/mfXDCbJL (Not finished) – most recent
https://pastebin.com/NVP7ygTL (20 Feb)

Thanks for your help!

Sorry. Ignore this. It’s not an issue.

I too have the problem even with 3.0.5 and found I had to change in google-calendar-events/vendor/nesbot/carbon/src/Carbon/Carbon.php, the code beginning with line 57 to:

const SUNDAY = 1;
const MONDAY = 2;
const TUESDAY = 3;
const WEDNESDAY = 4;
const THURSDAY = 5;
const FRIDAY = 6;
const SATURDAY = 0;

Of course, this will be overridden in the next plugin update so is a temporary fix. I’m also not sure of the logic with this so it may depend on other settings you may have.

Thanks Frankie. Quick response too. Legend!

Also, with the plugin activated and then trying to publish a post I got this warning:

Warning: Cannot modify header information – headers already sent by (output started at /home/loudmoun/public_html/wp-content/plugins/archive/archive.php:1) in /home/loudmoun/public_html/wp-admin/post.php on line 233

Warning: Cannot modify header information – headers already sent by (output started at /home/loudmoun/public_html/wp-content/plugins/archive/archive.php:1) in /home/loudmoun/public_html/wp-includes/pluggable.php on line 1178

Ah, yes. Thanks.

‘Tis working indeed but the issue turned out to be that when clicking upload and selecting an image (as I’ve done on many other sites) the URL field wouldn’t ‘record’ the image URL.

My fix was to manually add the image URL into the logo field and then saving changes. I don’t have time atm to investigate why this worked though. Sorry.

Thanks jeffr0 for your critique. I too am keen on this plugin but can see it’s not ready yet.

Well done Ross! Thanks.