You are actually think, that “the functionality is great” (as you write), but
began the gratitude with one star…
You don’t write to support forum…
You don’t write to support email…
Well, thank you too…
Change log was added, so please don’t worry.
Thread Starter
pgodd
(@pgodd)
I gave the one star because you are doing the development wrong.
Today AGAIN you pushed a change without notice.
I am dropping your plugin and installing one whose developer follows some simple rules.
You should thank me for not posting this complaint to the main forum. Your plugin could be de-listed. You are doing a prohibited practice. This is not a support problem, this is a bad developer problem. You got the rating you deserve.
I can see you are skilled. But you think the rules don’t apply to you?
Plugin Developer guidelines:
14. Frequent commits can be seen as gaming the Recently Updated lists. Try to limit commits to prevent this. All commits should include a commit message describing the content of the commit, in reasonable detail. Frequent blank commit messages makes it hard for other developers and users to follow what is changing in the plugin. Blank commit messages may also be cause for rejection of the commit or removal of the plugin from the directory.
15. All code changes to a plugin that has a Stable Tag of “trunk” must result in the version number being upgraded. For the trunk and tags method, trunk can be continually updated without version number changes, while tags should generally not be updated ever past the initial tagging.
So who deserves to be sorry?
I think what the OP is referring to is that “fact” that when commits are being pushed to the repo that the stable tag is also being updated as well. While I do agree the original review is not based on the functionality, it is based on the plugin/support/etc. and how they rate their “overall” experience with your plugin.
All code changes to a plugin that has a Stable Tag of “trunk” must result in the version number being upgraded.
When committing to the plugin repo, ONLY update files in the “tag” directory when you are updating your plugin version number. Update your “trunk” at will.
@backup-dropbox If you have any questions that are not answered in the guidelines, please contact plugins.
Thread Starter
pgodd
(@pgodd)
Thank-you.
I don’t wish to be angry with the developer.
But security alerts up to 4 times a week for files changed without my permission is an inconvenience.
With no notice and no versioning, I cannot tell if this is legitimate or a result of hacking.
This means I have to review the code and look for malicious code each time a change is pushed. LIke I said. The plugin has excellent functionality and is very easy to use. The developer can be proud of his skills. But he should be conscious of the effect of this practice, and potential clients should be aware of this too.
I see he has updated the change log which is excellent. But this morning I was greeted by yet another warning that code had changed without my permission. I have raised my rating to 3 stars due to the developer’s quick response regarding the issue with changelog updates.
I understand he is proud of his work and a bad rating is upsetting. If the problem with pushing unannounced changes is addressed I would be happy to give this plugin a 5 star rating.
@pgodd’s 2.reply
I am dropping your plugin
you are welcome, if you dare to communicate in such manner.
You should thank me for not posting this complaint to the main forum.
Please, if you want, then of course, do this. Also please, mail to our support the name of your own backup plugin, that you are develop. I would appricate this.
You got the rating you deserve.
Except reviews from such competitors as you. That’s for sure.
But you think the rules don’t apply to you?
We follow all the rules of WordPress, as also remarks of our customers and users, as also from you about change log.
As a competitor, you don’t have to apologize
Thank you Justin.
We are updating the stable tag with lifting up of version ONLY, if all of our users must update the whole plugin.
In most cases this is a bug fixing, security issues and new features.
@pgodd
I don’t wish to be angry with the developer.
It’s late, I already am angry… 😉
But security alerts up to 4 times a week
You could find other way to report about your problem.
And now – “after fight don’t wave fists”.
I understand he is proud of his work and a bad rating is upsetting.
I’m glad, that you understand this. But then why you do this?
If the problem with pushing unannounced changes is addressed I would be happy to give this plugin a 5 star rating.
For you information and maybe also undestanding: now we have a few people, who threaten us with a bad rating, if we don’t add some features for the plugin. And I don’t know, maybe you one of them. What should I think after your review? Just think about that.
If there is a problem, then solving of this problem must be not here in review.
Review is for review, and support is for solving of problems.
Thread Starter
pgodd
(@pgodd)
You are one angry little dude aren’t you?
I am not a competitor.
Your problems with others are not my doing.
Perhaps you should consult someone about your paranoia?
Who cares what you think, with an attitude like yours?
You do not command the reviews. A review is an opinion of the product, and the user experience. I have been honest.
You, however are acting like a child.
Have fun with that.
Back to one star.
