comment on

We are using Metadot and actually having a problem with it.

In October, we did a multiple upgrade -- to RH Enterprise, to Apache 2.0, to Plesk Reloaded control panel (from Ensim), to Persistent Perl, and to the latest version of Metadot. Something broke the file upload capability in the software.

In our investigation we suspect something going on with the handling of the POST of the form that does the upload. Seems that the server times out. The form does not appear to be malformed.

I am actually willing to retain a Perl guru to help us figure out what's going on, so if you're interested, email headguy (at) thewimaxguys.com. We also need someone to help develop and maintain the code in the long run.

Sorry if this is inappropriate in this forum. I'm a n00b here. But I would appreciate any pointers to info or people who can help. And, yes, I've posted on the Metadot forum to no avail.

Thanks for any ideas.

Mike Ellsworth

In reply to Re^2: Experiences with Metadot? by mellsworth
in thread Experiences with Metadot? by neilwatson

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks