Joona Nuutinen

I think that the original poster meant that the link on the WordPress plugin update page (within WP admin), has a link to a changelog that stopped updating at WooCommerce version 5.0.0

https://raw.githubusercontent.com/woocommerce/woocommerce/master/changelog.txt

The link should be pointing here:
https://github.com/woocommerce/woocommerce/blob/trunk/changelog.txt

Here’s a screenshot of the plugin update view, in which the old link has been for years:

WooCommerce plugin changelog link in the WordPress plugin update dashboard is pointing to an outdated version of the changelog

Please update this link!

Sounds great! I will give it a try.

Thanks for the quick reply! Yes, you understood my suggestion correctly. For American customers, your current workflow is very good, but for most European countries, editing the price with VAT included would make it way more usable.

I’m having the same problem, but in my case the problem extends to the front end as well. I have updated the database.

• This reply was modified 5 years, 7 months ago by Joona Nuutinen.

What is the shortcode format for the handpicked product block? In my 10k+ product store, the query never finishes, so I would like to be able to pick the product manually using the shortcode and skip the GUI altogether?

It would be great if the plugin warned about the compatibility issue, but would allow the post type to be switched regardless.

Agreed 100%.

This feature doesn’t seem to be available yet. It’s the only missing feature of this great plugin.

This is exactly what I would need.

My only question is – when will there be a responsive default layout?

Good call. I’ve had to switch Twitter feed plugins several times in the recent years, because they’ve been abandoned. I hope your plugin will live longer.

You probably didn’t read the instructions. The plugin settings are within the Customizer, which is a pretty logical place to put them.

I’m also looking forward to this feature! Would make this plugin even more useful.

Hey guys, glad to see you’re interested in maintaining this plugin. I’m not a coder myself, but I would love to see this plugin being developed further. Please adopt it!

I had this problem too. I used Codestyling Localization to find out how the language file should be named, but then moved the file I originally created in Poedit to the plugin’s lang folder (not under WP’s languages folder).

The language files should be named like this (if they’re in Dutch):
wpvipergb-nl_NL.po
wpvipergb-nl_NL.mo

and placed here:
plugins/rizzi-guestbook/lang

Took a while to figure this out. The developer should document this, OR change the language files to be read in a more standardized way, like this: rizzi-guestbook-nl_NL, or better yet, use the languages folder.