Text widget flash clock has disappeared

• 

  dragonkatet · Member · Feb 19, 2015 at 8:13 pm

  • Copy link
  • Add topic to favorites

  Hi. Ever since I have had my blog here on WordPress (dragonkatet.wordpress.com), I have had a flash clock as a text widget in the sidebar, primary widget position at the top, followed by several images.

  The text widget required the use of a [gigya src] code to make the clock show up as visible.

  I have noticed that the clock is no longer showing as visible. Why not?

  I have researched and discovered that:

  “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. Your intentions may be innocent, but someone somewhere might try to use such embeds to damage the site, affecting all of our users.” From your page here: http://en.support.wordpress.com/code/

  My questions are:

  1) Why was I allowed to have my flash clock as a text widget for ALL these years if it is/was not allowed?

  2) Is this removal of the gigya src code a new policy? And if so, how do I put a clock on my blog? I DO pay for extra storage space/media, if that helps.

  3) If a flash clock is no longer allowed, you *might* want to remove old topics about clocks in side text widgets, because I am guessing I am not the only one with a flash clock on his/her blog and it would be nice to know these things. I imagine others will be searching the support forums for relevant information about why their clocks may have disappeared.

  Example of an old thread that should probably be deleted if it is no longer relevant: https://en.forums.wordpress.com/topic/wpcom-clock-widget?replies=2

  Please let me know how I can put a clock on my wordpress.com blog.

  The blog I need help with is: (visible only to logged in users)

• 

  jeremeylduvall · Member · Feb 19, 2015 at 11:15 pm

  • Copy link

  Hi,

  The Gigya embed code has stopped working due to a shift from HTTP to HTTPS for your site dragonkatet.wordpress.com. The only two ways around this currently would involve either of the following:

  1. Host the Gigya URLs over HTTPs. They’re currently being served over HTTP. This isn’t likely to happen.

  2. Purchase a custom domain on your site to force it to HTTP. This isn’t really a long-term solution. We just do not provide HTTPS certificates for mapped domains at the moment so your site would be served over HTTP with a custom domain.

  Thanks for the alert about the previous forum threads! We likely won’t be going back and addressing them all as we never officially supported Gigya codes. However, if individuals have questions, we’re happy to answer them!