• Ive installed a backup of my blog manually with a xcloner backup (same location – new database) and in settings permalinks Im getting a error. All my permalinks call up properly just in the settings I have a notification.

    In Permalinks Settings Im Seeing:
    “Something has gotten mixed up!

    Your siteurl option is set up as https://www.my name.com/blog, but your WordPress.com connection lists it as 0!

    Your home option is set up as https://www.my name.com/blog, but your WordPress.com connection lists it as 1!”

    I have these options, Ive tried them all except ignore:

    1. “The data listed above is not for my current site. Please disconnect, and then form a new connection to WordPress.com for this site using my current settings.”

    2. “Ignore the difference. This is just a staging site for the real site referenced above.”

    3. “That used to be my URL for this site before I changed it. Update the WordPress.com Cloud’s data to match my current settings.”

    I edited my .htaccess & wp-config.php, to try and fix it. I have deauthorized and reauthorized jetpack.

    in wp-config.php I have:

    /** MySQL hostname */
    
    define('WP_SITEURL','https://www.my name.com/blog');
    define('WP_HOME','https://www.www.my name.com/blog');
    define('RELOCATE',true);
    define('WP_SITEURL','https://www.my name.comm/blog');
    define('WP_HOME','https://www.my name.com/blog');
    define('RELOCATE',true);define('DB_HOST', 'localhost');

    this is my .htaccess file

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /blog/
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /blog/index.php [L]
    </IfModule>
    
    # END WordPress

    Im using WordPress 4.2, TwentTwelve Theme 1.7 & CHild Theme, Jetpack 3.5

    Any help appreciated.

Viewing 15 replies - 1 through 15 (of 26 total)
  • Anne

    (@chilathecockedronsismaltori)

    Wfeu, we had the same issue/message this morning. We got that message when trying to update our site to the latest version of WordPress.

    Recommendation we received from one of our tech resources: “Disable JetPack – upgrade to WordPress 4.2, then reinstall JetPack – (this is a JetPack bug of sorts it seems).”

    We deactivated Jetpack, updated to 4.2, then reactivated Jetpack. All appears to be working well at this point…

    Same thing happened to me, however I’m not able to update to WP 4.2 because of managed hosting by GoDaddy it seems.

    managed hosting by GoDaddy it seems.

    Then you’ll need to talk to GoDaddy.

    I’m getting the same error when I go into the Plugins page. I’m also using WP 4.1.2 with GoDaddy managed hosting.

    Anyone got a resolution yet?

    By the way, I got two sites at GoDaddy, and I get the error only in one of them. I’m not 100% sure it’s their fault.

    I got this message today too and have GoDaddy hosting. Anyone find a resolution yet?

    Me as well.

    I guess it does relate to GoDaddy, then. Anyone contacted them as of yet?

    I was actually on hold with them and during that time I deactivated and reactivated Jet Pack, connected to WordPress and now the message is gone.

    I deactivated JetPack and it fixed the issue as well. However, I cannot update to WordPress 4.2 from 4.1.2 using GoDaddy’s managed WordPress hosting. Only o Linux cPanel. I guess that GoDaddy hasn’t pushed the update yet.

    Also, of note, I got a response from the JetPack team lead in Slack and he states that a debug patch got shipped before it was ready.I’m sure a patch will be released shortly

    Ohhhh dang it…the message came back ?? I’m going to try calling again.

    happyhealthfreak, please update us with their response.

    Just FYI for non Godaddy-managed folks:

    I host elsewhere (pair.com); I tried the deactivate/activate sequence after upgrading WP and updating Jetpack. That seems to have cured it for me. But, this is on an extensive multisite and I had to reconnect each site once I had activated Jetpack again.

    OK so I spoke to the hosting support at Go Daddy and he said Jet Pack is on top of these updates and it should work itself out. While I was on the phone with them the message disappeared for the second time. So it looks like it has worked itself out on my end…hopefully!

    Is there a way to force a WordPress update from 4.1.2 to 4.2 on managed WordPress hosting?

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Jetpack – Permalinks – "Something has gotten mixed up!"’ is closed to new replies.