Hi,
Yes just a Resolved child board would be fine.
It would make this forum more organised and stop people asking if their bug fixes have been incorporated in to the core (mainly me!).
Visitors can then see which bugs have been addressed and those that are still outstanding at a glance and don't arrive at the site and see lots of "Bug Reports" (which is the first thing I looked at and thought hmm lots of bugs then).
Phil.
Yes just a Resolved child board would be fine.
It would make this forum more organised and stop people asking if their bug fixes have been incorporated in to the core (mainly me!).
Visitors can then see which bugs have been addressed and those that are still outstanding at a glance and don't arrive at the site and see lots of "Bug Reports" (which is the first thing I looked at and thought hmm lots of bugs then).
Phil.
Hi Daniel,
We are a well established website hosting provider and also provide website design services and am looking to replace the current shopping cart that my staff offer to customers with a new fresh uncluttered one as the current offering has become a little convoluted and bloated with unnecessary code / functionality.
I still do a lot of coding myself and have investigated the design of this product and am satisfied that it is on a sound footing with lots of flexibility built in.
This has the potential to be an excellent offering for me (and my support staff) and my customers alike (some of which are pushing for a new shopping cart solution) as it is clean and easy to modify.
This is only a suggestion but in my experience a good one. It would also permit people to see that bugs are addressed quickly (which they are) and that the development of this product is still very active and well supported (which it is).
I have visited the bug tracker on Google and there are 47 issues listed but it doesn't appear to have been updated. I can't find the bugs or bug fixes that I have raised or that others have raised recently so we are relying on you responding to forum posts informing people that the issues are fixed and are now included in the core.
This takes up your time unnecessarily and has the potential to flood the forum with "has it been fixed yet" type questions (speaking from experience). When an issue has been resolved you would simply move it to the "Resolved" area. This would reduce the amount of communication required and keep the forum clean and tidy.
If you think that this is not the correct approach and don't see any benefits thats fine with me but could you delete the old fixed issues or simply reply to the bug reports with a "Done! now in core" so that people can tidy up things like "check if fix in core" and "must re-apply code" documents when a new release is made.
Thanks,
Phil.
We are a well established website hosting provider and also provide website design services and am looking to replace the current shopping cart that my staff offer to customers with a new fresh uncluttered one as the current offering has become a little convoluted and bloated with unnecessary code / functionality.
I still do a lot of coding myself and have investigated the design of this product and am satisfied that it is on a sound footing with lots of flexibility built in.
This has the potential to be an excellent offering for me (and my support staff) and my customers alike (some of which are pushing for a new shopping cart solution) as it is clean and easy to modify.
This is only a suggestion but in my experience a good one. It would also permit people to see that bugs are addressed quickly (which they are) and that the development of this product is still very active and well supported (which it is).
I have visited the bug tracker on Google and there are 47 issues listed but it doesn't appear to have been updated. I can't find the bugs or bug fixes that I have raised or that others have raised recently so we are relying on you responding to forum posts informing people that the issues are fixed and are now included in the core.
This takes up your time unnecessarily and has the potential to flood the forum with "has it been fixed yet" type questions (speaking from experience). When an issue has been resolved you would simply move it to the "Resolved" area. This would reduce the amount of communication required and keep the forum clean and tidy.
If you think that this is not the correct approach and don't see any benefits thats fine with me but could you delete the old fixed issues or simply reply to the bug reports with a "Done! now in core" so that people can tidy up things like "check if fix in core" and "must re-apply code" documents when a new release is made.
Thanks,
Phil.
There are not 47 open bugs.
http://code.google.com/p/opencart/issues/list
Just 6 and post of them are not really bugs.
You state you have a lot of resouces avalible. It would be great if you could put create some documentation or add a payment gateway to the project.
http://code.google.com/p/opencart/issues/list
Just 6 and post of them are not really bugs.
You state you have a lot of resouces avalible. It would be great if you could put create some documentation or add a payment gateway to the project.
Hi Daniel,
Thanks for you quick reply.
Sorry yes I should have stated that in my post 47 listed of which only 6 remain open.
This doesn't move from the fact that it isn't updated with bugs reported here on the forum though.
Phil.
Thanks for you quick reply.
Sorry yes I should have stated that in my post 47 listed of which only 6 remain open.
This doesn't move from the fact that it isn't updated with bugs reported here on the forum though.
Phil.
Who is online
Users browsing this forum: No registered users and 23 guests