OnPoint Plugins

← Back to support

How to update ALL Urls

Resolved

Requested: 1 month and 3 weeks ago

Dear support team,

we are facing the following issue with the Go Live Update Urls PRO plugin and kindly ask for your help.

We had to change URLs from http://deutex.fr to https://www.deutex.fr. This was done by using your plugin which did a great job so far.

However, some of the ancient URLs still appear to be loaded when typing www.deutex.fr in the Firefox or Google Chrome web browsers address bar. Thus our webpage is recognized as unsecure because a total of 18 elements are appear in the web browsers insepctor tool to still have old URLS as their source.

We have run the search and replace process several times again – without success.

How can we make sure that ALL old URLs, especially those recognized by the web browser as unsecure, are renamed to their new sources https://www.deutex.fr, please ?

Kind regards,
Masih

  1. Hi Masih,

    I ran the plugin using the URL without the trailing slash. This replaced the final 30 URLS.

    It appears the URLS on your site have been replaced correctly and are ready to go.

    Looks like all you have left to do is redirect your http viewers to https.  There a many methods to enable forced https, here are a couple:

    Add forced SSL to your site’s .htaccess file

    RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$  https://www.deutex.fr/$1 [R,L]

    Use a plugin

    The “WP Force SSL” plugin is designed to redirect all traffic from http to https via the settings.

    Disclaimer: We de not endorse, build, nor maintain the WP Force SSL plugin.

  2. Hi there,

    many thanks for your reply.

    First of all, we thank you very much for your help and for pointing to the force SSL direction. It seems that we have solved the https browser security issue by applying the code described in the thread here – thanks a lot!

    However, we are facing various theme issues since this morning (European time) which we still have to understand (see files attached). One possible source could be the renaming of the URLs as you describe in your email below.

    Good news after all is the fact that we have made a backup prior the URL renaming process.

    Anyways, may I kindly ask you to have a look into the files attached to this email and give us your opinion on whether or not those issues described are related to the latest URLs renaming process from  OLD: http://www.deutex.fr to NEW: https://www.deutex.fr, please.

    We really hope to identify the core problem of all those issues so that maybe we do not have to restore the update, this might save us some work done on the webpage in between the backup and the issues occurring.

    Your help is highly appreciated,

    Kind regards,

    Masih

  3. Hi Masih,

    I took a look at your screenshots and the corresponding sections of the site and I was unable to recreate the issues described:

    1. On the edit users page, I’m able to generate passwords.
    2. On the Updraft Backup/Restore page, I’m able to use the tabs like normal.
    3. The rest appear to be Woocommerce areas which may currently not be active as I’m unable to locate them.

    Based on the described symptoms, it sounds like you have a JavaScript error somewhere. As this plugin does not load JavaScript on any page except for it’s own “Tools” page, it is likely not a conflict with this plugin. Just to rule it out, I tried activating this plugin, and the issue did not occur so we can rule that out.

    Even though our plugin is not the cause, if you are able to recreate the issue and post the the output from your browser console, we may be able to point you in the right direction. If you’re unable to retrieve your browser console output, we can retrieve the output ourselves, if you are able to provided steps for us to reproduce the issue (as we have not been able to reproduce the issue so far).

  4. Hi there,

    Thanks a lot for, I really appreciate your help.

    I disabled all plugins and it seems to me that the Jquery / Java Script problem still persists. Please find attached the console’s error log.

    Here are the errors :

    • Uncaught ReferenceError: wp is not defined
    • Uncaught ReferenceError: jQuery is not defined
    • Uncaught TypeError: wp.i18n is undefined
    • Uncaught ReferenceError: moment is not defined
    • Uncaught TypeError: wp.date is undefined
    • Uncaught TypeError: o.widget is not a function

    Maybe renewing the WordPress core files solve this issue ? I have to admit that I have no idea what to do next.

    Kind regards,

    Masih  

    Ps : the console error log comes from a FireFox browser, I also checked on Google Chrome browser and the Jquery / Java Script problem is also visible, so I guess that the issue is not related to the browser itself.

  5. Hi Masih,

    I tracked down the issue to a specific endpoint. For example if I use a VPN to access your site from Denver Colorado, I’m able to access the admin without issue and the console nor UX errors do not exist. However, if I access your site from Paris France the errors are showing the console and I’m able to recreate your issues.

    When I access a JavaScript file from Denver (for example: https://www.deutex.fr/wp-includes/js/wp-util.min.js?ver=5.5.3) it being served from Cloudflare with a status of “BYPASS” and everything works as it should. When I access the same file from Paris, it is being served from Cloudfare with a status of “HIT” and then is redirected over and over until it fails.

    The first possible cause is Cloudflare needs to be reconfigured to work with the www or https version of the URL. If I enter the same URL without the www it works fine https://deutex.fr/wp-includes/js/wp-util.min.js?ver=5.5.3.

    Next, I see the network is still configured to be http instead of https as you can see in the network settings. =Most likely they are set in your wp-config.php. I also see the main web site URL is set to http://deutex.fr so you’ll want to look for that URL anywhere in your wp-config.php and update it. To update the site domain in the database, you may run this plugin without the schema (deutex.fr) as the domains are stored in the network tables without any scheme.

    Lastly, it’s possible something within your .htaccess is redirecting the assets. You could try removing sections of your .htaccess to see if something in there is the culprit.

    Hope this helps!

  6. Hi there,

    this is to inform you that we solved this issue and that it was not related to your plugin.

    We thank you  very much for your help and for your comments that helped us to understand more in detail the source error and thus to find a solution to the problem.

    Many thanks and have a good day.

    Kind regards,

    Masih

Respond