Help Rebuild OsCommerce
Moderator: General Moderators
Yes it does require register globals to be on, and it does weird stuff like this..
There is an entire folder full of function files. Seems a bit misguided to me.
What does tep mean anyway?
Code: Select all
function tep_db_free_result($db_query) {
return mysql_free_result($db_query);
}What does tep mean anyway?
I vote mediawiki
Man... osCommerce sucks majorly. The code is messy and just all around HORRIBLE. I haven't ever done much more that throw some header/footers on an oscommerce site that was already built. This is the first time I've really dug into the code. It's very badly written. Just looking at this makes me want to do this project that much more.
Man... osCommerce sucks majorly. The code is messy and just all around HORRIBLE. I haven't ever done much more that throw some header/footers on an oscommerce site that was already built. This is the first time I've really dug into the code. It's very badly written. Just looking at this makes me want to do this project that much more.
- RobertGonzalez
- Site Administrator
- Posts: 14293
- Joined: Tue Sep 09, 2003 6:04 pm
- Location: Fremont, CA, USA
Nope... I'm pretty sure it needs to be a gmail account. I sent you an invite (although I'm not sure one is needed anymore... is it?)Jenk wrote:I have a "google" account, but it's not gmail.. user account is jenk<[at]>beeb<[dot]>netThe Ninja Space Goat wrote:do you have a gmail account so we can add you to the googlecode admin list?
so I'm not sure it'll work (I can't register new projects for example)
Here is what I have come up with so far:
Docmonkeys: All of us will be doing this by way of a wiki (astions will host the wiki)
XHTML/CSS Designers: myself, oren, astions
Programmers: myself, astions, jenk, (onion? Everah? bg?)
If I have missed you, please just post here and let us know what part you would like to be involved in, and I will add you to the list
Alright... time to get a preliminary list of features etc. out there. Please... everybody involved... take a look at these lists and let me know which you have a problem with and which are for sure so we can at least get a feature list up.
Core Feature List:
Catalog (categories/products)
Easy install for core application
Ability to install or upgrade
Ability to import data from another install of same app
User accounts
Shopping cart
Email receipts
PHP5/OOP
Plugin/Module Support
Mysql Back-end (eventually we will add support for additional dbs/backend)
Payment Processing (I'll do some research on how we could support additional payment modules easily)
Valid XHTML/CSS
Administration panel (this will obviously need quite a bit more discussion)
Module List: (none of these are, by any means final, complete, or even thought out completely... just putting them here for future reference and so I don't forget them)
Import/export from excel spreadsheet
PDF Receipts
Quick-buy
User templates
Visual cart (I will explain this later... just an idea I have)
Design Details:
Test-Driven Design
Swift-mailer for our emailing needs
Build our own framework/codebase
Model/View/Controller (primarily)
Much as I'd like to I'm much too busy these days. I might get involved at a later date though. And obviously I'm more than willing to answer questions on here.The Ninja Space Goat wrote:Docmonkeys: All of us will be doing this by way of a wiki (astions will host the wiki)
XHTML/CSS Designers: myself, oren, astions
Programmers: myself, astions, jenk, (onion? Everah? bg?)
You're missing some very important things that should be in the core .. (some might fall under the 'install' featureset though):The Ninja Space Goat wrote: Core Feature List:
Catalog (categories/products)
Easy install for core application
Ability to install or upgrade
Ability to import data from another install of same app
User accounts
Shopping cart
Email receipts
PHP5/OOP
Plugin/Module Support
Mysql Back-end (eventually we will add support for additional dbs/backend)
Payment Processing (I'll do some research on how we could support additional payment modules easily)
Valid XHTML/CSS
Administration panel (this will obviously need quite a bit more discussion)
Product import - There needs to be a way to import product data from CSV, XML, Excel etc.
Application Migration - A script to migrate data from OSCommerce, ZenCart etc will allow people to switch to your application.
Reports - Running a shop means keeping track of exactly what's happening in it. You will need to generate reports.
Auditing - On the main ecommerce app I've written I keep a complete audit of exactly what every user does (eg: Viewed Product 1 -> Viewed Category 1 Listing -> Viewed Product 2 -> Added Product 2 to basket -> Changed Product 2 quanity to 2) .. I can 'replay' a user's complete interaction with the shop. It's very useful if someone complains of a bug. It's not something you could add later .. if you're putting that sort of thing in you need to plan it from the start.
-
jamiel
- Forum Contributor
- Posts: 276
- Joined: Wed Feb 22, 2006 5:17 am
- Location: London, United Kingdom
One of the major parts of this project if it is going to work is going to be a solid database design.
We have built a couple of shop's in house and have found that the method of linking a transaction to an order to an item to a product works really well and provides some flexibility. Also if they are purchasing "Accounts" you don't want the "Purchaser" to be the same as the "User" to allow for multiple accounts to be bought etc.
If I can add my two cents to the features list, most businesses find the ability to add affiliates invaluable.
We have built a couple of shop's in house and have found that the method of linking a transaction to an order to an item to a product works really well and provides some flexibility. Also if they are purchasing "Accounts" you don't want the "Purchaser" to be the same as the "User" to allow for multiple accounts to be bought etc.
If I can add my two cents to the features list, most businesses find the ability to add affiliates invaluable.