YouTube Not Posting

  • Author
  • #574816


    @disembedded-I’m seeing the video in the post you linked above. No problem in Chrome. Checking FF and IE8 now.



    I really hope that a staff member takes a look at this issue!!



    @justjennifer That’s because I just changed the code for that one.


    I have already complained about the same problem with [AUDIO …] vs [audio ] tag. It appears that a change was made by wordpress to stop accepting capitalized tags, and only process all lower case tags. This change was not announced and is not backwards compatible. Although for the life of me, I can’t imagine the reason why case should be such an important matter.

    WordPress needs to revert this recent change, or make it backwards compatible. I am a paid subscriber and run an online magazine reviewing music, with embedded legal tracks for preview. This recent change has broken over 500 of my posts. I have no way of rectifying this on my end. The only thing I can think of is export, bulk replace, and import again, which, I am positive, will not go as smooth as it sounds.

    If my tone in this post sounds harsh, it is because I am very disappointed with this recent change, and the lack of proper testing prior to its implementation. I have followed the original directions for embedding audio and video, and now, these have ‘magically’ changed…

    I am looking forward to expedited resolution in this matter…



    This has created a terrible mess for me, and I’m sure for many others!



    @disembedded-pardon me for pointing out that if you want people to see the problem, it might be better not to fix it in the meantime. :/ Hope it all works out.


    My name is David D. Robbins Jr., and I run a music blog, Their Bated Breath, on wordpress.COM. The same thing is happening to me too disembedded. Well, at least it’s good to know it’s WordPress’ issue and not something I did. And yes, disembedded, this is a real killer of web hits. Ugh.


    Thank you, David… Precisely my point. Here’s a proof of a broken page:

    Here’s one where I had to convert from capital letters to lowercase for a workaround:



    @justjennifer- Thanks for your comments. Here’s an example of a recent posting that I haven’t fixed yet:


    Oh Lord, I just saw what was offered as a solution above and finally read your posts headphonecommute. You’re right. It’s is a matter of capitalization. At first when I read that I thought it might be a joke. Something wordpress did this afternoon means that I have to go and re-type every video embed code for 100s of previous posts? If that’s truly the solution, it’s nonsense. Complete WP rubbish if you ask me. A clear sign that self-hosting in a website format might be better for my future pursuits. Unbelievable. It’s like playing tennis for five years, and one day being told that all balls that hit the line are now considered out — with no explanation or warning by WP. And like you said headphonecommute — and at what advantage does the change make in realistic terms? I’m pretty upset too as you can imagine.



    Certainly no comfort to anyone, but all the shortcodes mentioned on this page are in lowercase letters.

    @disembedded definitely have to give Staff something to work with.



    @daviddrobins-You’re right…this is just plain horrible. I will have 100s of YouTube codes to find and re-type as well. Very grim business.


    I can assure you, that although today all of the shortcodes are in lowercase letters, they were once all CAPITAL. The best way to implement any shortcode is to just copy and paste it – correct? There would be no advantage for me to suddenly decide to capitalize the words. So it’s a bit unnerving that they ‘magically’ switched to lower case… Furthermore, a one line function to make the code case-insensitive would fix the problem.

    I think I am more unnerved than anything, at the fact that production change was rolled out worldwide, WHILE the entire support staff is on a week long retreat. Shouldn’t there be a policy for a change freeze, if there are no available support staff?



    Hi headphonecommute,

    You’re absolutely right. They gave no notice, and support staff is on a week long retreat. None of them are responding to this mess. I definitely wouldn’t call them “happiness engineers.” Would call them “[obscenity removed] engineers.”


    I just noticed too that it isn’t simply the lowercase, but it must be exact:
    [Youtube = http://www
    [youtube = http://www
    [youTube = http://www
    [ youTube = http://www
    ONLY …
    [youtube=http://www …

    That would be fine by me, if all the previous coding didn’t work perfectly fine before. Hey, the good news is my blog still works. What’s infuriating is that WP makes this change without telling anyone, and to no discernible advantage. I mean, there must be millions of blogs effected by this, but especially those dealing with movies, television and music videos. I’m nearly speechless. I’m almost reluctant to change, in the hopes that WP wises up and finds an easier solution or goes back to the way it was before. Clearly, this is a foul up.


    I run an international fan blog for Korean R&B artist Taeyang. His group Big Bang has just made their return after a two year absence yesterday. Their concert is this weekend. If I’m unable to post videos my site is sunk.



    @headphonescommute-Not to argue the point about when a change from upper to lower case shortcodes was made (and to the best of my memory it was always lowercase), but I’m looking at posts on my blog from 2007 with YouTube videos which are working just fine.

    Regardless, if all uppercase shortcode embeds worked previously, then hopefully a solution to the problem will be found.



    I agree…hoping a solution will be made.


    Yes. I think the solution can be applied quiet rapidly. And as I mentioned before, the origin of my greatest frustration stems from the fact that support is out on vacation while a new change was rolled out. I’m OK with occasional issues and bugs – those things happen. Anyone in this digital world of computers and software should understand that. But when a change is not tested and can potentially affect a large user base, the release schedule should be limited to emergency roll outs while your support staff is on vacation. I’d love to fume over this more, but I think I’ve made my point, and now I’ll patiently wait for a solution…



    Still patiently waiting for some staff member to wander down here where we peasants live, and say or do something about this problem.

The topic ‘YouTube Not Posting’ is closed to new replies.