OnPoint Plugins

← Back to support

There has been a critical error on your website. Please check your site admin email inbox for instructions.

Resolved

Requested: 4 years and 8 months ago

 

Hello,

Obviously I’m trying to fix a lot of URL issues with my live site migration that point back to my old staging site.

I installed the basic version, then upgraded to pro (both are active).

I then entered the old URL: http://qg6.ebd.myftpupload.com/

I entered my new URL: https://adtutoring.com/

Hit the test button and got:

Verify the Old URL and New URL have matching trailing slashes.
Both urls have a trailing slash.

Verify the Old URL and New URL have matching structures.
Both urls have a scheme.

 

Verify this site is accessible from the New URL.
This site is accessible from the New URL.

So everything looks fine, I have a backup so not too worried, I click on the “Update URLS” button and after a couple seconds I get:
There has been a critical error on your website. Please check your site admin email inbox for instructions.
I click back and refresh the page, click on the Previous Actions made to the site URL just to see if anything was recorded and I see:

Site Address (URL) History

Old URL
New URL
Date

https://adtutoring.com/
https://adtutoring.com/
January 5, 2020 @ 10:27 am
Use

Close Results

Why is it using the Old URL with the value of the New URL?  There is a redirect for that Old URL to the New URL (ie if you enter it you will be redirected to the new URL) but I didn’t expect that it would impact this… if that is indeed whats happening.

I suppose I can do this the manual way inside the database but I was hoping for a plugin fix that would be quick and easy 🙂

  1. Hi Lee,

    Are you able to send me a copy of your server’s PHP error log? The last couple pages right after this plugin has been run would be helpful to track the issue.

    Otherwise, did the site perhaps send you an email with the error listed in it?

    As far as the history showing the Old URL, my hunch is process does not get that far before the server error so it is not being recorded properly.

    Mat Lipe

  2. The error I get is:

    [06-Jan-2020 18:28:36 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 204800 bytes) in /var/www/wp-includes/wp-db.php on line 1995

    Thats the only error generated when I try to use the plugin.

    I’ll see what I can do to increase the memory size for PHP, but being a hosted site I haven’t found a way yet, I’ll reach out to GoDaddy tech support in a bit to see what they say.

  3. Hi Lee,

    There are a couple of workarounds with may resolve the memory issue:

    1. You may selected one or more sections to update at a time instead of running all of them at once. This will reduce memory usage a little per run.
    2. By adding the following filter to your active theme’s functions.php file, the memory limit will be set to 512 instead of 256 during this plugin’s runs only.

    Hope this helps!

    Mat Lipe

  4. Ok so running them 1 at a time reports

    The URLS in the checked tables have been updated.

    Awesome, but how do I know that its indeed worked.  For example if I am tediously running this for every table how can I check and be sure its worked?

    I assume I can inspect that element with the chrome browser and check an images src setting?

    ie: on my home page https://adtutoring.com there is an image of two ladies to the right of “The Best Tutors in Edmonton” it originally has  an element of:

    <img class=”uabb-photo-img wp-image-2242 size-full lazyloaded” src=”https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img/tutoring-post-secondary-student-best-tutors-in-edmonton” data-src=”https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img/tutoring-post-secondary-student-best-tutors-in-edmonton” alt=”Tutoring Post Secondary in Edmonton” itemprop=”image” data-srcset=”https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img,w_510/tutoring-post-secondary-student-best-tutors-in-edmonton 510w, tutoring-post-secondary-student-best-tutors-in-edmonton-300x225 300w” data-sizes=”(max-width: 510px) 100vw, 510px” sizes=”(max-width: 510px) 100vw, 510px” srcset=”https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img,w_510/tutoring-post-secondary-student-best-tutors-in-edmonton 510w, tutoring-post-secondary-student-best-tutors-in-edmonton-300x225 300w” title=”Tutoring Post Secondary Class”>

    You can see that some of the src/srcset/ etc… values are just weird.  I don’t know what happened when GoDaddy migrated the site for me.

    There seems to be a few variants that need to be updated:

    https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img/https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_510/https://adtutoring.com/

    https://cdn.shortpixel.ai/client/to_webp,q_glossy,ret_img,w_510/https://adtutoring.com/

    https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_300/https://adtutoring.com/

    although only the SRC needs to be fixed now…

    If I select the _posts table for update it says updated… but the src on that image remains unchanged.

     

  5. Hi Lee,

    If the plugin reports that it has completed, then it did run. One way to check this is to do a search in the database table for the value you are changing before and after to see the changes.

    Here are some things to check if you are not seeing updates on the front end:

    1. Flush any page/server caches which could be storing content such as caching plugins or varnish.
    2. Double check the old field to make sure it matches exactly to what you expect to be changed.
    3. If going table by table, double check the expected table is actually the one containing the values you expect to be changed.

    If you are still having trouble, please send me the following so I can look into it:

    1. URL to where I can see the old value.
    2. Entered old value.
    3. Entered new value.

    Have a great night!

    Mat Lipe

  6. Ok its indeed working just fine!  Thank you for your time, that last message I sent was a red herring as I’d completely forgotten that Short Pixel had been enabled prior to migration and it was causing some issues as well – ugh.  Switched it off and everything is working great no more artifacts from the migration!

    Thanks for your patience and hope your new year is going great!

New Response

You must be logged in to respond. Only PRO members are allowed to respond to support requests.

We use cookies to allow login, checkout, and analyze site traffic. By continuing to use this website, you consent to the use of cookies in accordance with our cookie policy.

Cookie Settings