• Hi

    I’ve read a couple of support articles. This one seems close to my issue:

    https://www.ads-software.com/support/topic/site-kit-doesnt-work-after-migration/

    I recently migrated my site https://apbmodern.com from a server to wordpress.com hosting. On my server I had wordpress installed in a folder ‘wordpress’ in the root. On wordpress.com hosting wordpress is effectively installed in the root. The address to my wp-admin has changed as a result.

    After the migration Site Kit was saying another user had admin access (there is only one user). I reset Site Kit in Tools / available tools. I then got the regular message to connect to Analytics in the Site Kit Dashboard. I jump through my authroizations at accounts.google.com and get redirected back to wp-admin, but with the wrong redirect address (https://apbmodern.com/wordpress/wp-admin… rather than https://apbmodern.com/wp-admin…). I’ve tried amending the redirect URL in the browser window, but I get a timed out message.

    Is there a way to resolve this and connect Site Kit? Thank you!

    Regards
    Mike


    The page I need help with: [log in to see the link]

Viewing 15 replies - 16 through 30 (of 45 total)
  • Thread Starter bigflannel

    (@bigflannel)

    These are the domains I have an issue with trying to reconnect at the new host:

    upstatemetalsales.com
    movementsciencemadesimple.com
    laboskdesign.com
    karsh.org

    I also have more to move!

    Thank you.

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel That’s very helpful information thank you once more! I am going to pass this back to the internal team with all of the information you have shared and we can hopefully get a solution that works for you when migrating these sites.

    Could you please share the current sites you have run into this issue with so that I can share these with the team and investigate the records and correct if needed.

    Again this may take a day or two but as soon as I have more information I will get back to you here. Thank you for your patience it’s greatly appreciated.

    Thread Starter bigflannel

    (@bigflannel)

    Hi Adam

    These sites are currently have the issue:

    upstatemetalsales.com
    movementsciencemadesimple.com
    laboskdesign.com
    karsh.org

    Thank you!

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel Perfect, thank you! I have passed these on to the team to correct for you. I have also passed on all information on your migration steps to see if we can find a solution for you to avoid us having to correct these each time for you.

    As soon as I have an update I will share it with you here.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel The last batch of sites you have supplied should now have been corrected and you should be able to complete setup.

    Unfortunately at this time, there isn’t a way around this other than us to manually correct these for you as we have been doing. The good news is that the team are already aware of this issue and have been discussing it this week to provide a solution for it.

    I can’t say when this may be but it is being actively looked into at this time so if there are any updates to share then I will share them here.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel While we look to recreate this scenario and look for a fix, would it be possible for you to change the path inside wp-admin? Is there the option to you to change the wordpress path first, before migrating the site?Site Kit would then pick this change up on the service and you wouldn’t run into this issue.

    However we are still looking to address this particular issue and I will share any further updates with you here. Thanks for your cooperation and patience as always.

    Thread Starter bigflannel

    (@bigflannel)

    Hi Adam

    You mean in General Settings? The location of WordPress?

    Can you explain more? Where would Site Kit pick up the change from so that when its running at the new path it knows where it is? Why would an amended site on the same hosting and same domain not experience the same things as an amended site on new hosting with the same domain?

    I appreciate the suggestion.

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel Yes, that’s exactly correct. Changing the URL path in WordPress to the new path before you migrate the site will update the record on the service side to the new URL.

    When trying this you don’t need to delete the plugin as you have been doing. If you could try this and let me know if you have any success that would be great.

    Thread Starter bigflannel

    (@bigflannel)

    Hi Adam

    I am trying to think this through. If I change the WordPress admin site URL without changing the location of the files in the webroot, I imagine WordPress will stop working. When does Site Kit pickup the change: on change of the WordPress admin site URL, or at some other moment?

    If I change the location of the WordPress files, am I not back in the same position (at the same host, rather than a new one) where wp-admin is at a new location and Site Kit won’t reset?

    I am also trying to figure out sequencing of the migration, if I change the WordPress admin site URL before migration, and don’t move the files in the webroot, I imagine the migration will fail. So I migrate the site, then change WordPress admin site URL? Then update the DNS and Site Kit should reset at the new domain?

    Any guidance appreciated.

    Thank you.

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel Just to let you know that I have seen your latest response but I am awaiting further information before updating you. Thanks for your patience as always.

    Thread Starter bigflannel

    (@bigflannel)

    No problem.

    I just moved a site and attempted to amend the WordPress admin site URL. I ended up with the same issue on the migrated site, the redirect after Google authorizations still contains /wordpress/ and the login fails.

    This was my sequence:

    migrate site to new host (incl google site kit plugin, plugin not reset)
    have everything ready at new host for DNS change
    amend WordPress admin site URL on old host with DNS pointing at it
    site on old host breaks as expected after amending WordPress admin site URL
    amend DNS to point domain at new host
    when DNS resolved and pointing at new host try to reconnect Site Kit – it fails with /wordpress/ in the redirect URL
    reset Site Kit on the new host and try to reconnect – it fails with /wordpress/ in the redirect URL

    The current list of sites that need a reset if possible at your end are:

    upstatemetalsales.com
    movementsciencemadesimple.com
    laboskdesign.com
    karsh.org
    linccornell.com

    Thank you and I appreciate any guidance.

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel Thanks for the added information I have passed this on to the team to review and reset your records for you. I will update here once I have heard back.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    Hi @bigflannel Can I just check with you again if you have tried changing the admin url before migrating the site, not after? Or was this the problem you raised previously where this wasn’t possible for you to do so?

    I am still discussing this with the team to see what might be happening in your case and if this is something we can address or something we can give you a workaround for.

    Thread Starter bigflannel

    (@bigflannel)

    Hi Adam

    No. I have not tried amending the WordPress admin site URL before migration. Amending the WordPress admin site URL breaks the site unless I move the wordpress installation in the webroot.

    So I either have to amend the wordpress installation and then change the WordPress admin site URL, in which case, why is that any different to the migration? I am on the same host, but am amending the wordpress file locations and amending WordPress admin site URL. Isn’t that the same in effect as I am doing during a migration. Or, I amend WordPress admin site URL without changing the wordpress file location, the site breaks (front end and back) and I can’t migrate via plugin, I have to migrate manually. That might work, but is double the work, might not work, and the site is down during the migration. It doesn’t make sense and I still have not heard from you when Site Kit might detect the change (surely only if the admin is working), and my gut is it still will not work. You have not given any indication of when Site Kit updates: the hook, the action it happens on? I can’t see it happening if the site is broken, and I don’t understand why amending the WordPress admin site URL and wordpress file locations before migration is any different to a migration.

    Regards
    Mike

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @bigflannel Thanks once more for all the insights you have shared here. I have passed all the information on and once I have another update I will share here.

Viewing 15 replies - 16 through 30 (of 45 total)
  • You must be logged in to reply to this topic.