colinhrt

Thank you. It sounds like the tracking error is something in the setup of my site, which I could get to the bottom of. The data retention is by design and I should have read the popup properly. But until the the upcoming release comes out there will be the php error, So I have decided to go with something else for the time being, but I liked the look of the goals feature in Burst so I will probably be back later.

Just a small update, when I deleted the plugin through WordPress it left the burst_goal_statistics table behind in the database.

Thank you for that. I have tried the WordPress Cron job on PHP 7.4, 8.0, 8.1, 8.2 with the updated Pretty Links Plugin installed and it works fine now with no warning messages.

Regards

Colin

I have just tried this with PHP 7.4

PHP 7.4.33 (cli) (built: Nov 8 2022 11:36:34) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.33, Copyright (c), by Zend Technologies

And there is no warning then, so it seems it is something that came in with PHP 8.0, possibly PHP 8.0 is being more strict or something.

I just tried installing PHP 8.0.

PHP 8.0.26 (cli) (built: Dec 5 2022 21:59:43) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.26, Copyright (c) Zend Technologies
with Zend OPcache v8.0.26, Copyright (c), by Zend Technologies

And I see the same warning when running this, it does like when being run from the command line the PrettyLinks plugin is not handling the missing REQUEST_HEADER variable nicely.

Thank you for quick response I look forward to an updated version of the plugin with this fix incorporated at some stage when you have some free time. As I mentioned there is a work around so its not a blocker for me.

Hi

I looked at that code in GitHub, that seems to be for version 1.4.0 of the plugin, the version that I have installed from www.ads-software.com seems to be 1.4.1, I looked at the other forks in the repository, there is one that it looks like you did that has the 1.4.1 changes in but is now version 1.5.0.

I am not terribly familiar with Git I always avoid it when possible (I don’t want to hear about how wonderful it is ?? ) I thought I should make a fork make my changes then create a PR from that but in this scenario I am not sure.

I have modified 2 files
etsy-importer.php
includes/fields.php

Can I just send you those files

I also encountered the not setting product post statuses correctly on all the posts, some get set to publish and the rest to draft.

Got to the bottom of this and have fixed that in my code updates as well. The actual logic for updating the statuses was not right and basically it only sets the status correctly on last block of products updated from Etsy to WordPress.

I have rearranged it so it now sets all the posts to draft at the start of the import/update and then sets all the ones still found in Etsy to publish on WordPress as it updates them from Etsy, so by the end of update they are all in the correct state.

After further investigation I discovered it was the plugin MainWP Child that was causing the issue, I disabled it and the update from 4.9.4 to 4.9.5 worked fine. As I was only trialing MainWP to see if it was useful to me I have simply removed it, being able to update my sites is more important and I have already have the monitoring and backups through other means.

I don’t know if that behaviour of MainWP Child is deliberate or a bug, either way it was not useful to me.

Hi borisev

I think you may have missed something. My report can be downloaded for free as well.

People only need to subscribe if they want a version that contains their affiliate links that they can give away for free.

When someone subscribes they receive a permanent unique link to download their report and can download the latest one each day through that link and or promote that link to give it away easily.

This custom report containing their affiliate links is I believe the unique point.(https://www.cbgravitas.com)

Regards

Colin

Thanks for that.

I am thinking of putting a page on my site where a user who has lost the activation email can request it again. The site ( https://www.cbgravitas.com ) is a front end for a subscription service I have set up which sends some information to their email account, and I have another plugin I developed to integrate the two. So now knowing that the activation link does not expire until clicked on I can simply save it when it is generated in my systems database and resend an email with it if requested.

This does not handle customers who entered the wrong email address, thinking of some sort of expiry period for them, if they have not activated their account after say 3 weeks the system will automatically purge them and cancel and refund any subscription they may have set up as well. As it is a monthly subscription this would stop it before a rebill if they don’t stop it earlier.

• This reply was modified 7 years, 11 months ago by colinhrt. Reason: Some typos