just starting with contributions

[scotch33]

Hi guys,

 

I've installed a few OScommerce shops now and have mainly worked with the design aspect of the shops.

 

I am now keen to start learning more about sql and php and am looking for some robust and reliable contributions with good installation instructions to extend the store functionality, so I can practice on a new installation on one of my sites and start to learn how this all works.

 

Can anyone suggest some well developed contributions that would be a good place for me to start learning with. I am hoping that this will be (along with a book on PHP I gave myself for christmas) a good starting point to eventually be able to start helping on contribtions myself.

 

I am also interested in contributions anyone reccommends that can be added to the base OSC folder before installation if anyone has favourites. I hope to eventually have a base system for installing that is full of extra bits! Has anyone done this?

 

Thanks!

[Simmy]

Payment without account is a personal favorite of mine!

 

Look through the contris for ones that let you add quantity boxes to the prod listing and attributes dropdowns as these are pretty handy from a customer point of view.

 

3 images is quite good too.

[Jack_mcs]

John - There are a lot of different ways the instructions for contributions are written. Which is the best way is probably a matter of taste. I'm not sure if you are looking to learn how to install the contributions or how the changes made in them work. But for either one, start with something small. The new oscommerce paypal system is one the easiest to install. Likewise, my Form Controller contribution only has two instructions to install it (there are others like this but this is the only one I am familar with off the top of my head). Obviously, you should backup everything before installing any contribution.

 

There are a number of threads in the forums that deal with best contributions to install. Try searching Top Ten Contributions, or something similar to find the results.

 

Jack

[ozcsys]

One suggestion I would make is always find and read the support thread for a contribution before installing it. You can find out if it works, what problems there are with it, what instructions may be missing etc. There is not much worse than spending time installing a contribution and finding out it does not do what it is supposed to do.

The second is BACKUP BACKUP BACKUP!!! You should always backup every file you are planning on making changes to or replacing and also your database if any sql changes are needed. Usually when doing anything that involves changing more than a couple of files I do a database backup in the osC admin and then just backup the whole site.

If you are planning on making changes to a live store always test them first on a test site so if you hose something your are not in a panic because your store is down.

When you are planning on making multlple changes or installing multiple contributions always test the complete site between them so that if something goes wrong( and it will) that you know exactly which contribution or change is the problem.

You will see post where someone has installed 2 or 3 contributions and their site is broke and now they have no idea what the problem is ( and no backup and it is a live store) You feel bad for them but there is not much you can do, so do not let yourself be that person.

[♥bruyndoncx]

Here's my stock anwser :)

HTH

______________________

Contributions For Dummies

 

The most important bit is to make a backup of your php files and the database before starting, so you can always revert back. Also when you have a live shop, you should work on a copy of your shop, install & test it there and then copy over to the live shop.

 

Pre-requisites to install contributions:

 

access to mysql database usually via phpmyadmin

text/code editor

FTP access to your server

very usefull: file comparison software eg beyond compare. This you use if complete files are in the package and you have to see how they are different from your files.

 

Preparing for the installation: Read the announcement and support thread for the contribution. It might warn you of certain issues/limitations that could be blocking for you, so you don't waste time. Besure of the actual version you have, be aware that some hosted osC installations come with 'loaded' versions which means that a number of contributions are already installed which make it harder to install additional contributions (if you are touching the same files) Find the latest package that is labeled being complete and download it. Find any additional updates since and download them See in the forum if there are other manual edits/fixes posted.

 

If the updates are just some files to add or overwrite; I tend to combine all of them in a single directory and upload that, if updates come with detailed instructions, you should perform them cronologically, one after the other.

 

Create a before directory with the files you are going to update/replace with new files.

 

Installation: Almost every contribution will have a readme or installation.txt file. Follow the instructions carefully.

 

Any file with .sql extension you have to run in your database using phpmyadmin. If you are unsure of the database name and/or login to use, this information is recorded in catalog/includes/configure.php so you can always look it up there.

 

Before you upload complete php files to your server, you have to make sure that they do not overwrite any changes you made. Using ?Beyond Compare you can compare directories and files one by one and apply the changes to your set of files.

 

For step-by-step instructions, read them carefully, try to understand the code you are replacing and what it's supposed to do so you are confident you are replacing the right set of code. Especially if you have heavily modified files, better take some time to verify this and ensure you are putting the code where it belongs in your store. Pay attention to round and curly brackets and where you put the code exactly. Don't forget semi-colons at the end of the line, and pay attention not to add/leave empty space before the starting php tab or after the ending php tag in your file as this causes strange error messages.

 

Usually you can only test the results of the pages you edit when you are completely done. However there is a logical sequence. Generally you apply the sql changes first, then you do the admin changes and test this. If this is all ok, then you change the catalog side and do the complete test. This will also allow you to backout easier if you decide based on the admin changes that the contribution isn't really doing what you thought it would ...

 

Once you are finished/happy with the result, also visit the support thread and give the contributors a pad on the back, otherwise they might get depressed not knowing if anybody actually succesfully used their contribution :lol: Also if you like the contribution or would like to get enhancements and can spare some money paypal donations are generally appriciated as they allow the contributors to spend more time contributing.

[scotch33]

Thanks Guys, thats a really big help. I shall create a dummy store on my server and use it just to play with.

 

Thank you again. :thumbsup: