OpenCart 1.5.1.3 Released

JNeuhoff wrote:

Qphoria wrote: Since this was done in a point release (unfortunately )

This should have really been labelled 1.5.2 or even 1.6 because there are new features with the tax rates, including changes in the underlying database. Will do some thorough testing for all my Opencart extensions (there are tons of VQmod XML files which we plan to publish, too ) and bugfixes.

Anyway, a big thanks to Daniel and Q for all the hard work that went into this software release.

I have to agree this is getting pretty ridiculous. 1.5.1.3 should have been a bug fix change only with no other changes, and all the rest of this crap should have waited for 1.5.2 with the order editor.

So now as a mod maker you have to make mods and say this version works 1.5.0-1.5.0.5 then this version works 1.5.1-1.5.1.2 and this version works with 1.5.1.3. And I'm sure that everything will break again for 1.5.2 that is unless Daniel decides to throw some more breakage into a 1.5.1.4 version first.

JNeuhoff wrote:

Qphoria wrote: Since this was done in a point release (unfortunately )

This should have really been labelled 1.5.2 or even 1.6 because there are new features with the tax rates, including changes in the underlying database.

I really do not understand why we still keep using version-numbers as it is completely useless as there is no logic in the versions and and what "kind" of release it is (full, just a bug-fix or new functions).

@Daniel, why is it so hard for you to understand and agree with all of us that version-numbering should have (some) logic?

Every-time / release we have this pointless and useless discussion about version-numbering.

Needless to say that there is a lot of time, effort and money lost because of this

Qphoria wrote:...yet another reason this should not have been a point release.

I did my best...I even was able to post before the new version was released, but my powers of persuasion weren't enough this round.

Maybe I'll try and use a bigger font next time...

JNeuhoff wrote:

Qphoria wrote: Since this was done in a point release (unfortunately )

This should have really been labelled 1.5.2 or even 1.6 because there are new features with the tax rates, including changes in the underlying database.

LOL! are you reading my skypes to daniel?! Those were my exact words!

i2Paq wrote: I really do not understand why we still keep using version-numbers as it is completely useless as there is no logic in the versions and and what "kind" of release it is (full, just a bug-fix or new functions).

@Daniel, why is it so hard for you to understand and agree with all of us that version-numbering should have (some) logic?

Every-time / release we have this pointless and useless discussion about version-numbering.

Needless to say that there is a lot of time, effort and money lost because of this

Perhaps we should revisit and maybe rethink the versioning to be clearer and something that we can all agree on. It is very tedious to develop addons for opencart when the API keeps breaking.

Qphoria wrote: Perhaps we should revisit and maybe rethink the versioning to be clearer and something that we can all agree on. It is very tedious to develop addons for opencart when the API keeps breaking.

well seems like everyone has thought about it and agrees but Daniel.

Xsecrets wrote:

Qphoria wrote: Perhaps we should revisit and maybe rethink the versioning to be clearer and something that we can all agree on. It is very tedious to develop addons for opencart when the API keeps breaking.

well seems like everyone has thought about it and agrees but Daniel.

Which is pretty much the only person who needs to agree... so perhaps we need to step back and see what goes through his mind.

Qphoria wrote:

Xsecrets wrote:

Qphoria wrote: Perhaps we should revisit and maybe rethink the versioning to be clearer and something that we can all agree on. It is very tedious to develop addons for opencart when the API keeps breaking.

well seems like everyone has thought about it and agrees but Daniel.

Which is pretty much the only person who needs to agree... so perhaps we need to step back and see what goes through his mind.

That's pretty much what we've been doing for the last few years, and I don't think anyone's figured out what's going trough his mind. Sometimes I'm not even sure he has.

you're preachin' to the choir brotha..

This is the most boring thread about OpenCart.
Discussed since 17 months (or longer?) - nearly with every 'Mickey Mouse' release Mr. Chefdeveloper does what he wants.

What will be the next release: 1.5.1.3.1.2.3.4
Does no matter, we can be sure that important functions will be changed.

On the other side he is crying to vote for the best application - the category 'Most Confusing' is still not available, but if I would be the first.

Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

ehandelsfabriken wrote:Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

because you can look at the svn. or use a program like beyond compare.

Daniel wrote:

ehandelsfabriken wrote:Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

because you can look at the svn. or use a program like beyond compare.

Can the svn give me a list of the files updated since the previous release? I'm sure I'm not the only one having the same problem. Since I've made som core modifications myself, I want an easy way to see exactly what files are safe to write over without loosing my own changes. However, I'm not sure a list of updated files is the best way to go since I've never gone the svn way before.

ehandelsfabriken wrote:

Daniel wrote:

ehandelsfabriken wrote:Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

because you can look at the svn. or use a program like beyond compare.

Can the svn give me a list of the files updated since the previous release? I'm sure I'm not the only one having the same problem. Since I've made som core modifications myself, I want an easy way to see exactly what files are safe to write over without loosing my own changes. However, I'm not sure a list of updated files is the best way to go since I've never gone the svn way before.

well yes it can, or you could even take a second an look at the second post on this thread as see that a patch version with only the changed files is available too.

well yes it can, or you could even take a second an look at the second post on this thread as see that a patch version with only the changed files is available too.

Thanks Xsecrets!

ehandelsfabriken wrote:Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

Xsecrets wrote:

ehandelsfabriken wrote:

Daniel wrote:
because you can look at the svn. or use a program like beyond compare.

Can the svn give me a list of the files updated since the previous release? I'm sure I'm not the only one having the same problem. Since I've made som core modifications myself, I want an easy way to see exactly what files are safe to write over without loosing my own changes. However, I'm not sure a list of updated files is the best way to go since I've never gone the svn way before.

well yes it can, or you could even take a second an look at the second post on this thread as see that a patch version with only the changed files is available too.

This projects goes a heavy and strange way.
Assuming that every 'end user' can handle with SVN is bold.
Splitting (and opening) parallel threads for a common task (as a list of upgraded/updated files should be) is also contra productiv.

Making some complicated is the common way here.

A quite simple way to check what has changed is a tool like WinMerge
Easy to handle and tell you fast and exactly where and what was changed.
Just download the files you want (e.g. the latest OC package), unzip that into a new folder, start WinMerge and compare.

OSWorX wrote: This projects goes a heavy and strange way.
Assuming that every 'end user' can handle with SVN is bold.
Splitting (and opening) parallel threads for a common task (as a list of upgraded/updated files should be) is also contra productiv.

Making some complicated is the common way here.

A quite simple way to check what has changed is a tool like WinMerge
Easy to handle and tell you fast and exactly where and what was changed.
Just download the files you want (e.g. the latest OC package), unzip that into a new folder, start WinMerge and compare.

This is not assumed, that is why I always make the patch version.. for the normies.

ehandelsfabriken wrote:Why isn't there a list of changed files since the previous release in the changelog? Isn't that pretty much considered a standard or a minimum in the world of software development?

There is a patch version in the second post that has only the changed files.

When I upgraded, I lost my Import/Export Tool and my Blog tool from the Extras menu... not sure if I just missed something or if that is a bug to report. I tried re-installing those add-ons using their versions which are compatible with 1.5.1.3 and still no-go. I had to revert to a pre-upgrade backup in order to get them back.

Qphoria

Patch Only Version:
I've compiled a zip of only the changed files, for those that want to limit the upgrade to only the changed or new files.
Only use this zip if you have an existing 1.5.1.x version

We are currently using 1.5.1.1 with some extensions. What is the best way to implement the newest version?

Patch Only Version to limit the upgrade or use the updated upgrade script? What is the difference?

opencartrules wrote:Qphoria

Patch Only Version:
I've compiled a zip of only the changed files, for those that want to limit the upgrade to only the changed or new files.
Only use this zip if you have an existing 1.5.1.x version

We are currently using 1.5.1.1 with some extensions. What is the best way to implement the newest version?

Patch Only Version to limit the upgrade or use the updated upgrade script? What is the difference?

You can do patch only, but get the system/library/cache.php file from the full zip
patch only has only changes from 1.5.1.1