I can see the SVN repository shows the latest version. I see Stable tag is set to the latest version. And the root file for the plugin is also set to the latest version. I’ve also waited several months for it to reflect in WP. Yet the directory still shows the wrong version.

The latest version is 2.6.1 but the WP directory says it’s 2.5.0

I’ve tried releasing new versions recently but nothing seems to work.

Theres a tag for 5.5 in SVN here, but docblock shows
Version: 5.4

WPPackagist show 5.5 as the latest, which pulls in the codebase that has 5.4 in the dockblock, i.e., it will not pull in 5.4.1 and 5.4 does not exists as a tag.

When can we expect an update correcting the tagging issue?

https://semver.org/#semantic-versioning-200

The immediate version number previously is 1.2.9.4 and the latest update jumped up to 2.2.9.4

This plugin is great, but for security reasons I want to remove version number line printed like below in the source code:

<!– Schema & Structured Data For WP v1.9.99 – –>

Can someone help me with this.

1.0.4 is the version number shown here on the WP repo and on the update in WP admin. However, in the changelog for “1.0.4” shows 1.0.3 17 November 2020

Cheers!
Lyle

I am new to plugin development. I was giving it a first shot, my plugin got approved, I uploaded the stuff to SVN, and all seems to work fine.

Except: the plugin page does not recognize the new version number of the plugin.
I used the boilerplate, and adapted version in my plugins starter php.

Do I need to define the new version anywhere else to make it working?

Again, sorry if this might be a stupid question. A pointer to the right part of the documentation would be appreciatet as well.

BR,
Peter

I have a question regarding the creation of a child theme from an unmodified parent. In the Codex, there is a ‘How-To’ (https://codex.www.ads-software.com/Child_Themes) which I am following. In the how-to, the following statement is made regarding the creation of the functions.php file for the child theme:

If your child theme style.css contains actual CSS code (as it normally does), you will need to enqueue it as well. Setting ‘parent-style’ as a dependency will ensure that the child theme stylesheet loads after it. Including the child theme version number ensures that you can bust cache also for the child theme.

And the following example is shown:

<?php
function my_theme_enqueue_styles() {

$parent_style = ‘parent-style’; // This is ‘twentyfifteen-style’ for the Twenty Fifteen theme.

wp_enqueue_style( $parent_style, get_template_directory_uri() . ‘/style.css’ );
wp_enqueue_style( ‘child-style’,
get_stylesheet_directory_uri() . ‘/style.css’,
array( $parent_style ),
wp_get_theme()->get(‘Version’)
);
}
add_action( ‘wp_enqueue_scripts’, ‘my_theme_enqueue_styles’ );
?>

My question is:

Where exactly in the example shown does the ‘child theme version number’ go and won’t the child theme version number be identical to the parent’s version number?

Thanks in advance for your support!

Frank