March 6, 2011 at 11:28 pm #2877dcMember
can you please provide a changelog with updates?
i have heavily modified versions of these plugins and updating either overwrites all my work or takes ages to run diffs on every single file.
thanks.March 7, 2011 at 12:28 am #29879amin007Participant
When there is a major version release the change log is updated here:
We do not provide change log for everyday patches. Here are some reasons:
– We work on our plugins actively so sometimes we can have two small updates in one day.
– Not all changes are from functionality change either. For example, if we find that one of our customer’s server is having issue with a particular feature we try to change the code and add workarounds in the code so that this doesn’t happen with other customers with the same server configuration.
– Just going from version 4 to version 5 will most likely have more than 100 revisions committed to the repository by multiple developers so its not very straightforward.March 7, 2011 at 3:24 am #29880dcMember
i don’t see any of those as being reasons why you can’t publish a log of what was changed with every patch.
it’d be great knowing what files were touched in any given update.
overwriting your entire installation for an alteration of one line of code is generally a very bad way of distributing patches.April 5, 2011 at 11:35 am #29881lkincaMember
I agree. One of the advantages of eMember/eStore over other solutions like WLM is that you can actually modify the code to get it to do what you need for special cases. But by not being able to update the plugin it just takes a LOT of time or we can’t upgrade. If you can document the files that are touched, at least, it would be a huge help.April 5, 2011 at 9:21 pm #29882wzpModerator
You can use free programs such as DiffMerge and ExactFile to compare existing and updated plugin directories…
Or, if you’re old-school like me, you can use…
% diff -r –brief current-version-plugin-directory updated-version-plugin-directoryApril 6, 2011 at 1:57 am #29883amin007Participant
@wzp, Thanks for sharing that.
We keep the source code open so developer’s like yourself can customize the plugin to your hearts content but having a list of code changes for every little change is not the way to go (its just not efficient). We will release the change log when a major version is released. You want to use a software like the ones mentioned above by wzp to automatically find the difference between your changed version and a version that you downloaded from Tips and tricks site.
If you are serious developer then you can also use a version control software with your development environment (eg. eclipse) and it will automatically show you the differences between your modified version and our version. You can even merge codes from our branch or rebase as necessary.
- You must be logged in to reply to this topic.