Where is the changelog?

Hi @josklever,

Sorry about that, it appears the file hasn’t be included in the latest versions. I will fix that in the next minor update.

For now, the changelog can be seen on Github – https://github.com/DannyCooper/olympus-google-fonts/blob/master/changelog.txt

Let me know if I can help with anything else.

Thanks!

Hi @dannycooper,

Please don’t mark a ticket as resolved, when it’s not yet resolved.

You should follow the guidelines on https://developer.www.ads-software.com/plugins/wordpress-org/how-your-readme-txt-works/ to make sure it’s also visible at https://www.ads-software.com/plugins/olympus-google-fonts/#developers

Thanks!

Hi @josklever,

I’ve updated the plugin to include the changelog.txt in the package and also link to it.

https://plugins.trac.www.ads-software.com/browser/olympus-google-fonts/trunk/changelog.txt

Moving the changelog from readme.txt to changelog.txt has been permitted by the Plugin Review Team. It’s also how Yoast and WooCommerce handle their changelogs.

Let me know if I can help with anything else.

Thanks!

Both Yoast SEO and WooCommerce still show the latest version(s) on the Development tab. Only the older changelogs have been moved. So you should still put the current (or latest few) release(s) in the readme. Because that’s the place people look for the latest changes.
For the (longer) archive you should put a link to the actual location and not just “see changelog.txt”, because everybody has to start a search for that file.

Thanks for the feedback @josklever.

As the changelog is now easily accessible via a link in the update modal, and changelog.txt is part of the download package. I am going to mark this as resolved.

If there is anything else I can help with let me know.

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

I think it’s still a shame, that everyone has to follow an extra link, while the information can be placed easily in the readme file as well, so it will appear on the correct page (like Yoast SEO, WooCommerce and most other plugins).

The downside of adding the additional text to the readme.txt is that it places a burden on our volunteer translators to translate non-permanent strings – https://translate.www.ads-software.com/projects/wp-plugins/olympus-google-fonts/

I’m not sure how other plugin authors do that. I’m only saying that users and people like me who are managing hundreds of websites for updates, expect the information on the correct location. Most changelogs I see are only in English and not translated, so that shouldn’t be a real issue. You might ask the plugin team for advice on this matter.

It’s in the guidelines, (almost) everyone else does it, so there must be an acceptable solution for you as well.