Vidyut

I am having this problem too. Old irrelevant posts are being sent out and subscribers are getting irritated. Deactivating did not help. Someone help!

Oh I figured it out. I deleted the API key and saved options and then inserted it again and saved options again. It is working now.

Scratch that. Didn’t work.

I had the same problem. Couldn’t troubleshoot it, but found that it resolves on its own given enough width (I am using the buttons in a widget). Adding a line break might be worth experimenting with.

Whoa! That is a serious SEO blooper. Thanks for heads up. Not using plugin, but will be sure to check what’s going where and disable anything as necessary!

If you are not using pagespeed (or not serving special features by user agent like lazy load images), you could keep just two variants – desktop and mobile – and shift other user agents into one or the other as you see fit (make everything not mobile into desktop and you should be fine). That will take out two sets of caches.

Hi,

I am so sorry for abandoning this post.

I have posted my current config here https://vidyut.net/varnish-config-wordpress-pagespeed-wp-touch/

It is working fine with wordpress, modpagespeed / ngx_pagespeed and wp-touch.

I am currently not using wp-touch for the most stuff, so I have taken ut the exact code for the switcher. This code will give you browser recognition and separate caches as per capabilities and serve appropriate content automatically. But it won’t allow for switching. I will need to install wp-touch and find the string for switching (seeing mobile site from desktop or vice versa). Basically, what I had done was once I have the string, I just add a pass for it.

It is possible to switch the type of device instead of passing through, but I never had the kind of traffic that would force me to cache those few queries.

Thank you. I had panicked and disabled the plugin. Problem is that I use it more for keeping an eye on subjects I cover rather than re-publishing the articles, so my posts are actually quite different, even unrelated to main subject of article, and the article getting injected was creating a horrendous content disaster.

I liked it, so when there was an update, I came back to check here. Trying it out again. Looks like it is working ok so far. Thank you for a great plugin and sorry for panicking and judging in a hurry. This plugin makes keeping an eye on subjects much easier.

You will have to edit the code of the plugin. It shouldn’t be too tough if you see the part where the url gets added. I am not able to understand why the url you get is wrong. Only thing I can think of is that it may have problems with multisite. I can look into this when I get time.

Not sure I have the coding expertise for that. Will check with creator of original plugin, or learn and wade into the code one of these days. If you find a solution before me, do share back, so I can add it in.

Just noticed this question.

Varnish easily caches a separate mobile version of the site by identifying the user agents, factoring in cookie (if switch to desktop) and adding a variation to the hash. No issues whatsoever. Works way faster than a pass through.

I can share my vcl once I get a bit free.

It does support custom fields. That is how it gets linked to the parent post and so on. But I am not able to understand what you are trying. You will have to code the feature that expires the offer. You could also check the Live Blogging plugin support (this plugin is merely one that is updated to work with latest wordpress) to see if such a thing has been done by someone else. https://www.ads-software.com/plugins/live-blogging/

Hi,

I hadn’t noticed the reply and disabled Cloudinary, but would like to give this another shot. Will update results of what happens.

Vidyut

This is good. I will add it to the plugin’s documentation, in case anyone else needs to do it.

Thank you.

It should be possible to add a “default” live blog that gets assigned if no specific live blog is selected. Will take coding, but should be simple enough. Alternative may be to get pressgram to send the metadata for associated liveblog.