Need help? Check out our Support site, then

Creating mumble:// Links

  1. I want to directly link to our mumble server using a mumble:// url handler however it keeps getting striped out. I tried in a widget and in the body of a page.

    The blog I need help with is

  2. I don't have a clue what mumble is or what you are trying to do. This blog is a free hosted blog ie. it's on servers. There is no FTP access and we bloggers cannot install any plugins or software into free hosted blogs.

  3. This site is not even hosted by and we cannot help with it here at WordPress.COM. Support is provided on the WordPress.ORG support forums and they are here If you don't have a username account at, click that link and register one on the top right hand corner of the page that opens, so you can post to the correct support forums for your software.

  4. What is the actual code you are using for this? Post it here between backticks so it shows up.

  5. What does it have being a site have anything to do with this issue, its is the .com support forums.

    The issues is that I can't post URI's to non http/https links (I haven't tried everything. But the URI I want to use, mumble:// get striped out.

    Mumble URI Syntax

  6. <a href="36047/?version=1.2.3"></a>

    It gets striped down to a href to ?version=1.2.3

  7. Even this site does it in a code block..

    The href is mumble://

  8. This board is only for technical and account support

    for free-hosted sites.

    If your site is self-hosted, you need to check with your

    web host or the forums.

  9. Really people... the first post says

    The blog I need help with is

    and guess what, that is a site!

  10. Yes, and as a result, mumble code is stripped out here for security reasons. The mumble syntax is unique and not supported here.

  11. Is there any way to make make a mumble:// link on a .com blog without it getting striped?

    I don't really see how unrecognized protocols are a security issue? You first need a client for it installed for the link to even do anything.

  12. Not at You might be able to do it at WordPress.ORG.

    At we share the "guts" of our blogs, so any code not specifically allowed here is stripped out by default. That's because all blogs on any given theme share their security; any risk deemed acceptable by the dumbest user of that theme is shared by all users on that theme. This leads to a proactive security program that by definition prevents non-mainstream and even many mainstream options, like javascript and iframes.

Topic Closed

This topic has been closed to new replies.

About this Topic