Apr 19, 2007, 8:10 PM
Post #1 of 6
I have a program which I worked on for at least a week with 40+ hours of time and I use the perl module called HTML:Defaultify
Why is installing a perl module such a pain for some webhosts?
I have an application at my website for a mortgage loan which people can start and if they want to save it and return to it later they just click a little checkbox and the data from the form is saved to a text file. Then they get an email with the code they use and a link to a form where they can retrieve their application with their data populated into the form. I used the module and I had two other webhosts Ipowerweb and another one which had no problem installing this module.
Now I have moved to netfirms, and this is the message I got dumb response from John ...
Thank-you for expressing an interest in this feature.
At the moment, we do not offer the HTML/Defaultify Perl Module. Although we do not add features and modules on the fly, it has been added to our list of client requested features and may be included in a future service upgrade. All feature requests and new modules that we install are evaluated and fully tested through quality assurance before releasing to our customers. This will ensure that the newly added features and modules function optimally on the web accounts.
Thank-you for your suggestion.
Have not these modules already been tested? Isn't these module already signup off on by the leading authority on perl?
Why does netfirms have to be pompously slow and redundant and retest the modules? Why can't they just implement them?
What does retesting modules that have already been tested prove?