Forum Replies Created

Viewing 7 replies - 16 through 22 (of 22 total)
  • Forum: Fixing WordPress
    In reply to: Blank page
    Thread Starter mscott

    (@mscott)

    I can’t get into the wp-admin section to disable. But, yes, I renamed all of the plugin directories in the wp-contents/plugins directory and tried, got the same blank page.

    Even tried renaming the wp-contents/plugins directory, still no dice.

    Thread Starter mscott

    (@mscott)

    See, that’s where the confusion settles in.

    “WordPress 4.2.1 is the only, safe version”

    “except for WordPress 4.1.4 and WordPress 4.0.4 right now… That may change later… or not”

    You can’t support older versions and not support the older versions at the same time.

    I’m all for forcing everyone to upgrade to WordPress 4.2.1 if they want to be secure. If people don’t like it, then they can use something else.

    You can’t say that there’s only ONE version of WordPress and then claim that WordPress 4.2.1, WordPress 4.1.4, and WordPress 4.0.4 are safe versions. You can say that there are THREE versions and list those accordingly as 4.2.1, 4.1.4 and 4.0.4. OR you can say there is ONE version, 4.2.1.

    That’s my two-cents anyway.

    Thread Starter mscott

    (@mscott)

    So what are safe versions of WordPress?

    4.2.1
    4.1.4
    4.0.4

    ???

    How long has WordPress been supporting multiple release trees? I really didn’t know they were still supporting the 4.0 tree.

    The problem I have with this (and I realize I may be preaching to the choir) is it makes it difficult for web hosts to know what is and isn’t secure on their servers.

    Up until WordPress 4.2 was released, I didn’t know that multiple release trees were being used. When WordPress 4.1 was released, I assumed that WordPress 4.0 died and everyone should be using WordPress 4.1.

    This made it easy to scour through our web hosting servers and find any WordPress script that wasn’t WordPress 4.1(.X) which we then encouraged users to upgrade or face security risks.

    Now – I guess – I’ll have to start looking for WordPress 4.0.4, 4.1.4, and 4.2.1. It would be easier if there was only ONE version – WordPress 4.2.1. If users don’t have to upgrade – featureset wise – then they won’t. This will lead to a lot of confusion (IMHO) later on. The more release trees you support, the multiple of the headaches involved.

    In the interim, it would be nice to have a page on WordPress’s website that ALWAYS lists what the latest version(s) are.

    Appears to have been a bad DNS resolver on the server. Removing that solved my problem.

    This normally a configuration error on the server. Please contact your host.

    Can you be more specific? I don’t know what has changed on the server to cause this.

    Thread Starter mscott

    (@mscott)

    > – Deactivate all of your plugins

    Tried this, no change.

    > – Switch to the Twenty Fourteen theme

    Tried this, no change.

    > – Clear your browser’s cache and cookies

    Didn’t try this, but I logged in from 2 other computers, both of which had never logged into the WordPress admin panel, no change.

    > – Re-log in and try to update again

    No change.

    Forum: Fixing WordPress
    In reply to: Redirection
    Thread Starter mscott

    (@mscott)

    At the root – http://thedomain.com

Viewing 7 replies - 16 through 22 (of 22 total)