[carpeperdiem]

I see both sides:

1. In the install/upgrade docs, there is a LINK to the most up-to-date documentation;
2. Customer expects correct documentation in distribution;

As a survivor of an x-payments install just last week, it is easy to miss a step. It's probably the most involved install I've ever done. I'm not talking about copy/pasting code. The x-payments install requires many things to happen successfully, else total failure. For the most part, it's documented, but yes, as Bullfrog pointed out, it's not all in one place.

The x-payments install and config requires multiple documents and lots of reading. In a more perfect world, it would be in one place.

Post-install, i wish the docs discussed template editing and steps for personalization. Without webmaster mode, it's a click and pray process.

But once configured, it's good to know that my cc processing is PCI-DSS secure. I don't think my customers care.

J