kureman

Hi @pulak00,

Thank you for your fast and efficient help!

Unfortunately I’m not very comfortable with installing plugins manually… If it’s not too risky I’m willing to try, but I won’t be able to before next week. Otherwise I can wait for the next release.

Have a great day too!

Hi @habibjh ,
There are no more issues with this new version, thank you for your quick fix!

@glenn735-admin
Thank you for finding the error. Could you please explain how you found this log?

Hi @mamunnu

Sorry, I don’t have much to send you…

All the pages on my website are blank with the WordPress following message (in French):

“Il y a eu une erreur critique sur ce site.

En apprendre plus sur le débogage de WordPress.“

Then, the plugin Asset CleanUp displays the following message:

Note: The checked URL returned an error when fetching the assets via AJAX call. This could be because of a firewall that is blocking the AJAX call, a redirect loop or an error in the script that is retrieving the output which could be due to an incompatibility between the plugin and the WordPress setup you are using.

Here is the response from the call:

Status Code Error:500?* for more information about client and server errors,?check this link?Suggestion:Select "WP Remote Post" as a method of retrieving the assets from the "Settings" page. If that doesn't fix the issue, just use "Manage in Front-end" option which should always work and?submit a ticket?about your problem.

Output:WordPress ? Erreur html { background: #f1f1f1; } body { background: #fff; border: 1px solid #ccd0d4; color: #444; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif; margin: 2em auto; padding: 1em 2em; max-width: 700px; -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, .04); box-shadow: 0 1px 1px rgba(0, 0, 0, .04); } h1 { border-bottom: 1px solid #dadada; clear: both; color: #666; font-size: 24px; margin: 30px 0 0 0; padding: 0; padding-bottom: 7px; } #error-page { margin-top: 50px; } #error-page p, #error-page .wp-die-message { font-size: 14px; line-height: 1.5; margin: 25px 0 20px; } #error-page code { font-family: Consolas, Monaco, monospace; } ul li { margin-bottom: 10px; font-size: 14px ; } a { color: #0073aa; } a:hover, a:active { color: #006799; } a:focus { color: #124964; -webkit-box-shadow: 0 0 0 1px #5b9dd9, 0 0 2px 1px rgba(30, 140, 190, 0.8); box-shadow: 0 0 0 1px #5b9dd9, 0 0 2px 1px rgba(30, 140, 190, 0.8); outline: none; } .button { background: #f3f5f6; border: 1px solid #016087; color: #016087; display: inline-block; text-decoration: none; font-size: 13px; line-height: 2; height: 28px; margin: 0; padding: 0 10px 1px; cursor: pointer; -webkit-border-radius: 3px; -webkit-appearance: none; border-radius: 3px; white-space: nowrap; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; vertical-align: top; } .button.button-large { line-height: 2.30769231; min-height: 32px; padding: 0 12px; } .button:hover, .button:focus { background: #f1f1f1; } .button:focus { background: #f3f5f6; border-color: #007cba; -webkit-box-shadow: 0 0 0 1px #007cba; box-shadow: 0 0 0 1px #007cba; color: #016087; outline: 2px solid transparent; outline-offset: 0; } .button:active { background: #f3f5f6; border-color: #7e8993; -webkit-box-shadow: none; box-shadow: none; } Il y a eu une erreur critique sur ce site.En apprendre plus sur le débogage de WordPress.

Hello @maybellyne ,

Thank you for your answer, it’s very clear and I mark this topic as resolved!

Hi @mateuszgbiorczyk

Thank you again for your answer. You’re right, the quality issue is not due to Converter for Media, it’s as you said a problem with the resolution of the displayed image. I don’t know how to get a better quality yet..

I thought the TinyPNG plugin, which duplicates the original image into multiple images fit for woocommerce etc might help here but I don’t think it does.

Anyway, I close this topic since your plugin works fine ??

Hi @mateuszgbiorczyk ,

Thank you for your fast answer!

Indeed I don’t see any difference on your images either. But I see a quality difference on my site, in fact, even on mobile. I don’t know the cause yet.

I took some screenshots here
– The image named “1-Eventail-product page-1” is a image of a product as I see it on my site, you can see it’s a little blurry
– The image named “2-Eventail-product page-2” is the same image as #1 but I pressed on the magnifying glass in the right upper corner. You can see the quality is better.
– The image named “3-Eventail-product page-1-zoomed” is the same image as #1 but I zoomed in with my two fingers (or ctrl+mouse on PC). It’s very blurry.
– The image named “4-Eventail-product page-2-zoomed” is the same image as #2 but I zoomed in with my two fingers (or ctrl+mouse on PC). The quality is good.

I am using two plugin to compress images : TinyPNG and Converter for Media. These images are not compressed with TinyPNG yet.
Could I try to disable Converter for Media only to check if the quality changes?

Hi @britner

Ok I understand!

Thank you for your answer and have a nice day

Hi @habibjh

Sorry but the problem appeared again after the last update.

You can see the problem on the shop page.

The page is ok when I disable the Post Grid plugin.

Do you know how I could fix this issue?

Hi @habibjh ,

I don’t know how but I the problem solved by itself!

It might be because, with Asset CleanUp, I unloaded the following files everywhere except on my main page:
…/the-post-grid/assets/js/rttpg.js
…/the-post-grid/assets/css/tpg-block.min.css

I mark this topic as solved.

Hi @habibjh,

Thank you for your fast support.

I am using the Post Grid block on Elementor.

I tried to purge the cache, CSS generated with Autoptimize and Asset CleanUp but unfortunately it didn’t help. I don’t know where to look at. I have to investigate deeper..

• This reply was modified 1 year, 9 months ago by kureman.

Hello @razyrx,

Ok, thank you for your answer.

Regards

Hi @pulak00,

Thank you for your answer!

You have put the point on the problem. I had added a rule with Asset CleanUp and Font-awesome was not loaded. I thought that loading Font-awesome was redundant because other plugins were doing it too. So I cancelled this rule and the problem is now solved ??

Have a nice day too!

Best regards,

Hi @bsfherman,

Thanks for your answer!
I read the doc and tried to add the following CSS code

html,
body{
  width:100% ;
  overflow-x:hidden ;
}

As a result, the overflowing text is “cut off” and cannot be read…
https://drive.google.com/file/d/1RiQYgh61byGePz_gt3PU86LQOgVleCkh/view?usp=share_link

Is there any other solution to force the content of the WPAstra footer column to stay within the mobile width range?

Hi @thebengalboy,

Thank you for your fast support!

Thanks again @nlemsieh!
I was looking at the wrong place..