WordPress.org

Ready to get started?Download WordPress

Forums

Lightspeed Systems filtering (4 posts)

  1. orangekoi
    Member
    Posted 5 years ago #

    OK. I do not have a wordpress.org site, however, I do have a wordpress.com site. Here's the issue. I have built a wordpress.com site for teachers for a school district. The district's filtering system automatically blocks the site since it is "tagged as a blog in the code", or so I've been told by the IT people for the school district.

    I appealed to have the site unblocked and they agreed. However, now the main domain is unblocked, the subdomains that contain the templates, photos, formatting, etc are still blocked. WordPress.com support identified all of the subdomains and suggested having the district unblock all of them. However, this route would require me to have future subdomains created for my site to be approved as well. This sounds like more of a pain than I want to deal with.

    My idea now is to convert the site to wordpress.org and pay for web hosting. However, like I mentioned before, I was told that the "blog tag" in the code was the first clue that the filtering system used to block sites. With access to the code, would I be able to remove all of these triggers to the filtering system? Does this solution sound like it would work?

    Any help is appreciated.

  2. whooami
    Member
    Posted 5 years ago #

    wtf is "blog tag"?

    when you figure out what that is, then do whatever you need to do.

  3. orangekoi
    Member
    Posted 5 years ago #

    From my understanding after a conversation with the information systems person, there is something in the source code that identifies my website as a blog. I personally am not a Jr. Network Administrator, so I may have used the wrong terminology so bear with me.

    The rest of my questions stands. If my site is built using wordpress.org, can I remove the triggers from the source code?

    Thank you whooami for your help so far.

  4. whooami
    Member
    Posted 5 years ago #

    The rest of my questions stands. If my site is built using wordpress.org, can I remove the triggers from the source code?

    that is NOT what you asked above.

    You asked this:

    With access to the code, would I be able to remove all of these triggers to the filtering system? Does this solution sound like it would work?

    And my answer still stands.

    The above is predicated, like I said, on knowing what to remove.

    The answer to your rephrased question is exactly the same. Once you know what to remove, remove it. WordPress is open source software. You dont need anyone's okay to alter the code.

    And just for clarification, your site isnt built using wordpress.org -- wordpress.org is the domain that hosts and supports the FREELY available open source version version of wordpress.

Topic Closed

This topic has been closed to new replies.

About this Topic