wsani

There is obviously a language barrier here, and it shows through the lack of grammar in your reply as well as the documentation, which you've provided. You meant to say "weak" not "week". I didn't say it was your job to cover anything other than set your customer's expectations correctly. If the module is highly experimental, then it needs to be disclosed ahead of time. I admit that it is being adverted as beta though, even so, beta doesn't mean I should use a search engine, not just Google, to figure out a product that you've released. This module is specific to WHMCS and XenServer and the online resources will leave much to be desired. I'm not debating the functionality of the module. I'm pointing out the fact that your documentation is misleading and/or lacks a few more details that are crucial. Look below: There is no "hope" of a COPY / paste because there is nothing that you can copy and paste. Most of the doc is information at best. There is no mention of the required packages. How? Through the web browser? What if the web page is just a blank page? Simply put, you can't "Google" the required steps for a module that's in Beta, and isn't widely used. Sorry... PS. I'm happy to see the module in existence. I'll be happier if it sees a little more development time though. Just a thought.

I wish I could agree, but, I feel this sound more like a cop out. A XenServer is a hypervisor that's a minimal version of RHEL. If you were to perform a CD install, you're going to end up with the same installation on all of your servers. Even if I were to keep what you've mentioned in consideration, I'm going to point out a few items, that is key in the success of the deployment, which aren't even mentioned in your document. I had to install a bunch of RPM packages just to be able to install RRDTOOL or PHP 5.2.12. Perhaps you can update the docs to actually discuss the needed packages. Luckily, I'm seasoned enough to walk through this and install the required packages, but, I can't say the same about everyone else. That said, a good application development process will always require a good set of documentation.

I see a lot of potential in this and I purchased the module. However, I'm a little uneasy about it since I need to get a bunch of packages (e.g. MRTG, Compiler, etc.) manually. There is a lot of room for simple mistakes, which could result in other issues. It would be really nice if you could make an RPM or even possibly provide us with an "fire and forget" script.

Nice look! I wondered that myself actually I'm sure Matt will include it in the coming versions, then again that's why we have Smarty templates. Hm, I personally haven't gotten that far yet. I've been fiddling with the templates a lot, so I'll add this to the to-do list. Thanks for pointing it out though.

This might be of use to you: http://willsani.com/2010/01/18/whmcs-client-email-log-link-modification/

I'm annoyed with pop-up windows, I don't want my customers to have to have to deal with them on our website, so I came up with a different way of displaying the email messages in the email log page: http://willsani.com/2010/01/18/whmcs-client-email-log-link-modification/ Hopefully this will be of use to some of you guys

I'm trying to rewrite the URL for networkissues.php to be a little more friendly. When I use the following in .htaccess it simply will not work: RewriteRule networkissues-view-(.*)\.html$ networkissues.php?view=$1 Any suggestions?

I made the mistake of upgrading to Parallels billing 5.3, 6.5 and finally 6.X, and now I can't use the import script. Has anyone successfully migrated from Parallels Billing version 6?

I'm considering moving away from ModernSucks 5.6 to WHMCS. Is this possible? If so, how easy is the process? Thanks.