Timofey Drozhzhin

I can confirm that it works flawlessly for me using the tls protocol. Look up the LSCache wordpress plugin on here. They do Redis Object Caching with support for tls via PHPRedis.

My setup is Alpine + Nginx + Php-fpm + PhpRedis 5. I connect to the Redis server on DigitalOcean via tls protocol.

If it makes it easier, I can put together a Docker image for you to test phpredis with working tls support.

Let me know.

Thanks!

It only worked after I prefixed the Host with Scheme (as I showed above). PHPResis 5+ supports TLS by prefixing the host with tls://hostname

• This reply was modified 5 years, 5 months ago by Timofey Drozhzhin.

@brechtvds – just in case you get similar issues on this topic – this also happens when memory_limit is too low. I had the same thing happen just now, error logs showed Out of memory errors. I switched it to memory_limit = 256M and all is fixed.

Thank you for explaining! ??

Maybe this is a good idea to create some kind of automatic cleaner in next release, what do you think?

You would probably know this best. I was just hoping there is a way to delete them, which you’ve pointed out!

@themastercut, this fixed it for me. Thank you!

I do have a question though – Once the Revision Draft is merged to the post, what’s the purpose of leaving the orphaned Revision Drafts and Revisions of Revision Drafts in the wp_posts table?

Aren’t we better off deleting them as a whole?

• This reply was modified 5 years, 8 months ago by Timofey Drozhzhin.

@themastercut of course. Just point me to the file when you’re done.

@themastercut, take your time! I crated a fix on my end. Just letting you know in case you want to fix it for other users.

Hi, BTW – disclaimer – I’m not the plugin author ??

I misunderstood the original question. So to answer the size of the images to upload to the recipe card:

It’s better to upload at least 1200px wide, because Google, Pinterest and other websites need access to the larger images. The recipe card does all of the optimizations/resizing for you, so you technically shouldn’t worry about it.

• This reply was modified 5 years, 9 months ago by Timofey Drozhzhin.

It comes down to the preference. OG:Image protocol (Facebook) recommends 1200×630. Google has been mostly using square and horizontal photos. Going off that, we personally try to stick to horizontal photos, 1200×900 or 1200×800 or similar.

As far as the main post photos, Pinterest and mobile users have been getting better results with vertical photos. That’s why you see most people use vertical there for Featured photos.

You cannot go wrong with any size and it really comes down to what you decide.

@alexlii, judging by your screenshot, if you’re using CloudFlare, you may need to add several Page Rules to exclude WP API from caching.

Thanks Brecht. I didn’t think about cloning the recipe. Will give it a try.

It does make more sense to automatically clone the child (wprm) with the parent, but then you’ll also need to figure out how to merge the child when merging the parent back into the origin post.

There’s also the permissions issue. A common flow of Revisionise and Revision Manager TMC is to limit the copyrighter’s editing to the revision (cloned parent post). So the editing permissions of the child (wprm) post, ideally will need to be that of the parent.

Honestly, I don’t know if it’s possible to do this with WPRM, or if it’ll break the existing logic, since WPRM is it’s own content type. I’m just passing a roadblock our developers came across and seeing if it’s in the roadmap. I guess ultimately this will be a decision up to you.

Thanks,
Tim

Thank you for confirming! Looking forward to the update ??

Hi, the command is definitely not purging Cloudflare. However, manually purging the Cloudflare from LightSpeed-Cache Settings does work. I wonder if the order of purging is incorrect….

I will debug the issue and update this ticket.

Thanks Brecht! Got it working!

I would love if you would consider adding the image size to the shortcode, i.e. [wprm-recipe-instructions header="Instructions" image_size="thumbnail" image_link_size="large"].

BTW – it looks like you have a minor typo line 201 class-wprm-sc-instructions.php $style .= 'max-width: ' . $image_data[1] . 'px;';. The $style hasn’t been previously defined.

That’s good news! Looking forward to this option! Thank you.