monitor
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] “All Urls which returned no-cache tags”I will try the debug now. There is a no-cache header, but how do I remove that? I have a default wordpress install. Not sure how no-cache ends up there.
alt-svc: quic=”:443″; ma=2592000; v=”35,39,43,44″
cache-control: no-cache, must-revalidate, max-age=0
content-encoding: br
content-type: text/html; charset=UTF-8
date: Sun, 20 Jan 2019 12:58:41 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT
last-modified: jeu, 17 Jan 2019 14:05:13
link: <https://www.domain.com/wp-json/>; rel=”https://api.w.org/”
link: <https://www.domain.com/?p=1>; rel=shortlink
link: </min/ad2ca.css>; rel=preload; as=style,</min/fc9a4.js>; rel=preload; as=script
server: LiteSpeed
status: 200
vary: Accept-Encoding,User-Agent
x-litespeed-cache: hit,privateForum: Plugins
In reply to: [LiteSpeed Cache] JS minify Fatal Errors in logfileHi, yes i’ll look into this a bit further and do better testing and let you know.
Forum: Plugins
In reply to: [LiteSpeed Cache] JS minify Fatal Errors in logfileI see these in my apache log file if JS minify is turned on:
PHP Fatal error: Uncaught Error: Class ‘JSMin\Exception’ not found in xxxxx/wp-content/plugins/litespeed-cache/lib/js_min.class.php:211
LiteSpeed_Cache_Optimize->_build_hash_url( in xxxxx/wp-content/plugins/litespeed-cache/lib/js_min.class.php on line 211I saw another user also posted it 2 days ago:
https://www.ads-software.com/support/topic/fatal-php-error-in-wordpress-log/
Forum: Plugins
In reply to: [LiteSpeed Cache] JS minify Fatal Errors in logfileReport number: ZIWRQAOY
Forum: Plugins
In reply to: [LiteSpeed Cache] JS minify Fatal Errors in logfileI did a few tests. Google cannot reach our site if these options are enabled:
Unreachable + Temporarily unreachable:
JS Minify – ON
Inline JS Minify – ON
JS Combine – ONComplete + Working:
JS Minify – OFF
Inline JS Minify – ON
JS Combine – ONSo the issue seems to be only with JS Minify.
Forum: Plugins
In reply to: [LiteSpeed Cache] JS minify Fatal Errors in logfileI have been struggling 2 days to find out why we have several thousand Google Webmaster Tools “500 not found” errors, and googlebot could not fetch anything from our site.
When I found these Litespeed Errors in the logfile, I disabled the plugin, and now all our urls can be instantly fetched.I assume that google cannot fetch your urls if there’s a JS issue.
In fact, google did not even index our site since we last updated the plugin, if I do a “site:xxxxx.com” test.I did not know google relies so much on JS to be working. We love your plugin, but we’ll be turning off any JS optimizations permanently to avoid it in the future.
I agree with the local browser cache, but this just means that every visitor would still load those images from the remote server for the very first time, so each visitor would be met with a slow loading site, instead of from the local LightSpeed server.
I wonder if this scenario is possible:
-Visitor A opens the homepage and loads the 50 remote images.
-Those 50 remote images are then locally cached
-Visitor B opens the homepage and loads the 50 images, but this time from the local cache. So it is af if the images were local stored images.So Visitor A would load https://external.com/image1.jpg and then Visitor B would see that same image but this time it is https://localcached.com/image1.jpg
Something like this.
I think I know why. It is quite common for Woocommerce to remove or hide the /shop/ path, same as /category/
The empty <lastmod></lastmod> at the beginning of the sitemap is because of that
<loc>https://www.xxxxxx.com/shop/</loc>
<lastmod></lastmod>We hide/remove this /shop/ path via a function in our theme.
Luckily you have an excluding option “Exclude some Posts, Pages or Custom Post Types”
I enter the Page’s post ID 790104 in there, and then Flush permalinks, but the /shop/ page is still in the sitemaps file.It is odd because the only tickbox I have is for:
Check to INCLUDE Post Types:Products
IncludeSo theoretically domain.com/shop/ should not be in the sitemaps.xml file
To test I also ticked “Disable date after each post, page, post type?” and cache refresh the /sitemaps/product.xml file but nothing has changed. /shop/ is still at top, without a date, and everything else has a date.Forum: Plugins
In reply to: [XML Sitemap Generator for Google] Using Google XML Sitemaps with WooCommercein the settings at Sitemap Content, make sure your ‘Custom Taxonomy’ are ticked. Those are actually the Woo products, and not the default ‘posts’.
Tick these 3Custom taxonomies:
Include taxonomy pages for Product categories
Include taxonomy pages for Product tags
Custom post types:
Include custom post type ProductsI am also just curious what your opinion is on the image i showed:
For example, this is one of the images it detected as not in use. (one of over 90 000 images)
I searched this image in the media library, and found it was still Attached to a real post. I then open that post, and see, yes, there’s the image. Same path, same image as the one Media Cleaner show as “Does not seem in use”
I hope you can see form my image, that I’m not making this up. So I wonder why your plugin will classify an image that’s still attached to a post, and appears in the post’s content as an image link, to be ““Does not seem in use”
Hello Jordy, sorry for my harsh words. I have edit my review to better reflect of how useful the plugin is, but just not for me.
I have thoroughly tested this plugin for several hours. I can guarantee you 100%, the images it detects are still in use, in actual posts, which are published and public.
Which means that if i delete the “Does not seem in use” image, my front end would have the image missing.
same for us
Thanks for the quick reply.
It is the latest version, but I did went ahead and rebuilt the index.We do quite a lot of searches during the day ( for item numbers ).
It works most of the time, but it would for no reason still throw out that error.When we just re-search that same item number it would work the second time.
Forum: Plugins
In reply to: [Next Level Cache] WARNING: A conflicting DB Drop-in is installed.Found the conflict. It was another plugin i used:
WordPress Database Ping
Forum: Plugins
In reply to: [Next Level Cache] WARNING: A conflicting DB Drop-in is installed.I thought to give this plugin another shot.
I simply can’t get pass this error, no matter how hard I tryThe DB Drop-in ‘wpdb2’ is installed at /home/xxxxx/public_html/xxxxx/wp-content/db.phpdb.php If you wish to use Next Level Cache you will need to replace this driver file with the one located at wp-content/plugins/next-level-cache/db.php.
why it’s looking for a “db.phpdb.php” file.
I confirmed everything, nothing is wrong with my paths or drop in location.