Book Image

Building Online Stores with osCommerce: Professional Edition

By : David Mercer
Book Image

Building Online Stores with osCommerce: Professional Edition

By: David Mercer

Overview of this book

<p>The book can be read from front to back, but each chapter is self contained so the reader can skip chapters to read those that they are interested in. Each chapter will move from basic to advanced where applicable and also relate what the administrator (reader) is doing to how this affects what the client sees on the site.</p> <p>So, for example, the customization chapter will start off with a discussion on the concept of design and how to relate this to your business. Once the reader has a clear idea of what they need to do, we look at some really simple changes such as modifying the site's language, before moving to some advanced modifications which may involve some PHP programming. At the same time the discussion will demonstrate how the changes made affect the site.</p> <p>Throughout the book, much consideration is given to the "right" way to doing things. Readers will have the great advantage that they begin, from the very start, doing things properly. This will save them a lot of time and effort in the years to come as they build on and modify their site. Utilizing best practices and sound methodologies is a great asset for beginners and experienced users alike.</p> <p>At all times, the coverage given in this book pays homage to the fact that, ultimately, the reader has a business goal in mind. To this end, the material never gets bogged down in technical issues or long discourses, but rather focuses on what is practically important for the online business and then moves on. To complement this, there are plenty of suggestions and hints as to how and where to look for further information.</p>
Table of Contents (19 chapters)
Building Online Stores with osCommerce: Professional Edition
Credits
About the Author
About the Reviewers
Foreword
Introduction
Index

Disaster Recovery


Making sure that access is properly controlled and that code cannot be subverted for unintended purposes is only a part of the concept of security. Ensuring that you can recover in the event of some unforeseen circumstances or an Act of God, as the insurance companies like to call it, is all part of an integrated security policy. I'm sure many of you, as have I, have worked on a document when for no reason the application simply packs up and says something suitably terse like I am going to close down and ensure that the last three hours of your hard work will never be seen again <insert evil laugh and fade to blue>.

Well, if this has happened on a document, then you can imagine the amount of anguish you are likely to experience when the last three years of sales information along with your configuration settings and database are erased by a ten year old kid who has breached your security and wiped the slate clean. Without a proper disaster recovery policy it is...