AgoraCart Free User Forums

I tried searching for this, but I think that the search function might be broken. It didn't find anything for several single-word search terms like:

weight
database
fields

Can someone point me to the current database layout for Agoracart? I found an article that was almost three years old that had a layout, but I don't know if it's accurate. I've got an existing customer database that includes a WEIGHT field, necessary to calculate shipping, but the forum article I read didn't have a weight field in the database structure.

Column 1 - PRODUCT ID # (current number displayed) (change to save as NEW record)
Column 2 - Category - One word only
Column 3 - Price - No $ sign needed
Column 4 - Product Name - 3 or 4 words
Column 5 - Image File - name.gif/.jpg/.png
<IMG SRC="%%URLofImages%%/0006.gif" BORDER=0>
Column 6 - Description - Enter the Text & HTML describing the product.
Column 7 - Shipping Price (Std) or Shipping Wt (lbs -SBW module)
Column 8 - 2nd Image/User1: text box
%%IMG%%image_name.jpg
Column 9 - User 2: text box
Column 10 - User3: text box
Column 11 - User4: text box
Column 12 - User5: text box
Column 13 - Option File - the list of files in the options directory
%%OPTION%%blank.html

all fields are manually filled in with the store manager add/edit screen. column 5 image structure is added by the manager program as is the token for the option in column 13. what you enter into the add or edit screen is inserted in the appropriate place. ie blank.html and 0006.gif. when editing by hand the image tag and option token should be maintained as decribed above.
for column 8 the %%IMG%% token is not auto inserted. you must manaually insert the token if you want to use the tiny image for viewcart and checkout. this is because this field can be used as a data field or as a tiny image field but not both! for example if using user1 as the tiny image display then you must dedicate this field for that purpose. same dedication principle for the other user fields, generally.

the native data.file format is plain text, pipe delimited. you can export and import through the store manager into/from csv and tab. there are no headers for the column fields nor for product rows.
dan

Thanks, Dan! That helps a lot.

Can I ask another question?

Is this information documented anywhere? I couldn't find it in the online manuals. If there is a more complete technical manual for purchase, I'd certainly be interested.

documentation for opensource programs varies widely. there is no documentation available for the dB. some hit and miss stuff here and there in the forums. if you want to write it up i'm sure the community would be most greatful
it sounds to me like you need instructions for manually manipulating the dB so you can transfer one dB structure to another.
this is always going to be time consuming and tedious. you can automate things like relocation of data rows. but the tedious part is like adding the image name into the image tag.
i personally prefer to do most of the editing in pipe, the native format. because of the description field sometimes having commas doing it in csv persents challanges. you can also use the pipe as a search feature for replacing stuff or as anchor for other manipulative functions.
make backups of successful transitions so you don't loose too much time and work effort.
the most basic columns you need for proper function are the first 6 columns...
Column 1 - PRODUCT ID # (current number displayed) (change to save as NEW record)
Column 2 - Category - One word only
Column 3 - Price - No $ sign needed
Column 4 - Product Name - 3 or 4 words
Column 5 - Image File - name.gif/.jpg/.png
<IMG SRC="%%URLofImages%%/0006.gif" BORDER=0>
Column 6 - - Description - Enter the Text & HTML describing the product.

this will get your product pages populated so you can customize the layout as necessary. it will also allow you to do test purchases and have most of the fields for the order log and emails. if using options and or userfield data to display on the productpage then you should propbably populate these fields as well befor messing with the ppinc.

if you have tons of products and categories then what i prefer to do is do basic sorting for the entire dB. then do category by category manipulation. sort the dB by category then cut out each category making a new dB for each category. this is advantageous to help reduce the chance of losing all data or coruppting all data as well as keeping relevant references localized. this way you don't have to sort through tons and tons of image names, descriptions and etc.
when done rejoin manually or import by updating not complete overwritting of the dB.
kinda tough not knowing what you're up against but it is going to taske time and work.
dan

I would have thought there was something, but there isn't.

Well, it is now documented with Dan's post...


_________________
God Bless!
Bonnie - AgoraCart Moderator

Get a Gold Membership