[1.4.1-Dev] BUG REPORT

just tested 1.4.1-Dev found out the following error on checkout

Unknown: Object of class DOMElement could not be converted to string in /home/ezenguco/public_html/open2/catalog/model/shipping/ups.php on line 218
Fatal error: Call to a member function getElementsByTagName() on a non-object in /home/ezenguco/public_html/open2/catalog/model/shipping/ups.php on line 221

I have activated both USPS and UPS

i think curl is not working on your server!

Small bug:
Admin when loading / editing a shop, the path settings have been mixed up,
it reads HTTP_SERVER HTTPS_SERVER HTTP_IMAGE HTTPS_IMAGE where it should read
HTTP_SERVER HTTP_IMAGE HTTPS_SERVER HTTPS_IMAGE

Also if the config file does not write during installation, there is no error displayed until you try access the site

template currency and language dropdowns to not format correctly, the language sits below the currency instead of next to it.

I will continue testing, however so far looks like one hell of a job

Sorry another one (more of a feature request)

Modules - payment / shopping and boxes, should be changeable by store aswell!

cpanelhosting wrote:Small bug:
Admin when loading / editing a shop, the path settings have been mixed up,
it reads HTTP_SERVER HTTPS_SERVER HTTP_IMAGE HTTPS_IMAGE where it should read
HTTP_SERVER HTTP_IMAGE HTTPS_SERVER HTTPS_IMAGE

Also if the config file does not write during installation, there is no error displayed until you try access the site

template currency and language dropdowns to not format correctly, the language sits below the currency instead of next to it.

I will continue testing, however so far looks like one hell of a job

don't repeat bugs already fixed
http://forum.opencart.com/viewtopic.php?f=31&t=11238

muflon wrote: don't repeat bugs already fixed
http://forum.opencart.com/viewtopic.php?f=31&t=11238

It was already fixed long before you posted it

Daniel wrote:i think curl is not working on your server!

umm not sure if its curl who is playing the spoilsport here .. since i am running version 1.40 in the same server with USPS and it works fine there.

Qphoria wrote:

muflon wrote: don't repeat bugs already fixed
http://forum.opencart.com/viewtopic.php?f=31&t=11238

It was already fixed long before you posted it

And that's the problem of development this system nobody knows what is fixed and what is not.

muflon wrote:

Qphoria wrote:

muflon wrote: don't repeat bugs already fixed
http://forum.opencart.com/viewtopic.php?f=31&t=11238

It was already fixed long before you posted it

And that's the problem of development this system nobody knows what is fixed and what is not.

No, thats the problem with non-devs getting leaked "dev" releases and thinking they should use it

just deleted the 1.4.1. i think there has been enough testing.

How is this dev version 'leaked'? If you didn't want people to use it, don't publish it on google code and put a massive notice that it has been released on the front page.

I thought it was for open testing/feedback so the bugs can be removed before the final.

I don't think this guy (or anyone) should be chastised for providing feedback about the bugs he has found even if they have already been fixed. If there was a standard method for bugtracking in this project he probably wouldn't have posted them. Expecting people to read through all the threads for 1.4.1 bugs before posting a new bug is a little much.

Are all these updates going into SVN? or do we wait for another dev/testing release?

Cheers! SuperJuice

No organization, people trying to help get scolded and chastised.

1.4 should be made stable, then a firm line drawn saying this is how things will proceed from this point forward.

It's not developers who break scripts, it's users and buyers who discover most problems, what better hands to put into than theirs?

Then simply fix what doesn't work. Ignore the "it would be nice", "Oh, while you're in there", etc. Just fix what's broken then move forward.

SuperJuice wrote:How is this dev version 'leaked'? If you didn't want people to use it, don't publish it on google code and put a massive notice that it has been released on the front page.

This whas done because of mis-communication.

I thought it was for open testing/feedback so the bugs can be removed before the final.

There was a plan to invite a a small group that would be testers and they would report issues found and maybe in some cases a solution.
Why this did not happen I'm not sure but hopefully this will be done correctly before the next release.

I don't think this guy (or anyone) should be chastised for providing feedback about the bugs he has found even if they have already been fixed. If there was a standard method for bugtracking in this project he probably wouldn't have posted them. Expecting people to read through all the threads for 1.4.1 bugs before posting a new bug is a little much.

I agree, anyone should be thanked if he or she reports a bug eventough it was reported before.

There is a standard of Bugtracking but NO-ONE uses it as far as I can see and this is even mentioned in a topic of its own (Bug Tracking System) at the top of this forum but maybe there should be a link next to Screencast in the top bar of this site so it is clear to see.
The Bug-trakcer can be found here: http://code.google.com/p/opencart/issues/list

Are all these updates going into SVN? or do we wait for another dev/testing release?

I have no clue....

peteVA wrote:Cheers! SuperJuice

No organization, people trying to help get scolded and chastised.

We, the mods, are working and trying hard to get a sort of organisation in place.
This takes more time and effort then we hoped.....

1.4 should be made stable, then a firm line drawn saying this is how things will proceed from this point forward.

It's not developers who break scripts, it's users and buyers who discover most problems, what better hands to put into than theirs?

Then simply fix what doesn't work. Ignore the "it would be nice", "Oh, while you're in there", etc. Just fix what's broken then move forward.

I agree, and thats why we all are here to test-drive 1.4.1.

That this is done in the current way is not what we all hoped for but at the current point this is all we have.

Like I've said before, we hope that before the next version is released we will have the pre-testers group in place but it is all up to Daniel.

I think it's obvious that Daniel isn't changing his ways and is essentially coding as he wants and everyone else is along for the ride.

You can try and make it fit the mold of a structured project as much as you want, if Daniel isn't interested in developing that way all we (and you) will ever be doing is playing catch up.

We don't even know what's planned now? 1.4.1 was removed because Daniel decided it had been bug tested enough even when people were finding new bugs?

No mention of where to from here, if the next release is just a stable 1.4.1? how about some information and some forward planning.

SuperJuice wrote:I think it's obvious that Daniel isn't changing his ways and is essentially coding as he wants and everyone else is along for the ride.

You can try and make it fit the mold of a structured project as much as you want, if Daniel isn't interested in developing that way all we (and you) will ever be doing is playing catch up.

If thats the way it is then "we" shall have to live with it or go elswhere.
I know that Daniel agrees on a lot of things, he just needs to take some time to setup things and atm. he spends his time on 1.4.x.

We don't even know what's planned now? 1.4.1 was removed because Daniel decided it had been bug tested enough even when people were finding new bugs?

No mention of where to from here, if the next release is just a stable 1.4.1? how about some information and some forward planning.

I cannot tell you what I don't know, all I know is that Daniel is very bussy on 1.4.2(?) and we, some of the mods, are waiting on reply's on some of our questions to him.

look guys. i'm very limnited on time and resouses. I do plan on developing opencart full time but i' not able to do so at the moment.

if i use things like SVN or beta, alpha testing etc.. will slow things down alot. opencart is a lot more stable and less buggy than other carts out there.

If you are using SVN correctly it shouldn't slow you down much at all (infact it should speed a lot of the process up), especially for bug tracking.. it will take out all this stupidity of following threads on the forum.

Everytime the process is criticised it comes back to how much time you have and then the defenders pop up saying how busy you are and how you donate all your time and how you don't make a living off it.... great.

People aren't asking you to spend more time, they are asking you to change how you spend the time on the project so everyone can benefit and in turn you can benefit from contributions. If you have SVN people can submit code changes and you can approve them, instead of you having to merge them all by hand.

As long as you are convinced that source management will slow you down I don't see anything with the project really changing.

opencart is a lot more stable and less buggy than other carts out there.

How do you know that? you don't have a decent bug tracking system to quantify it. With developers and users complaining about the same things every release.. surely it means there is something wrong.

Take a look at Roundcube, using TRAC. I can follow the source revisions and know exactly what has changed, and I can see the current bugs, the bugs being treated with priority etc. How is that not saving time?

http://trac.roundcube.net/log/trunk?rev=3295 <- good example of changes to a specific revision.. a 'changelog' is something that has been asked for again and again and something developers still aren't getting here. That isn't to say they want you to spend your time on it, just use a tool that does it for you.

SuperJuice wrote:If you are using SVN correctly it shouldn't slow you down much at all (infact it should speed a lot of the process up), especially for bug tracking.. it will take out all this stupidity of following threads on the forum.

Everytime the process is criticised it comes back to how much time you have and then the defenders pop up saying how busy you are and how you donate all your time and how you don't make a living off it.... great.

People aren't asking you to spend more time, they are asking you to change how you spend the time on the project so everyone can benefit and in turn you can benefit from contributions. If you have SVN people can submit code changes and you can approve them, instead of you having to merge them all by hand.

As long as you are convinced that source management will slow you down I don't see anything with the project really changing.

opencart is a lot more stable and less buggy than other carts out there.

How do you know that? you don't have a decent bug tracking system to quantify it. With developers and users complaining about the same things every release.. surely it means there is something wrong.

Take a look at Roundcube, using TRAC. I can follow the source revisions and know exactly what has changed, and I can see the current bugs, the bugs being treated with priority etc. How is that not saving time?

http://trac.roundcube.net/log/trunk?rev=3295 <- good example of changes to a specific revision.. a 'changelog' is something that has been asked for again and again and something developers still aren't getting here. That isn't to say they want you to spend your time on it, just use a tool that does it for you.

I completly agree with you. I was saing it for few times start using git instead of svn and all problems will go. Git can't slow anybody down. If you use github you can see every change in code and you need to write two commands in cmd it is simple and it make developing easyier.

ok give me some time. let me get 1.4.1 out first.