D

Thanks for your responsiveness, I’ve already improved my review considering that.

Only you should decide what is free and what is pro, but I do expect a clear statement and description. If there are more than one version of the plugin it should be clear what features are included in each of the versions.

For example, I quote the description of this plugin:

BuddyForms works great with other Plug-Ins. Enhance its capabilities with the following:

BuddyPress – Enable all publishing features of BuddyForms in BuddyPress
Ultimate Member – Submit and manage posts from your Ultimate Member profile
WooCommerce – Build your own marketplace with user-submitted products
WooCommerce Simple Auctions – Create and manage auctions via front end
Advanced Custom Fields – Integrate Advanced Custom Fields in your forms like native BuddyForms form elements
Posts 2 Posts – Efficient many-to-many connections between posts, pages, custom post types, users.
WC Vendors – BuddyPress WooCommerce Vendors integrates WC Vendors with BuddyPress and enables your vendors to use BuddyForms to create and manage their Products

also:

Full moderation control of the submitted content by predefining the status: pending, draft, published

Specifically, I wanted ACF, post2post and draft status. Since such integrations/features wasn’t included in the free version I find it misleading.

Since this was my main concern, if you’ll update the description with a feature comparison table between the versions, I’ll update my review to four stars.
(I’m not sure, if it’s technically impossible to insert a table into readme.txt, you can add an image with the table to the screenshots section)

As for advertisements, in my humble opinion, ads inside the admin panel should be totally prohibited. I am the web developer, the admin panel is used by my clients, so those ads will be visible to my clients. This information is irrelevant for them, and they are not your target audience for sure.

I do not expect those advertisement to totally disappear in the near future. So I will ask/suggest something else. If at all, ads in the admin panel should only be visible below all of the content/functionality provided by the plugin. Not in a sidebar, especially not above.

I am a developer myself (indeed, not my main occupation), so I do understand the need. I just find it frustrating to install a plug-in, try to figure out how it works, and only then find out that some of the features listed in the description only exist in the pro version.

Thanks anyway for supporting WP and releasing free plugins!
Good luck!

I’m also encountering this problem if someone solve this problem please share…

OK I’ve find the answer by myself.

TortoiseSVN – Creating and Applying Patches

A short summary of the mentioned page:

For open source projects (like WordPress) everyone has read access to the repository, and anyone can make a contribution to the project. So how are those contributions controlled? If just anyone could commit changes, the project would be permanently unstable and probably permanently broken. In this situation the change is managed by submitting a patch file to the development team, who do have write access. They can review the patch first, and then either submit it to the repository or reject it back to the author.

Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.

Creating a Patch File
Creating a patch is meaning to make some changes to your copies of the files that need a fix, and than export all the changes you’ve made to a *.patch file.

You can select the files you want included in the patch, just as you would with a full commit. This will produce a single file containing a summary of all the changes you have made to the selected files since the last update from the repository. So you can produce separate patches containing changes to different sets of files. Of course, if you create a patch file, make some more changes to the same files and then create another patch, the second patch file will include both sets of changes.

Applying a Patch File
Patch files are applied only to your working copy and not on the SVN.

This should be done from the same folder level as was used to create the patch. If you are not sure what this is, just look at the first line of the patch file. For example, if the first file being worked on was doc/source/english/chapter1.xml and the first line in the patch file is Index: english/chapter1.xml then you need to apply the patch to the doc/source/ folder.

Once you have selected the patch file and working copy location, TortoiseMerge runs to merge the changes from the patch file with your working copy. A small window lists the files which have been changed. Double click on each one in turn, review the changes and save the merged files.