Plugin hash change but the plugin version didnt change??

Posted in: Newspaper
Post count: 17

I use a CI process based on the version set in the main php file. Why is it the same version 4.4 and 4.4 (i understand that the built on date is different) but the hash is different? Couldn’t you have updated it to be 4.4.1 on the later of the two?

<?php
/*
Plugin Name: tagDiv Social Counter
Plugin URI: http://tagdiv.com
Description: Social counter for WordPress. Widget and visual composer block.
Author: tagDiv
Version: 4.4 | built on 09.06.2018 22:20
Author URI: http://tagdiv.com
*/
//hash
define(‘TD_SOCIAL_COUNTER’, ‘0aaca5a8d55fd5281eddcf22b7bf96ca’);

<?php
/*
Plugin Name: tagDiv Social Counter
Plugin URI: http://tagdiv.com
Description: Social counter for WordPress. Widget and visual composer block.
Author: tagDiv
Version: 4.4 | built on 12.10.2018 9:30
Author URI: http://tagdiv.com
*/
//hash
define(‘TD_SOCIAL_COUNTER’, ‘d608b7ce86371b999748dbc94bcf2599’);

Post count: 23312

Hello mgargano,

Please notice that the message is added for each plugin with the date when the new theme packet is released, even if no change has been made.

Thanks for your understanding!

Post count: 17

The message is not what I am taking exception with. It’s two plugins with the exact same version 4.4 – AND strict checking via a hash – that violates the principle of versioned software.

Post count: 17

What I mean are. two different sets of code (ie 2 versions) of the SAME plugin are tagged with the same version number

Post count: 17

Any update here?

Post count: 20688

Hi,

Sorry for the inconvenience. There were some modifications made in the social counter plugin in the previous update. However the version remained the same due to an oversight, sorry about this. We will try to be more careful in the future.

Thank you!

Post count: 17

Thanks

Viewing 7 posts - 1 through 7 (of 7 total)
The forum ‘Newspaper’ is closed to new topics and replies.