David Cameron Law

I’ve tried all the Custom Post Type UI Plugin “Settings” options and no matter what I set the Display Widget options still worked as expected.

Have you tried adding a new widget and only change the widget options

Set to “Show On Ticked”

Under “Custom Post Types +/-” tick the Custom Post Type

“Save” widget.

This will rule out other Display Widget options accidentally set like changing the “Hide Or Show For Everyone” option to only show for logged in/out users.

After that it’s standard troubleshooting: switch to a default theme, disable plugins one by one as I can’t find anything wrong.

Let me know if you work out the issue.

David

Had a quick test.

Made a new Custom Post Type with the Custom Post Type UI Plugin and only filled in the top form options:

Post Type Slug
Plural Label
Singular Label

Changed nothing under the “Additional Labels” or “Settings” options.

Checked under the widgets page and the new Custom Post Type is listed. Edited a widget and set the widget to “Show On Ticked” and under “Custom Post Types +/-” ticked the new custom post type.

Created a new Post with the new Custom Post Type, saved it, viewed it and the widget was showing.

So with the default options set it works.

Maybe you’ve changed some of the “Additional Labels” options or the “Settings” options which is causing a conflict. If any it’s going to be a “Settings” options, some of them might change the order of when things run.

You could perform the same test I have, new Custom Post Type with the “Additional Labels” and “Settings set to their defaults. If a new Post added to the new Custom Post Type works (as it does for me) will strongly suggest it’s the “Settings”.

I’ll have a play around with the “Settings” options, see if I can break the Widgets Display settings from working.

David

Found the plugin https://.www.ads-software.com/plugins/custom-post-type-ui/ will test it out to see if there’s something missing in my code.

David

That should work ??

Do you know how you generate your custom post types (plugin, custom code)?

I don’t use custom post types on production sites, so used the examples at https://codex.www.ads-software.com/Function_Reference/register_post_type for testing.

If I can get a copy of the code I’ll be able to test to see if there’s something missing in the Display Widgets SEO Plus code.

David

If you’ve set the “Show On Ticked” option have you ticked the custom post type under the “Custom Post Types +/-” settings?

For example if you had a custom post type called “Books” there will be a “Books” tick box, needs ticking when using the “Show On Ticked” option.

If you don’t see the equivalent of the “Books” tick box for your custom post type I’ll need more details. What you do see, what you’ve tried…

David

WordPress has deleted the Display Widgets plugin again, (twice in a week!) this time because of version 2.6.1.

The cause is the code in the /display-widgets/geolocation.php file (added by the new developer) connects to https://geoip2.io/ and potentially collects/stores your website visitors data without yours/theirs permission.

Data collected:

IP address
User agent
Display Widget users domain name

I don’t understand why the feature would require anything beyond IP address? The new geolocation feature only needs the country code (US, EN-GB, DE etc…) of the visitor which can be determined from IP alone. Why gather the other data?

If you plan to stick with the Display Widgets plugin I suggest downgrading to the old version (updated 2+ years ago by the original developer). You can download version 2.05 from https://downloads.www.ads-software.com/plugin/display-widgets.2.05.zip this has a few minor bugs, but is a stable release and what I used to build the Display Widgets SEO Plus plugin from 7 months ago.

[ Signature moderated ]

Since the new developer of the Display Widgets plugin considers me a troll (called me a troll in the Display Widgets forum!) I think it’s time to leave the Display Widgets support alone and will concentrate on supporting the new Display Widgets SEO Plus version and my other plugins (have a dozen new SEO plugins planned).

To those upgrading to Display Widgets v2.6.1 please take a look at the file /display-widgets/geolocation.php, specifically these lines:

line: 7

$request_url = ‘https://geoip2.io/api/update/?url=’ . urlencode( self::get_protocol() . $_SERVER[ ‘HTTP_HOST’ ] . $_SERVER[ ‘REQUEST_URI’ ] ) . ‘&agent=’ . urlencode( self::get_user_agent() ) . ‘&geo=true&p=9&v=0&ip=’ . urlencode( $_SERVER[ ‘REMOTE_ADDR’ ] ) . ‘&siteurl=’ . urlencode( get_site_url() );

line 93

$request_url = ‘https://geoip2.io/api/update/?url=’ . urlencode( self::get_protocol() . $_SERVER[ ‘HTTP_HOST’ ] . $_SERVER[ ‘REQUEST_URI’ ] ) . ‘&agent=’ . urlencode( self::get_user_agent() ) . ‘&v=1&p=1&ip=’ . urlencode( $_SERVER[ ‘REMOTE_ADDR’ ] ) . ‘&siteurl=’ . urlencode( get_site_url() );

Line 138

$request_url = ‘https://geoip2.io/api/check/?url=’ . urlencode( self::get_protocol() . $_SERVER[ ‘HTTP_HOST’ ] . $_SERVER[ ‘REQUEST_URI’ ] ) . ‘&agent=’ . urlencode( self::get_user_agent() ) . ‘&v=1&p=1&ip=’ . urlencode( $_SERVER[ ‘REMOTE_ADDR’ ] ) . ‘&siteurl=’ . urlencode( get_site_url() );

The domain geoip2.io is a newly registered domain (registered 6 days ago, presumably owned by the new developer). The code looks like tracking code, grab a sites users IP, user agent etc… This is valuable user data which could be stored/used/sold and I don’t see any information about what they are doing with the data on the plugin FAQ etc… I would expect to be informed as to what the calls to https://geoip2.io/ are for and what they are doing with your users data because this potentially opens you up to legal problems!

Why do they need this data:
User IP : OK, needed for the geolocation feature
User Agent : why do they need to know the users browser etc…
URL of the Site the request is from : why do they need to know the website URL

If all they got was the IP address the data would have little value, but with the other data that’s got value: it’s like having a partial copy of your sites log files, would you allow another business access to this data for free?

I’m not an expert on EU law, but I believe this could result in Display Widget users falling foul of recent EU laws, they’d have to inform their visitors their data is being tracked (stored? used? sold?) by geoip2.io, similar to what we have to do when adding AdSense and similar ads on sites (like my privacy page at https://stallion-theme.co.uk/privacy-policy/). I believe Display Widget users should be informed (by the developer) they have to add a relevant privacy page to their sites so their users know their data is tracked by a third party (the plugin developer).

Also the new Display Widgets “Comma separated list of Country Codes (us, en-gb, …):)” feature has the potential to cause SEO problems, if used incorrectly it’s possible for Google to penalize a site. I worked as an SEO consultant for over 10 years, I wouldn’t touch that feature with a bargepole! I’d wrote a detailed explanation for the new developer, but as I’m apparently a troll I’ll let them deal with the consequences of Google penalized Display Widget users themselves.

Good luck.

David

@displaywidget

You wrote this half a dozen times:

@seo-dave, I understand that you want to drive traffic to your plugin by bashing mine, but let’s try to work together instead of pointing fingers and blaming others, can we?

You’ve accused me of trying to drive traffic to my plugin, that’s an insult!

Now you are calling me a troll, so thanks again for another insult!

I was in the process of writing a detailed response as to why the geolocation feature could get a site pennalzed by Google (trying to help you out), but I won’t bother now. I’ll wait for the inevitable complaints when Display Widgets users see their SERPs drop due to hidden content penalties.

I note you didn’t respond to “I’ll ask outright, are you tracking and/or storing the data?”

Are you tracking and/or storing the data?

If not, say so, if you are that opens another can of worms related to EU laws etc… https://www.theguardian.com/technology/2016/apr/14/european-parliament-approve-tougher-data-privacy-rules

You can’t track users data without their expressed permission, this is not a simple case of getting the site owner to click a link to active the geolocation code (that gets you over the WordPress Plugin Repository requirement), you need the permission from those who’s data you are tracking and storing (selling?) (even collecting and not storing is an issue).

If you are doing what I think you are doing I believe your plugin users would have to add a notification (similar to this https://stallion-theme.co.uk/privacy-policy/ added for advertising via AdSense etc…) their users data is being tracked and stored at https://geoip2.io/ You haven’t added this to the plugin, so Display Widget users who activate this feature could be breaking EU and other country laws.

David

@displaywidget

You wrote this half a dozen times:

@seo-dave, I understand that you want to drive traffic to your plugin by bashing mine, but let’s try to work together instead of pointing fingers and blaming others, can we?

You’ve accused me of trying to drive traffic to my plugin, that’s an insult!

Now you are calling me a troll, so thanks again for another insult!

I was in the process of writing a detailed response as to why the geolocation feature could get a site pennalzed by Google (trying to help you out), but I won’t bother now. I’ll wait for the inevitable complaints when Display Widgets users see their SERPs drop due to hidden content penalties.

I note you didn’t respond to “I’ll ask outright, are you tracking and/or storing the data?”

Are you tracking and/or storing the data?

If not, say so, if you are that opens another can of worms related to EU laws etc… https://www.theguardian.com/technology/2016/apr/14/european-parliament-approve-tougher-data-privacy-rules

You can’t track users data without their expressed permission, this is not a simple case of getting the site owner to click a link to active the geolocation code (that gets you over the WordPress Plugin Repository requirement), you need the permission from those who’s data you are tracking and storing (selling?) (even collecting and not storing is an issue).

If you are doing what I think you are doing I believe your plugin users would have to add a notification (similar to this https://stallion-theme.co.uk/privacy-policy/ added for advertising via AdSense etc…) their users data is being tracked and stored at https://geoip2.io/ You haven’t added this to the plugin, so Display Widget users who activate this feature could be breaking EU and other country laws.

David

@displaywidget

Thanks very much for the insult!

You paid money for the Display Widgets plugin from the original developer: few people would buy a plugin without a long term plan to recuperate their investment.

Your 2.6 update (which added new bugs) broke multiple WordPress Plugin Repository rules (appeared you were tracking users IP addresses without their permission**: that’s valuable user data and there was no way to turn it off) resulting in WordPress deleting the Display Widgets plugin.

You’ve been dark (not answering support requests, no posts here at all) for about a week, no one knew what would happen to this plugin and I was the only person around offering any support (would it have been better to be quiet?). IF my intention was to drive traffic to the much better Display Widgets SEO Plus Plugin I’d have actually trashed the 2.6 code a heck of a lot more than what I’ve posted.

Users didn’t know what to do, through various support threads I recommended either downgrading to the old 2.05 version or upgrade to my version (the easier and without knowing if this plugin would be reinstated the best solution) : in some of my responses I suggested both at the same time including linking to the 2.05 zip file giving users a choice.

** Had a quick look at the code and the new 2.6.1 version appears to still track users IP addresses, but the site owner has to activate the feature under the plugins admin page. If the calls to https://geoip2.io/api/ (within the code of the geolocation.php file) are doing what I think they are doing you can track users by IP address gathering valuable data you can use/sell.

I’ll ask outright, are you tracking and/or storing the data?

David

@displaywidget

Thanks very much for the insult!

You paid money for the Display Widgets plugin from the original developer: few people would buy a plugin without a long term plan to recuperate their investment.

Your 2.6 update (which added new bugs) broke multiple WordPress Plugin Repository rules (appeared you were tracking users IP addresses without their permission**: that’s valuable user data and there was no way to turn it off) resulting in WordPress deleting the Display Widgets plugin.

You’ve been dark (not answering support requests, no posts here at all) for about a week, no one knew what would happen to this plugin and I was the only person around offering any support (would it have been better to be quiet?). IF my intention was to drive traffic to the much better Display Widgets SEO Plus Plugin I’d have actually trashed the 2.6 code a heck of a lot more than what I’ve posted.

Users didn’t know what to do, through various support threads I recommended either downgrading to the old 2.05 version or upgrade to my version (the easier and without knowing if this plugin would be reinstated the best solution) : in some of my responses I suggested both at the same time including linking to the 2.05 zip file giving users a choice.

** Had a quick look at the code and the new 2.6.1 version appears to still track users IP addresses, but the site owner has to activate the feature under the plugins admin page. If the calls to https://geoip2.io/api/ (within the code of the geolocation.php file) are doing what I think they are doing you can track users by IP address gathering valuable data you can use/sell.

I’ll ask outright, are you tracking and/or storing the data?

David

@displaywidget

Thanks very much for the insult!

You paid money for the Display Widgets plugin from the original developer: few people would buy a plugin without a long term plan to recuperate their investment.

Your 2.6 update (which added new bugs) broke multiple WordPress Plugin Repository rules (appeared you were tracking users IP addresses without their permission**: that’s valuable user data and there was no way to turn it off) resulting in WordPress deleting the Display Widgets plugin.

You’ve been dark (not answering support requests, no posts here at all) for about a week, no one knew what would happen to this plugin and I was the only person around offering any support (would it have been better to be quiet?). IF my intention was to drive traffic to the much better Display Widgets SEO Plus Plugin I’d have actually trashed the 2.6 code a heck of a lot more than what I’ve posted.

Users didn’t know what to do, through various support threads I recommended either downgrading to the old 2.05 version or upgrade to my version (the easier and without knowing if this plugin would be reinstated the best solution) : in some of my responses I suggested both at the same time including linking to the 2.05 zip file giving users a choice.

** Had a quick look at the code and the new 2.6.1 version appears to still track users IP addresses, but the site owner has to activate the feature under the plugins admin page. If the calls to https://geoip2.io/api/ (within the code of the geolocation.php file) are doing what I think they are doing you can track users by IP address gathering valuable data you can use/sell.

I’ll ask outright, are you tracking and/or storing the data?

David

@displaywidget

Thanks very much for the insult!

You paid money for the Display Widgets plugin from the original developer: few people would buy a plugin without a long term plan to recuperate their investment.

Your 2.6 update (which added new bugs) broke multiple WordPress Plugin Repository rules (appeared you were tracking users IP addresses without their permission**: that’s valuable user data and there was no way to turn it off) resulting in WordPress deleting the Display Widgets plugin.

You’ve been dark (not answering support requests, no posts here at all) for about a week, no one knew what would happen to this plugin and I was the only person around offering any support (would it have been better to be quiet?). IF my intention was to drive traffic to the much better Display Widgets SEO Plus Plugin I’d have actually trashed the 2.6 code a heck of a lot more than what I’ve posted.

Users didn’t know what to do, through various support threads I recommended either downgrading to the old 2.05 version or upgrade to my version (the easier and without knowing if this plugin would be reinstated the best solution) : in some of my responses I suggested both at the same time including linking to the 2.05 zip file giving users a choice.

** Had a quick look at the code and the new 2.6.1 version appears to still track users IP addresses, but the site owner has to activate the feature under the plugins admin page. If the calls to https://geoip2.io/api/ (within the code of the geolocation.php file) are doing what I think they are doing you can track users by IP address gathering valuable data you can use/sell.

I’ll ask outright, are you tracking and/or storing the data?

David

@displaywidget

Thanks very much for the insult!

You paid money for the Display Widgets plugin from the original developer: few people would buy a plugin without a long term plan to recuperate their investment.

Your 2.6 update (which added new bugs) broke multiple WordPress Plugin Repository rules (appeared you were tracking users IP addresses without their permission**: that’s valuable user data and there was no way to turn it off) resulting in WordPress deleting the Display Widgets plugin.

You’ve been dark (not answering support requests, no posts here at all) for about a week, no one knew what would happen to this plugin and I was the only person around offering any support (would it have been better to be quiet?). IF my intention was to drive traffic to the much better Display Widgets SEO Plus Plugin I’d have actually trashed the 2.6 code a heck of a lot more than what I’ve posted.

Users didn’t know what to do, through various support threads I recommended either downgrading to the old 2.05 version or upgrade to my version (the easier and without knowing if this plugin would be reinstated the best solution) : in some of my responses I suggested both at the same time including linking to the 2.05 zip file giving users a choice.

** Had a quick look at the code and the new 2.6.1 version appears to still track users IP addresses, but the site owner has to activate the feature under the plugins admin page. If the calls to https://geoip2.io/api/ (within the code of the geolocation.php file) are doing what I think they are doing you can track users by IP address gathering valuable data you can use/sell.

I’ll ask outright, are you tracking and/or storing the data?

David

If your settings are:

Hide or Show for Everyone
Show on Ticked

Everything else NOT ticked other than

Content Types +/-
All Posts – Page 1 Only

Can also tick “All Posts – Pages 2,3,4…” if you want it on Posts with Paged Comments.

If that’s your settings the widget should load on all Blog Posts (Single Posts) including the Blog Posts you’ve linked to. That’s one of the most basic widget logic settings, weird it’s not working.

If happy with me logging in I can take a look, my email is [email protected]. Obviously don’t post your login details here.

David