adfisch
Forum Replies Created
-
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsHi @vmarko,
just wanted to friendly follow-up if there are any news on this topic? Thank you. 🙂
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsDone. 🙂
Forum: Plugins
In reply to: [Download Monitor] All downloads suddenly showing “No file paths defined.”thanks for your fast reply. Indeed, a re-activation fixed the issue. Thank you! 🙂
Forum: Plugins
In reply to: [Download Monitor] All downloads suddenly showing “No file paths defined.”Maybe some more context information:
- We are using Download Monitor v 5.0.31
- Theme: Avada
- Multilingual website using Polylang (downloads are not working for any language)
Thank you!
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsThank you for checking this with your team. I am looking forward to your reply. 🙂
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsHi @vmarko,
thank you for your reply. Everything is custom. However, I don’t mean to be rude but I think the 403 is the problem but simply the fact that URLs are not being replaced by W3TC. Here’s why I believe so:
Bunny CDN only has Pull Zones (no Push zones). It does not cache all the files right away but retrieves and caches them the first time a user asks for the files. Consequently, there is most likely not a function in W3TC that checks if files exist in the CDN as this does not mean they cannot be cached?
The current security settings require a referrer header to be set to dreiw.marketing, otherwise a 403 is displayed. The reason you see a 403 is because when you send the URL manually, you do not send that header.
To double check I did following tests:
- 1st I copied the HTML from the front page. I then manually replaced the above mentioned non-CDN URLs with CDN URLs. The result: All content (including lightbox and small lazy loading images) are loaded from the CDN without a problem. You can check for yourself: https://dreiw.marketing/index-test.html
- 2nd I disabled the security feature in Bunny CDN. Now the links do not show a 403 error anymore. However, links are still not replaced in my source code.
To sum things up: To me it seems the URL replacing feature of W3TC misses the URLs in style and data attributes. If not, I would appreciate further clarification. I hope this makes sense and, again, do not mean to be rude. 🙂
Thank you!
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsHi Marko,
I set up some security policies such as only aspecting requests with the proper referrer dreiw.marketing. However, to me the problem seems to be that the URLs are not replaced in the source code in the first place?
Forum: Plugins
In reply to: [W3 Total Cache] W3TC + Bunny CDN: Not all URLs are replaced with CDN URLsHi Marko,
thanks for getting back to me. You can check out my website https://dreiw.marketing:
- Lazy-loading backgrounds: All images and videos have a sibling div with the class “lazy-picture-background” or “lazy-video-background”. These <div>s have an background image set by the inline style attribute. The URL is not replaced with cdn.dreiw.marketing.
- Lightboxes: The lightbox opener with the classes “b-hero-link lightbox-link” for the hero video (which is labelled “Reel abspielen”) has a “data-lightbox-content” attribute. In this attribute, URLs are also not being replaced, resulting in the reel being loaded from the original server.
If you have any further questions, please let me know. I really appreciaty your help! 🙂
Regards,
Adrian
Hi @stevejburge,
I just updated from WP version 6.1.4 to 6.2.4 and the box re-appeared. I guess this means your new plugin version is not compatible with the old WP version?
Thank you!
Sorry, I just updated the post before:
So far we have completely reinstalled the plugin without success. Also, our system used to work with real cron jobs (so we had WP Cron deactivated). We switched back to WP Cron, also without success. Do you have any more recommendations on further steps?
Hi there,
we actually have the same issue (find screenshot attached) and where just about to post when I saw this thread. Your plugin used to work fine until recently, now other system settings have changed in our ecosystem. Could it be, that there came some kind of bug with the latest update?
Steps taken so far: Deactivation and complete re-installation of the plugin without success.
Thank you!
- This reply was modified 2 years, 5 months ago by adfisch.
thank you for your reply. I made a few adaptions and now everything works perfectly.
Thank you for your help! 🙂
Hi @wpmudev-support8 and @wpmudevsupport11,
thank you for your fast replies. I have one last question and would appreciate your help: Since there is no ETA on the ability to disable the default article markup, is there a way to programatically remove it?
I know that I could deactivate the Schema module. However, this also prevents me from using the Schema Builder or Breadcrumb Feature. Thus, a code snippet for only disabling the article schema would be very handy.
Thanks a lot.
Hi Adam,
thank your for your code snippet. It worked perfectly! 🙂
Adrian
Forum: Plugins
In reply to: [SmartCrawl SEO checker, analyzer & optimizer] Bug report:Hi Zafer,
thanks for your fast reply. Yes, I have installed SmartCrawl 3.6.5. You should be able to replicate the issue by:
- Making sure that you have a static page as your home page.
- Activate the Breadcrumb feature in SmartCrawl > Advanced Settings.
- Under “Configuration” set “Add homepage to the breadcrumbs trail” to true and provide a label (in my case “Startseite” which is German for “Homepage”).
- Now, evaluate the Breadcrumb Schema markup, e. g. with Google’s Rich Results Test Tool. Since we are on the front page, there should only be 1 breadcrumb. However, even the homepage gets itself added to the trail. So there are 2 breadcrumbs of the homepage instead of just one (see my screenshot above).
Possible and easy solution: When prepending the homepage to the trail in your code, add the following conditional statement:
if ( ! is_front_page() ) { ... }Thanks for your help. I am looking forward to your reply. 🙂