<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">Khalid Baheyeldin</b> <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Plesk is very finicky about the versions of software you install<br>and very jealous of its own configuration file.</blockquote><div><br><snip good characterization of Plesk> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So, this "fun" way will now extend to Drupal? Great. Means<br>more headaches for the clients and consultants.</blockquote><br></div>I still insist, this is not the case, in that we should not view one use case (non-technical person grabs hosting, chooses to auto-install Drupal instead of Joomla) with another (Drupal developer develops website as consultant, makes customized install of Drupal).
<br>These are different space and time use cases.<br>For example, at least one of my clients is someone who first got turned on to Drupal via a fantastico install, then when I was contracted, of course together with the customer we made our own SVN based install. One thing had nothing to do with the other, in fact, client already knew about Drupal, accepted Drupal.
<br>On the other hand, if thousands of people start installing and discovering Drupal via their Plesk consoles, and set up simple sites, what's the problem? If a consultant runs into limitations they can either do a manual install or change hosting.
<br>A client can afford a separate hosting for a project: the cost of hosting begins to approximate zero, anyhow.<br><br>saludos,<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br>
<br>