Alexis Wilke
Forum Replies Created
-
In my case, I found out that my Apache setup was using .com for the “Directory” directive when my new domain name was a .app (I changed the VirtualHost TLD properly, but not the Directory).
That meant that the permalink did not work at all since the magical code as shown by sonofadoc was never seen by Apache2.
Once I fixed the TLD, everything worked like a charm.
@cdgweb It can help speed up a developer’s work if you change the code to test on your end and offer it to them in case it works. However, in this case, I don’t think it’s the correct behavior. They should instead look into not adding that page to the sitemap.xml (as others have done earlier.) I don’t personally see any value in having such a page in your sitemap.xml anyway. It’s not going to help your SEO.
No resubmit required. It may take a few days for Google to update their message, though. But it will just happen.
Alex
FYI, the problem arise as a compatibility issue because I have a plugin that compresses JavaScript. Now you could say that I should turn that off or that their stuff is bogus. Frankly, for a couple of
;, I think we can add them to your plugin. It will make your code that much stronger anyway.The compression (minifier) plugin that I use is named: “Minify HTML”
https://www.ads-software.com/plugins/minify-html-markup/
I would think that pretty much any JavaScript minifier will have the exact same problem with your code. So I wouldn’t put that on the back of the minifier.
Actually, for the same number of characters, you can replace the newline with the semicolon:
};var easy_fancybox_auto=function(){';And to save even more you can remove the spaces around the
=sign.- This reply was modified 6 years, 8 months ago by Alexis Wilke.
- This reply was modified 6 years, 8 months ago by Alexis Wilke.
Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkMy last argument about this one: The canonical URL is there with a default WordPress installation. So you should remove that feature altogether since it can’t work with a normal WordPress install. Or… maybe fix the code. ??
Anyway, I’m fine on my end at this point so I won’t sweat it any more than that.
- This reply was modified 6 years, 8 months ago by Alexis Wilke.
As a side note, the last
}in that script has the same problem, although it’s find because it’s currently the last character. My point of view is that it should also be ended with;. (Line 230, same file)Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkAnd obviously it’s not resolved, since you did not change any code, it just cannot be resolved.
Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkMy problem is this when I ask your plugin to remove the protocol & domain:
<link rel="canonical" href="/11-ways-of-promoting-your-niche-website/">That’s wrong. Just a path is wrong for the
href="..."attribute is wrong.I don’t care about the
/>part. Please ignore that part. That’s not what I reported.The canonical path MUST be a full URL including protocol, domain, and path.
Now, if I don’t turn on that feature, it works as expected, but of course all the other links also remain full, even those in anchors, etc. which could be optimized.
- This reply was modified 6 years, 8 months ago by Alexis Wilke.
Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkHow about concentrating on the real problem and not destroy the canonical link?
Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkI don’t know if its generated or my browser, but that’s a detail that the tag is closed with a slash, right? My document starts with
<!DOCTYPE html>, so HTML5.Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkOn the other hand, the line that adds the canonical link looks like this:
<?php wp_head(); ?>So I’m not too sure how I could add your comment just around that one link. On the other hand, all links should probably not be minimized in that sense. But the HTML code can still be minimized. So surrounding that php code with the
<!--[minify_skip]-->and<!--[/minify_skip]-->“tags” is not all that great.Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkAh, I see it’s already implemented. For a well known link that should not be minified, though, I think it should be automatic. I think most people are going to miss that one!
Forum: Plugins
In reply to: [Minify HTML] Your code breaks the Canonical linkComments? That would mean your theme would need to know to add those comments… right? Not likely to happen, I think.
Yes! That works. Thanks @mertij
That should be the default. I don’t think there is any need to even include that HTML page (maybe it already is the default I turned it on?!) Either that or the HTML page should not say “noindex”. Actually, if possible, if that flag is Enabled, then the HTML page should not say “noindex” and vice versa.
The page “exists”, it’s not listed in the “All Pages” dashboard, though. It’s generated dynamically by the Google XML Sitemap plugin.