[support] Validation Error

[Earnie Boyd]

Quoting "Tom Holmes Jr." <tom at tomholmes.net>:

> Wow ... absolutely stunning ...
>
> Anton ... Yes, I know ... I am not 100% using the recommended
> requirements of Apache and the mod_php,
> Maybe thats because the Drupal Community hasn't tested this out with
> Tomcat, JBOSS, Resin, or any of a dozen other web-servers out there.

And why should we?  It isn't standing OP for PHP.

> I've have done EXTENSIVE research and there are quite a few articles
> extolling the virtues of running Drupal on Resin for the performance boost.

I've seen some of that but I've never attempted it.  If ppl who have 
experience with this setup exist on this list they can speak up to help 
but if not I'm afraid your SOL with help with this configuration on 
this list.

> Go ahead and Google:    Resin and Drupal .....
> If I had installed this on Apache and STILL got the error ... do you
> honestly think I would get an answer quicker?
>

Maybe more responses even.  If ppl who have RESIN/Drupal experience 
exist on this list they can speak up.  You're configuration doesn't fit 
the majority so the majority will be silent except to say that it isn't 
the standard setup.

> I've spent the last two days researching this issue and from what I can
> see, this was an issue with 4.x which NEVER got resolved.

Did you give pointers to the issues?  Sorry, I don't remember, but are 
you sure it wasn't resolved?  "Validation Error" sounds very generic 
and can be applied to many situations.

> Now it seems the issue is still around ... and STILL there is no answer
> as to what is going on or how to fix this once and for all.

You still don't point to it.

> This is why corporations can go to proprietary software .... in hopes of
> getting a definitive answer ... there is no such promise from the open
> source world.

Corporations pay for ppl to be available to help.  They can do that 
with Drupal too.  See http://drupal.org/paid-services for a list of 
those willing to help for hire.

> But hey ... I'm an OSS advocate ... but if I had installed this on
> Apache, and still get this error ... I STILL wouldn't be able to sell
> this solution.

Just because you're struggling doesn't make the solution invalid.  I 
can understand though you wouldn't want to sell yourself out of a job 
that someone is paying you to do.  Especially since you're not able to 
resolve it.  Your attitude needs adjusted toward being nice to those 
who are trying to help.  Flames never do anything but fill the list 
with noise.

>
> Where I work ... we're a JAVA/J2EE shop and we have Resin which runs all
> our java/j2ee applications.

Drupal is PHP and not JAVA/J2EE.

> And I have been a Java/j2ee developers for the past decade ...

Drupal is PHP and not JAVE/J2EE.

> If I had written Drupal with the problems it has now without logging and
> more expansive error messages ... I'd be out of a job.

Have you looked at the watchdog table?  Is the error there?  Have you 
looked at the php errors or do you even have php logging turned on?  
Have you looked at the server logs to see what is written there?  Have 
you narrowed the list of modules to determine exactly where the errors 
happen?  Have you installed the devel module [1] to see if it might 
give clues?  Have you done all that you can to help debug the issue?

> if I was a PHP programmer ... I'd probably have this fixed by now ...
>

Now we get to the source of your anger.  You have been asked to learn 
something new and pressed for time just haven't spent the time needed 
to get beyond square zero.  In my nearly 30 years of experience I've 
learned one thing about differing programming languages.  It is all 
data->process->data and the only thing that changes in the syntax of 
the process and the format of the data.

> Maybe I could make a few suggestions to the Drupal community:
> 1) accept that it is a problem and fix it

The problem is yours until you point us to an issue.  We are willing to 
help but only if you are willing to listen.

> 2) maybe expand on the error messages instead of the generic message

Maybe you haven't looked at all of the error messages yet.

> 3) maybe expand on some logging since this doesn't seem to generate any
> logging at all for this issue.

Maybe you haven't turned on all of the logging that is needed.

> These would go a long way to explaining what the issue is and how to fix
> it ... right?
>

I doubt that anything we do can help you in this moment of your 
frustration.  You are the one with the problem, not us.  You have to 
explain and help us help you.

> I wasted a lot of time today completely doing a fresh install only to
> get the same results three times ...

Why was it a waste to determine that the problem is repeatable.  There 
is nothing like a problem that isn't repeatable to waste time.

> After about the fourth time, I added all my modules at once and it
> finally started working.

How are you adding modules?  There are a core set that always need to be on.

> However ... I don't know if this error will pop up some time in the
> future .... and if it does ... I'm not gonna sell Drupal as a solution.
>

We still don't know what you installed to cause or fix the issue.  And 
we still don't know if this problem is RESIN only related.

[1] http://drupal.org/project/devel
[2] http://drupal.org/paid-services

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/