msgarvin

After reverting the site back to 2.5.1, the pages are loading fine. An instruction in the lazyloader didn’t work in the initial update attempt and this was apparently corrected by rolling back.

Just another clarification on the issue of the incorrect URL being created for the shortpixel cdn.

QUOTE:
Additionally some url’s to shortpixel are wrong,
e.g. https://cdn.shortpixel.ai/client/q_lqip,ret_wait,w_32,h_32///%5Bdomain.com%5D/wp-content/plugins/gtranslate/flags/32/zh-CN.png

while it should be
https://cdn.shortpixel.ai/client/q_lqip,ret_wait,w_32,h_32/https://%5Bdomain.com%5D/wp-content/plugins/gtranslate/flags/32/zh-CN.png
END QUOTE

The original URL is in fact a correct rendering. This is a cloned environment for dev and testing (rather than using a live environment). As a subdomain, it cannot be located with https.//www.. In this instance, the correct prefix is clone912. Hence, there is one forward slash to end the shortpixel component and two slashes to locate the image file URL. Having ‘https:’ in between would most likely throw a 404 error.

Another issue that I found in a deeper dive into the code:

<img width=”1357″ height=”620″ src=”data:image/svg+xml,%3Csvg%20xmlns=%22https://www.w3.org/2000/svg%22%20viewBox=%220%200%201357%20620%22%3E%3C/svg%3E”

is a piece of Google translate code that had also stopped functioning.

Eventually, I had to assume that the platform itself was in a fragile state and the plugin didn’t have an adequate environment in which to perform. I’m no longer working on this project but wanted to bring this around to closure as best I could.

Thanks again for your assistance.

HI –
Thanks for the quick response. Shortpixel mentioned the link creation as being incorrect. They too don’t have any answers. It is highly probable that the link changes are a result of the upgrade from 2.5.1 to 2.6.1. This was the third plugin updated in a sequence to prep the site for a migration to the production environment. I always update each plugin separately and test various pages and functions to ensure nothing broke or to isolate what broke. Testing begins usually more than ten minutes after installation to allow server propagation and caching.

What process do I need to use to revert this to 2.5.1? I’m establishing a dev environment with a completely clean install from scratch but that will take time to ramp up for production release. I prefer not to touch the live environment, only to migrate tested updates. I’m looking for an interim solution to get the content live without manual updates.

Thanks again for your assistance.
Michael

Kubiq,
Thanks again for your response. Even though restoring a previous image of the site did not work, restoring a previous Db file did. The staging environment is whole – ish again.

Thanks
Michael

Thank you for your assistance so rapidly. Very much appreciated.

I have recently taken over on this website to assist with resolving numerous problems. I myself am not a programmer, just a detailed analyst. The installation is dirty. When I first looked at it, there were 7 themes installed, three had been configured and abandoned. There were some 50 plus plugins of various stages of overlap and conflict. Systematically, I moved the team from doing anything to the live site and work exclusively on this clone site. Since that effort stabilized, I have worked to remove everything that is not mandatory by the current theme and functionality. All extraneous themes and plugins have been removed and the data tables optimized. Page speed and other tests continued to show improvement as page functionality with WPBakery was streamlined and improved. Images are the most pressing issue at the moment which is why your plugin was sought.

While this is ongoing development, it has been my plan to create a clean installation of wordpress and the Porto themes so that all of the plugins and theme files can operate without any remnants or junk. From your message, it sounds like that should take precedence when I recover the current clone912 staging env.

I’ll let you know if the Db restore takes care of the ‘https:/.jgp/.jpgclone912…..’ issue.

Thanks again for your assistance.