Jonas
Forum Replies Created
-
Thanks @jlapitan – adding the schema by editing the page and adding the schema in there does get it to display to correctly. When I set the schema up via WP Dashboard I did however also specify the ‘placement’ to be the correct page, so would expect it to work that way also. Anyhow, I am getting support to take a closer look but if they can’t fix the issue then your solution at least provides a viable workaround. Thanks for that.
@magazine3 OK, will do.
@magazine3 OK, have disabled it. Still the same problem.
@magazine3 Yeah sure. Here you go: https://imgur.com/a/q54QPKB
Forum: Plugins
In reply to: [AddToAny Share Buttons] AddToAny adding bloat when disabledHi @micropat – thanks for getting back to me. It would be nice to have an option to disable it that doesn’t require a developer.
To me it would make sense that unticking the “show sharing buttons” checkbox for a page would also stop AddToAny’s assets from being loaded on that page. With Google’s continued push to have site owners improve their page speeds, reducing unnecessary bloat is increasingly becoming more important.
I’ve found I can get around this now with the help of the premium version of the Asset CleanUp plugin, but not everyone will want to pay to have access to something like that.
Anyhow, just a recommendation.
Good job on AddToAny as a whole, it’s a very nice plugin and generally does strike a fairly good balance between functionality and performance.
@rom174 No, I wasn’t getting them in general. Funnily enough I now did receive one for your latest reply… Anyhow, all good.
@rom174 No, it’s because Google’s John Mueller has said that they do not care about popups that are triggered by exit-intent: https://www.youtube.com/watch?v=gS4_JH-QqSg&t=931s
P.S: I don’t know why I am not getting email notifications from WP for your replies…hence the long delay in replying.
@rom174 Interesting, I hadn’t seen Matt Cutts’ replies. I suppose if you wanted to take as little risk as possible then the exit intent popup would still be the safest option.
Forum: Plugins
In reply to: [W3 Total Cache] Cannot exclude page with infinite scroll ajax on it@optimizingmatters Excellent catch Frank, thank you very much for jumping in, that indeed looks like it’s the issue. Disabling AO’s HTML minification solves the problem.
I have wrapped the infinite scroll blog element in noptimize tags and subsequently re-enabled AO’s HTML minification and also removed the caching exclusions which I had set up for the page in W3TC.
This now works for the page in question.
It seems to me like W3TC should not be loading its minifier if one has disabled the minification option in W3TC? I’m not sure whether AO’s own minifier would’ve produced the same issue but even if then troubleshooting would involve one rather than two plugins.
In any event I’m very grateful that you jumped in here and guess perhaps lucky that I mentioned AO in my thread (guessing you got notified of the mention?).
Will leave you an overdue 5* review on AO.
Forum: Plugins
In reply to: [Adaptive Images for WordPress] Retina compressionHi @nevma
Yes, personally I’d be happy to pay for a Pro version with improved compression and HiDPI support.
I get what you’re saying about being wary about doubling the cache. But since one wouldn’t want to compress non-retina images as aggressively as retina ones so as to not end up with artefacting in the non-retina images I would think that would be necessary for this kind of solution.
Also only an issue for users for whom disk space is in short supply. I guess I’d feel it’s always good to have options – i.e. the ability to choose to have
– fast load times, minimal loss of disk space but
-
no retina support
or
– retina support, minimal loss of disk space but-
slower load times
or
– retina support, fast load times but a-
bigger loss in disk space
Like the ‘fast, cheap, high quality’ scenario…can only ever choose 2 🙂
Anyhow, thanks for the feedback, I’m going to keep having a look around to see how else this challenge is being approached, but will keep an eye on where to you take this plugin.
Keep up the great work.
Cheers,
Jonas@rom174 Well, cloaking is serving different content. You can have the same exact popup/interstitial just the trigger is different. Sure, a hardliner might consider it cloaking but I’ve never had any trouble doing this on sites and wouldn’t think Google would have an issue either – also this kind of stuff is pretty commonplace: https://moz.com/blog/white-hat-cloaking-it-exists-its-permitted-its-useful
@danieliser this is in reference to: https://webmasters.googleblog.com/2016/08/helping-users-easily-access-content-on.html
@optimi365 See: http://www.thesempost.com/exit-interstitials-not-impacted-googles-mobile-interstitial-change/ If you purchase Popup Maker’s exit intent extension then you can either always serve exit intent popups and you’ll be fine. Or get the the advanced targeting conditions extension as well and then you can serve whatever popups you want to non-Google traffic and to Google traffic you can serve exit intent popups.
@danieliser Haven’t used your plugin or extensions yet (busy researching it for our agency) so I’m not sure if you advanced targeting conditions extension also makes it possible to not serve popups to users on their first page view. Because that’s yet another way to avoid Google’s interstitial penalty. I.e. If a visitor is being directly referred from Google and on a mobile device then only show popup to the user on their second page view. Because Google just doesn’t want mobile users to be confronted with popups as they directly click through to a page from Google’s search results.
Hi,
likewise for me, same errors displayed in plain text across any and all pages displaying a button! Luckily I had an old version of the plugin lying around so could roll-back…