Please test the new version

This branch gives full credit to the original author for the good work done originally, however since the original author does not allow this version to be published on www.remarpro.com, it will not be supported on www.remarpro.com, so please use github directly.

If the Github version is a legitimate fork then why doesn’t the author submit it as a fork with a new name?

it was released on www.remarpro.com as woopoly, but was taken down after a few days.
Apparently on www.remarpro.com:
– in order to release as a separate plugin, it must contain new/changed functionality, if it is only bugfixes that is considered a copy of the plugin which is not allowed
– at the same time the author is entitled to discontinue support for their product and to not release bugfixes.
Comments from someone with more experience on www.remarpro.com rules would be welcome!

Comments really do not matter one bit in this case. ??

The plugins team makes the determination. It has nothing to do with the original author, only that team can approve plugins here. If it was not approved

This really is not the place to promote another version of this plugin, this is for the review of this plugin here. I may redact the link but I’ll give that some thought first.

Hi, on the comments point, what I mean is that there should be some way that the community can organise itself to release fixed versions of plugins which have been abandoned by their authors and I was hoping someone might be able to point to the rulebook on that.

In this case I understand that the fixed version was published ok on www.remarpro.com but that a takedown request came from the author, however I wasn’t directly in the loop on that so I can’t verify that.

The review itself reflects that the plugin here does not work with current software versions and that the author does not intend to fix it.
Since the author has not commented for >1 year, people in the community have been replying on the support forum for this plugin about how to get a working version (and also some previous reviews). However there should be a pinned post or clearly visible review, at the moment it’s not at all clear that most of the issues raised in the support forum are actually fixed – although clearly they can’t be considered resolved in the published version. Also if you look at the github, 7 different teams have done branches with fixes of which decarvalhoaa has done a public spirited effort to bring this together.

Anyway, great that these forums are moderated, and no intention of trolling on this, we do just want people to be able to find out how to fix it. Of course it would be great too if the author became inspired to release the update.

Hello @jonathan

let me clarify the things a little bit in here , as this post is not totally correct .

I have contacted decarvalhoaa two weeeks ago:

Hello Antonio

This is Hyyan Abo Fakher the author of woopoly plugin.

I am contacting you so we can work together to improve the plugin.

As you know I was not able to maintain the project for a while because of my tough situation here in Germany as a Syrian refugee – Yes I am a refugee –

I took a look in What you have achieved so far and I like it. And I would like to Start merging your Patches in the plugin core and push a new update to the wordpress repo.

If you are interested, please contact me back so we could plan a workflow together.

Because I am working now, I would be able to maintain the plugin in the weekends only.
…..

Since I was unsure you would continue working on your plugin, on request from some folks I have started preparing to publish my fork on www.remarpro.com. You may have seen that there is quite a lot of commits to prepare this. It will not be straight forward to pull back to your plugin only the bug fixing related commits. Anyway, we can work on that.

Thanks for contacting me back , As I can see you have already published your fork in wordpress repo, I am not really a fan of this idea, as your fork contains only bug fixes and does not contain major features, and that will be confusing for the plugin users as they won’t be sure what plugin to use , Anyway you are free to do that of course, and I will understand if you do not want to share your work back as PR to my Repo

there is no issue in making a PR to your repo. I was only mentioned that there is a bunch of code changes that for sure you will not want in your plugin. Changes related to prepare the plugin for www.remarpro.com. How do you want to deal with that? …..

As you can I am already working on finding a way to integrate decarvalhoaa work in this plugin, but the problem as it seems it that decarvalhoaa commits are not really clean to be merged directly as PR into the plugin repo.and I want to keep a clean code in the plugin repo. but this is something to do in the near future for sure .

For now I am working on releasing a new version which will fix some issues related to the newest versions of woocommerece and polylang.I hope I can release my work soon enough.

Oh great, thanks Hyyan,

I understand decarvalhoaa is now on holiday and I haven’t got the full situation, good to see you are back on the case – and safe and employed – and I note you have pulled in the requests from the other branches except decarvalhoaa.

decarvalhoaa also said he had pulled in all the other fixes, although there are also a number of bugs/issues outstanding on the decarvalhoaa branch.

If the same issues exist on the Hyyan branch should I now re-raise them there or what is your preferred approach?

I am glad that you do understand the current situation now , as you have said I have accepted all PRs that could be merged into the plugin code and added Some Fixes to keep the plugin up with latest version of its deps

For decarvalhoaa fixes, I can merge some of them manually,as they can not be sent as PR, I will contact decarvalhoaa and ask him if that is OK , or we can find another way.

I would recommend to raise all issues into the orginal plugin repo, but I will keep an eye on the currenrt issues in decarvalhoaathe branch too.