This seems to be caused by a combination of different factors:
- You use a plugin to use shortlinks in your sharing buttons. When trying to share a post, your readers are actually sharing
https://wp.me/p4dEx6-5sN, and not the full post URL.
- WP.me Shortlinks do not redirect to the full post URL directly. Instead, they redirect to the default shortlinks on your WordPress installation. The shortlinks were designed this way, because default WordPress shortlinks redirect to the full permalink. Here is an example with my own site:
https://wp.me/p3Bu3Z-4Ho redirects to https://jeremy.hu/?p=18066, and https://jeremy.hu/?p=18066 then redirects to the full URL, https://jeremy.hu/tv-band-of-brothers/.
- On your site, however, default shortlinks do not redirect to the full permalinks anymore.
https://wp.me/p4dEx6-5sN redirects to https://www.giannellachannel.info/?p=21005, but https://www.giannellachannel.info/?p=21005 doesn’t redirect anywhere. Instead, it displays your home page. That’s why your readers end up sharing a link to your home page.
You consequently have 2 different ways to solve the issue:
- To quickly fix the issue with the sharing buttons, you could disable the plugin that enables shortlinks for Jetpack sharing buttons.
- However, on the long term, you will want to fix the underlying issue with your permalinks. Something on your site blocks short permalinks from redirecting to the full, pretty permalinks. It could be a caching plugin that caches all requests including a query parameter; it could be an
.htaccess rule you created when switching over to HTTPS; it could be one of the plugins you use to enforce the use of HTTPS on your site.
I hope this helps.
Thread Starter
TeoAu
(@teoau)
Thank you. I really don’t remember why I installed the shortlink plugin, disabling it eliminated the issue. Thank you!
Something on your site blocks short permalinks from redirecting to the full, pretty permalinks. It could be a caching plugin that caches all requests including a query parameter; it could be an .htaccess rule you created when switching over to HTTPS; it could be one of the plugins you use to enforce the use of HTTPS on your site.
I’m using “Really simple SSL” to coordinate mixed content; “SuperCacher” and CloudFlare plus: in CF plus I activated the “Standard caching” option and it should not be this the reason of the shortlink issue.
You can set Cloudflare’s CDN to cache static content according to these levels:
No Query String: Only delivers files from cache when there is no query string.
Ignore Query String: Delivers the same resource to everyone independent of the query string.
Standard: Delivers a different resource each time the query string changes.
We recommend using the Standard level.
Note: By default, Cloudflare does not cache HTML content. You can create a Page Rule to cache static HTML content.
Examples:
No Query String: example.com/pic.jpg
Ignore Query String: example.com/pic.jpg?ignore=this-query-string
Standard: example.com/pic.jpg?with=query
Thank you again
DT
CloudFlare indeed is most likely not what’s causing this issue. I’d recommend going through your other plugins to see where the problem lies.
