Hello!
Searching after "model" is not a very good tipp.
It would be very useful to have a real step by step guide for adding fields to:
- product
- customer
- address
- order
This is probably the work of 2 Hours for one of the people already using this system.
But it will save ANYONE new with this system 10 hours at least!
Please be a rockstar and make such a guide!
Regards,
tronics
You should first learn what "Framework" means as opposed to "Websites for Newbies"tronics wrote:Hello!
Searching after "model" is not a very good tipp.
It would be very useful to have a real step by step guide for adding fields to:
- product
- customer
- address
- order
This is probably the work of 2 Hours for one of the people already using this system.
But it will save ANYONE new with this system 10 hours at least!
Please be a rockstar and make such a guide!
Regards,
tronics
I have already added 10 fields and debugged the VAT extension: http://www.opencart.com/index.php?route ... ion_id=115
When I wrote 'step by step' I did not mean line-numbers.
The fields in the several files have different implications:
In the list or only in edit, filter the field, tie the field to the customer or to the address and so on.
When I wrote 'step by step' I did not mean line-numbers.
The fields in the several files have different implications:
In the list or only in edit, filter the field, tie the field to the customer or to the address and so on.
Example:
This explanation of the opencart fork chromiumcart goes into detail (actually it could/should be much deeper):
http://forum.chromiumcart.com/index.php ... 648.0.html
With a guide like this a new adaptor of the software can oversee the requirements for such an day to day operation as "adding fields".
Every framework is different and very often it is more a drag to learn then it saves time.
The decision for a programmer to work with a specific software is very much dependent on being able to make quotes about how long something takes.
So we are doing good giving out informations what has to be taken in consideration when e.g. adding fields.
This explanation of the opencart fork chromiumcart goes into detail (actually it could/should be much deeper):
http://forum.chromiumcart.com/index.php ... 648.0.html
With a guide like this a new adaptor of the software can oversee the requirements for such an day to day operation as "adding fields".
Every framework is different and very often it is more a drag to learn then it saves time.
The decision for a programmer to work with a specific software is very much dependent on being able to make quotes about how long something takes.
So we are doing good giving out informations what has to be taken in consideration when e.g. adding fields.
LOL.. notice that I am the creator of that thread as well.tronics wrote:Example:
This explanation of the opencart fork chromiumcart goes into detail (actually it could/should be much deeper):
http://forum.chromiumcart.com/index.php ... 648.0.html
With a guide like this a new adaptor of the software can oversee the requirements for such an day to day operation as "adding fields".
But this topic is a quick breakdown about the "Framework" and explaining "What it is" not about "Adding a field". So I will split this topic into its own thread for "Adding a field"
*hehe* so that was you again 
What do you think if we make a "add a field/filter checklist"?
Not a step by step, but a commented checklist where people can understand the underlying reason before duplicating code.
(At first I was confused about the 2 forks-- which one do you think has more future?)
What do you think if we make a "add a field/filter checklist"?
Not a step by step, but a commented checklist where people can understand the underlying reason before duplicating code.
(At first I was confused about the 2 forks-- which one do you think has more future?)
Who is online
Users browsing this forum: No registered users and 29 guests
