D

Excellent, thanks!

A follow-up GDPR question: When I use All-in-One WP Migration to make backups of my website, are those backups available only to me and to the destinations where I send those backups (such as Dropbox or Amazon S3)? Or does All-in-One WP Migration also automatically send copies of those backups anywhere else, such as to All-in-One WP Migration’s headquarters or to any other parties? Thanks!

If I use Shortlinks by Pretty Links to create links on my website that point to third-party ads that pay me a commission when my website visitors click on those links and make a purchase, will the advertiser know that I deserve credit for the sale if I have Shortlinks by Pretty Links set to “Simple Click Count”? In other words, does “Simple Click Count” obscure the information that the advertiser would need in order to know who to credit for the sale?
Thanks!

A quick follow-up question: You said the Stripe Payments plugin doesn’t generate cookies. But I notice that on the page of my website where I’m using the Stripe Payments plugin, the following cookies are being generated: https://checkout.stripe.com, https://js.stripe.com, and https://m.stripe.network. Is the Stripe Payments plugin creating those cookies? Or is Stripe (the company) creating them? Thanks!

Thank you. That was very helpful. By “data usage,” I just meant any miscellaneous information about the website visitor that the plugin might collect, such as IP addresses.

Not at all. Lots of plugins collect various sorts of personally identifiable information (which, as defined by GDPR, includes IP addresses). Does your plugin collect personally identifiable information or use cookies?

I’d like to know the answer to this question, too. If Multi-Column Tag Map plugin has been abandoned, what would be a good substitute? Thanks!

I just noticed a private page showing up on my recently created WordPress site, but I can’t access the page. Nor do I know how it got there. Anybody figure out the cause of this peculiar problem?

Hi Michael,

No, there’s no tag.php template file. I just now checked via email with the theme maker, who said that the tag archive is controlled by the achieve.php file. The theme maker also wrote, “WordPress should pick it up automatically for your custom post types. If it doesn’t, make sure to pass the ‘has archive’ => true parameter to your register_post_type function call.” He didn’t say where or exactly how I should do that, but I assume it should be done in the functions.php file.

Here’s the section of my theme’s functions.php that refers to the archive:

if ( ! function_exists( ‘ttf_common_archives_title’ ) ) :
/**
* Adjust the archives page title to something sensible
*/
function ttf_common_archives_title() {
if ( is_category() ) { /* If this is a category archive */
printf( __( ‘Posts from the ‘%s’ category’, ‘ttf_common’ ), single_cat_title( ”, false ) );
} elseif ( is_tag() ) { /* If this is a tag archive */
printf( __( ‘Posts tagged ‘%s’’, ‘ttf_common’ ), single_tag_title( ”, false ) );
} elseif ( is_day() ) { /* If this is a daily archive */
printf( __( ‘Archive for ‘%s’’, ‘ttf_common’ ), get_the_time( ‘F jS, Y’ ) );
} elseif ( is_month() ) { /* If this is a monthly archive */
printf( __( ‘Archive for ‘%s’’, ‘ttf_common’ ), get_the_time( ‘F, Y’ ) );
} elseif ( is_year() ) { /* If this is a yearly archive */
printf( __( ‘Archive for ‘%s’’, ‘ttf_common’ ), get_the_time( ‘Y’ ) );
} elseif ( is_author() ) { /* If this is an author archive */
printf( __( ‘Posts by %s’, ‘ttf_common’ ), get_the_author() );
} elseif ( is_paged() ) { /* If this is a paged archive */
_e( ‘Blog Archives’, ‘ttf_common’ );
}
}

endif; // ttf_common_archives_title

I’m not adept at php code. Would you know the proper way that I would “pass the ‘has archive’ => true parameter to your register_post_type function call” in the above code? And then after making that change, I would add the revised functions.php file to my child theme, correct?

Thanks!

Thanks for creating the new version. I’ve installed it, and it works well. I most appreciate it. It’s a great plugin!

That worked. Thanks!

Here’s the info from my server-info tab:

OS: Linux gator4139.hostgator.com 3.12.74-213.ELK6.x86_64 #1 SMP Tue Jun 20 00:36:01 CDT 2017 x86_64
PHP version: 5.4.45
WordPress version: 4.8.1
WordPress multisite: No
openssl: Available
allow_url_fopen: Enabled
stream_socket_client: Available
fsockopen: Available
cURL: Available
cURL Version: 7.19.7, NSS/3.27.1

Hi, me again. Disregard that previous request for help. I found the solution at your website here:

https://wphowto.net/gmail-smtp-plugin-for-wordpress-1341/46

Under this section:

Error refreshing the OAuth2 token

When I went to Google Console, I also noticed that my domain needed to be verified—which is weird, since the Gmail SMTP plugin has been working fine on my domain for the last year. I’m not sure if Google somehow lost the verification of my domain or if this is a new requirement from Google. So I verified my domain. And I also saw that Google now wants a privacy-policy URL added to the Credentials>OAuth consent screen (“Optional until you deploy your app,” says Google), so I added my privacy policy’s URL. Now the email seems to be working again.

Thanks for including those troubleshooting instructions on your website.

I’m still having the same problem with the new update of WP Retina 2x that everybody else is having. Until the plugin maker comes out with a new and improved update, my strategy for getting my website back to functioning order was to replace the current version of my website with a backup version of my website made the day before I installed the newest update of WP Retina 2x. I did it because I wanted to revert to the prior version of the plugin and also eliminate any other lurking website problems that the newest plugin update might have caused.

I think the WordPress codex would do everybody a favor by making it possible to download earlier versions of plugins. That way, if the newest update of a plugin doesn’t work, we can easily access an earlier plugin version.

Hi,

I followed the steps you described: 1. Make sure all my other plugins are updated (I’m not using any of your other plugins, and all my other plugins are already updated to the current versions). 2. Delete WP Retina 2X from my WP. 3. Reinstall WP Retina 2x.

But unfortunately, I got the same result. WP Retina 2x fails to work in all the ways that I described earlier. There’s definitely a problem with it.

Regards,
D