Another note on using code in wordpress

I’ve read the WordPress help page on using code, but still it seems like in practice, what works and what doesn’t is hit or miss. For instance, the code help page states, “Flash and all other embeds are not allowed in WordPress.com posts, pages, or text widgets. For security reasons, we remove the tags needed for these to work.”  The emphasis on all other embeds is mine.

Well, it some cases that is true, and they do “remove he tags needed for these to work.” But let’s test this rule here to show it is inconsistent.

from the Internet Archive.

That, my friends, is an embed code that appears to be working on WordPress.com. However, if I were to add the height and width code, it would not work. Inconsistency is what is bothering me. In fairness, it seems as though WordPress is treating this particular form of embed tag as a video tag.

But it is not only that, it is the fact that most of this code works throughout the internet, but not WordPress.com. This is….well, inconsistent.

“Inconsistent” seems to me to be the word to use when referring to the way html is handled on WordPress. And that is why, with the exception of the audio or video tag (most of the time), and YouTube or Vimeo (also, only most of the time), html should be avoided on WordPress.

After all, I could achieve the same end with a simple link, which WordPress apparently still supports. Thus, play or download movie.

Thank you and good day to you, and good luck. Over and out.

 

Ok,I’ve been too hard on WordPress and code…

But it doesn’t explain all the problems. However, this one problem was my fault. So, I’ll try again to embed my Google site with a video player set up:

Oh, now I see why that can’t work because of security reasons. Never mind. My bad on that one, but some of the other embed and video tag problems still haven’t made sense to me.

Broken tag generator

By the way, WordPress has a technical problem with the tag generator for tags on posts. It won’t let me pick any of the pre- generated tags that are already in the list to use. It simply closes the list each time. I hope it isn’t something wrong specifically with my blog, as in malware, but I can’t imagine that being the case. It is likely a technical problem on their end.

Test of Opera with WP, Opera is Super Fast

just a test of uploading with Opera, which I thought WP didn’t like so much- or perhaps it was another site that protested. Anyway, the Linux version of Opera is likely old, but very fast. Super fast in fact. Update: Oh right, it was a certain mini-blog platform that begins with “t” and ends with “r.” That’s the one that didn’t like Opera.

Maine, from a while back. Acadia.

Maine, from a while back. Acadia.

Google Console, crawl errors, and SEO- What does it all mean?

I have a few online places, including this one, that I check with Google Console now. Apparently, this site is doing well, with no errors, although the crawl stats are less impressive than some of the other sites. Oddly, a couple of blogs I have using another blogging platform (shh…Google), have crawl errors, even though the crawl stats seem to be higher currently.

What does it all mean? Does it matter much really at all? I suppose it makes me inclined to use this one more, as the Google seems to be telling me it is the one functioning best. Of course, I don’t understand the way the whole thing works entirely. They call it SEO (Search Engine Optimization), and it seems to change based upon the weather or something.

So, maybe WordPress knows what it is doing after all. I thought they were just making certain things (like html code on the blog) difficult just because. Maybe, it is helping SEO. I don’t know really.

But I do know that I’m inclined to use the site that makes those issues the least burdensome, and from what I can see currently through the Console dashboard (although it will likely change over time), this site is performing well enough for now. Oh, Google…sigh.