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. 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. 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?
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. 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. 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. 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.
Where I work ... we're a JAVA/J2EE shop and we have Resin which runs all our java/j2ee applications. And I have been a Java/j2ee developers for the past decade ... 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. if I was a PHP programmer ... I'd probably have this fixed by now ...
Maybe I could make a few suggestions to the Drupal community: 1) accept that it is a problem and fix it 2) maybe expand on the error messages instead of the generic message 3) maybe expand on some logging since this doesn't seem to generate any logging at all for this issue. These would go a long way to explaining what the issue is and how to fix it ... right?
I wasted a lot of time today completely doing a fresh install only to get the same results three times ... After about the fourth time, I added all my modules at once and it finally started working. 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.
Thanks! Tom
HI Tom,
On Dec 4, 2007 4:45 AM, Tom Holmes Jr. tom@tomholmes.net wrote:
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. 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.
I do suspect that the "Access Denied" error has to do with the "access" table and with one or another module that controls "access" that gets removed or uninstalled without the proper columns in the appropriate tables removed.
In many Drupal sites over two years this was the first time I got this, and I did remove all sorts of crud from my site in anticipation of the upgrade.
BTW - The only role cache plays in this issue is that in due course the cache table is filled up with access denied messages. This is why clearing cache is a very short term solution.
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.
My experience is that in the case of proprietory software you do get the promise to fix the problems. And then you wait a long time, maybe years and then you pay for the upgrade.
Maybe I could make a few suggestions to the Drupal community:
- accept that it is a problem and fix it
That is one of my peeves. There are a few problems that have been skulking around for a loooong time and when you hit the problem the response is "what, that problem? what about it?" Maybe the Drupal community should skip the future 7.0 release of Drupal in terms of adding absolutely no new cutting edge features but rather to concentrate 100% on stability and useability and most importantly to update every single Drupal module and theme to that release!
- maybe expand on some logging since this doesn't seem to generate any
logging at all for this issue.
I would like to see some automated error logging from within the "admin" interface that reports these "errors" so that fixing these errors can be prioritized.
I share your frustrations, but hey, there is nobody out there to find the solutions and to post the answers but us. That is really at the core of Drupal. At the same time, I become frustrated because the focus remains constantly at the "cutting edge" and the core stability does not necessarily receive the same attention.
future .... and if it does ... I'm not gonna sell Drupal as a solution.
I have thought more than once about searching for something "better" and every time I return to Drupal!
I will keep you updated on any solutions I can find. BTW do you get "accessed denied" when you do a core install without additional modules?
Casper
------------------------------------------------------------ Casper Labuschagne +27827054416 ; Skype=krooninfo ; Struggling with computer errors, virusses and spyware? Are you forced to upgrade all your hardware and software? There is an alternative to the Windows madness! Visit http://www.ubuntu.com and install Ubuntu Linux!
On 04/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
Wow ... absolutely stunning ...
If I had installed this on Apache and STILL got the error ... do you honestly think I would get an answer quicker?
I wasn't suggesting it to get you an answer quicker. It was to help you towards getting an answer at all by eliminating some variables.
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. 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.
Having never had this problem myself, I did some searching. As far as I can tell you are probably dealing with a different problem. There was a patch applied in 5.3 for an issue with the same error message. I suspect you are dealing with something else specific to those contrib modules.
Just because something says "validation error" doesn't mean it is the same problem. It's not like null pointer exceptions in Java apps all come from the same bug.
Maybe I could make a few suggestions to the Drupal community:
- accept that it is a problem and fix it
There hasn't been any indication so far that you have tried any of the suggestions for isolating this problem. This problem you've hit certainly hasn't crippled everyones Drupal sites, so it is going to take some diagnosing to find out how to reproduce it.
The mailing lists or forums aren't the place for tracking and fixing bugs. These are just for getting some help from fellow users. Once we've helped you isolate the problem, you'll be able to file an issue against the right components where it can be tracked by the developers that work on those components.
My comments below:
Anton wrote:
On 04/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
Wow ... absolutely stunning ...
If I had installed this on Apache and STILL got the error ... do you honestly think I would get an answer quicker?
I wasn't suggesting it to get you an answer quicker. It was to help you towards getting an answer at all by eliminating some variables.
I ALWAYS try to lookup information from these mailing lists, then the forums on the Drupal site, the Drupal site in general, and then finally extending out to Google. I tried to provide as much information as possible and I am willing to provide more. As I think I clearly stated ... I installed Drupal in two different environments: one where both resin/drupal/mysql are all on my laptop ... and the other environment where resin/drupal and mysql are separate servers. The former works ok, the latter does not ... that makes me think there is something else wrong and it's not resin. But both you and Earnie seem to have this fixation that I did not test it out with Apache/PHP ... since this issue has been around since 4.73 with users presumably using Apache/PHP ... I thought logically ... that it was irrelevant.
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. 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.
Having never had this problem myself, I did some searching. As far as I can tell you are probably dealing with a different problem. There was a patch applied in 5.3 for an issue with the same error message. I suspect you are dealing with something else specific to those contrib modules.
Just because something says "validation error" doesn't mean it is the same problem. It's not like null pointer exceptions in Java apps all come from the same bug.
Yes ... I know ... but logging and error messages would be a great help. If you, like me, do Java development ... you use logging and error trapping extensively so you can track bugs in your code. We hope our co-workers who do Java development do the same thing ... that way you can debug their code if necessary ... the more logging and error trapping the better .... right?
Maybe I could make a few suggestions to the Drupal community:
- accept that it is a problem and fix it
There hasn't been any indication so far that you have tried any of the suggestions for isolating this problem. This problem you've hit certainly hasn't crippled everyones Drupal sites, so it is going to take some diagnosing to find out how to reproduce it.
As I stated above ... I have tried to always provide as much information as I had, and I am willing to provide more if needed. Just ask me ...I did thoroughly explain what I did to do an install and what modules I installed. And the fact that one system works and one does not with almost the same setup. I also did turn off the caching as someone else mentioned ... and that did NOT fix the problem.
I know you and Earnie want me to test this out with Apache/PHP ... and when I get the time today ... I will. If I get the same error ... then it's NOT ME!!!!!! If I don't get the same error, then I will continue to test out on my own to see why this is happening. But as I previously stated ... since this was happening with 4.x and has been a long time problem ... I presume past users had he problem with Apache/PHP. But ... I will try with Apache/PHP though I think I will get the same issue ... and for all I know it's a problem with a contributed module ... I don't know. Maybe it's a combination on how I added those modules .... again who know's.
The mailing lists or forums aren't the place for tracking and fixing bugs. These are just for getting some help from fellow users. Once we've helped you isolate the problem, you'll be able to file an issue against the right components where it can be tracked by the developers that work on those components.
This particular mailling list may not be for fixing bugs, and that was NOT my original intent. My original intent was to find out if anyone had this issue and how to resolve it. The one thing that is aggravating is when someone reports a problem, fixes it ... but then doesn't tell anyone how to fix it. So, I looked at the drupal site and finally google. I see this question being asked a lot ... and have NOT YET seen anything anywhere in the Drupal Site .... in the bugs/issues area that this is even logged. That to me is problematic ....
I am sorry for my bad attitude ... but I felt the attitude I got wasn't exactly great from you! Instantly questioning why I would install this on Resin as opposed to Apache/PHP because that wasn't required ... in essence I felt like you were saying .... "well if you had done that ... it wouldn't have been a problem."
So ... I will continue testing with Apache/PHP and see if it still is an issue ... and I will experiment with adding the four modules that I did. And if it's still a problem ... I am going to either A) fix it myself B) drop Drupal as being an insufficent enterprise-ready CMS system
Thanks and have a lovely day! Tom
On Dec 4, 2007, at 11:12 AM, Tom Holmes Jr. wrote:
Yes ... I know ... but logging and error messages would be a great help. If you, like me, do Java development ... you use logging and error trapping extensively so you can track bugs in your code. We hope our co-workers who do Java development do the same thing ... that way you can debug their code if necessary ... the more logging and error trapping the better .... right?
In all fairness PHP vs. Java debugging is not even in the same category. To do real PHP work including traces will probably require debugging extensions or such, which may or may not be compatible with your server environment. Whereas in Java that stuff is bolted into the environment that runs your app, pretty tightly.
Some things that might help can be found at the links below: http://www.johnandcailin.com/blog/cailin/log4drupal-logging-api-drupal http://drupal.org/project/trace http://drupal.org/project/visualize_backtrace
Visualize backtrace is very cool, but requires xdebug, which may or may not work with resin. Please let us know if it does. (or any debugging plugins for PHP for that matter)
-Mike
__________________ Michael Prasuhn mike@mikeyp.net http://mikeyp.net 949.200.7595 714.356.0168 cell 949.200.7670 fax
On 05/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
I tried to provide as much information as possible and I am willing to provide more. As I think I clearly stated ... I installed Drupal in two different environments: one where both resin/drupal/mysql are all on my laptop ... and the other environment where resin/drupal and mysql are separate servers. The former works ok, the latter does not ... that makes me think there is something else wrong and it's not resin.
Maybe. If the problem still cropped up on mod_php to a remote MySQL server, then I'd agree Resin has been eliminated as a variable. The reason I'm harping on about eliminating Resin is because it is a VASTLY different environment to everything else. It isn't the fact that the web server is written in Java (that is the minor bit) - it is the fact that PHP itself is reimplemented in Java, and there are huge differences between the way a JVM compiles/optimises/runs something and natively compiled code runs.
There could be a subtle session problem with the php-mysql libraries in Resin when using a remote mysql server - is that not plausible? After all plently of hosting providers host Drupal on mod_php with remote mysql servers.
I don't know if you've followed Jython or JRuby development, but getting those environments to the point where most complex applications or platforms work on them isn't trivial. And the Jython/Jruby teams will always be shaking out the obscure corner case issues that are exposed by new applications.
But both you and Earnie seem to have this fixation that I did not test it out with Apache/PHP ... since this issue has been around since 4.73 with users presumably using Apache/PHP ... I thought logically ... that it was irrelevant.
You still haven't pointed to the actual issue report. The main candidate I manged to find (http://drupal.org/node/63990) that matches your description has already been patched (in Drupal 5.x) for a couple of months, and Drupal 5.3 has been released since then.
So I suspect you are talking about a different issue altogether. But without you telling us what issue you are talking about we don't know.
As I stated above ... I have tried to always provide as much information as I had, and I am willing to provide more if needed. Just ask me ...I did thoroughly explain what I did to do an install and what modules I installed. And the fact that one system works and one does not with almost the same setup. I also did turn off the caching as someone else mentioned ... and that did NOT fix the problem.
Great. That is useful. Unfortunately as far as I can tell you haven't told us that before.
I know you and Earnie want me to test this out with Apache/PHP ... and when I get the time today ... I will. If I get the same error ... then it's NOT ME!!!!!!
Exactly. Which is why we want to know that.
But as I previously stated ... since this was happening with 4.x and has been a long time problem ... I presume past users had he problem with Apache/PHP.
You still haven't pointed out which problem you are talking about. As I said before the same error message doesn't indicate the same problem.
But ... I will try with Apache/PHP though I think I will get the same issue ...
I hope so too - it will be far more easily fixed by the developers that way.
and for all I know it's a problem with a contributed module ... I don't know.
I suspect it is a contrib mondule myself. Most contrib modules don't get anywhere near the scrutiny and review that Drupal core gets.
The one thing that is aggravating is when someone reports a problem, fixes it ... but then doesn't tell anyone how to fix it.
example?
I see this question being asked a lot ... and have NOT YET seen anything anywhere in the Drupal Site .... in the bugs/issues area that this is even logged.
Well someone with the problem has to log it. What we are trying to do is help you narrow down where to log it (eg the contrib module(s), core, or even Resin).
Instantly questioning why I would install this on Resin as opposed to Apache/PHP because that wasn't required ... in essence I felt like you were saying .... "well if you had done that ... it wouldn't have been a problem."
Not at all. Maybe it is my old sysadmin background, but when your job is diagnosing and isolating problems in large hetrogenous software stacks you see the importance of eliminating as many variables as possible. Otherwise it is just futile guesswork.
I would actually prefer the problem be confirmed with mod_php. It will get fixed quicker, and be one more step towards Resin being Drupal ready (which is exciting).
I think Java development has shielded you somewhat from the platform specific differences involved in other cross platform development environments. And to be honest Resins PHP implemented in Java (while really cool and exciting) is probably PHPs biggest divergence ever from the platform the actual PHP project produces. It is a far bigger change than that between different Java VMs, and you can't deny that changing JVMs can cause problems with some applications.
It is extremely naive to expect it will be problem free. It will mature and get better the same way APC, e-accellerator, fast-cgi, PHP on IIS, lighthttp, nginx etc are all maturing and getting better. Early adopters of those platforms have all gone through varying amounts of the same pain you are.
And if it's still a problem ... I am going to either A) fix it myself B) drop Drupal as being an insufficent enterprise-ready CMS system
Hell I wouldn't use PHP at all if I was a enterprise user :)
But sorry, one issue with 3rd party plugins when using an application on an obscure unsupported and untested platform is effectively meaningless when judging that applications enterprise readiness.
Lets face it enterprise software usually has very strict system requirements for what is supported and enterprises are very anal about sticking to those requirements.
Would something like Websphere be unready for the enterprise if your Java web app ran into problems when you ran Websphere on some obscure (but very fast) new JVM written in Lisp? I doubt IBM would give you any support even if you proved the problem was with Websphere.
There are far more legitimate enterprise concerns with Drupal than this issue.
On 05/12/2007, Anton anton.list@gmail.com wrote:
On 05/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
As I think I clearly stated ... I installed Drupal in two different environments: one where both resin/drupal/mysql are all on my laptop ... and the other environment where resin/drupal and mysql are separate servers. The former works ok, the latter does not ... that makes me think there is something else wrong and it's not resin.
Maybe. If the problem still cropped up on mod_php to a remote MySQL server, then I'd agree Resin has been eliminated as a variable. The reason I'm harping on about eliminating Resin is because it is a VASTLY different environment to everything else. It isn't the fact that the web server is written in Java (that is the minor bit) - it is the fact that PHP itself is reimplemented in Java, and there are huge differences between the way a JVM compiles/optimises/runs something and natively compiled code runs.
There could be a subtle session problem with the php-mysql libraries in Resin when using a remote mysql server - is that not plausible?
Sounds even more plausible now...
After stumbling across Resins bug tracker, it looks like Resin 3.1.4 fixed a bug with connecting to remote mysql servers. eg:
http://bugs.caucho.com/view.php?id=2103 http://bugs.caucho.com/view.php?id=2074
Hopefully an upgrade to Resin 3.1.4 will fix all your problems, and Drupal will instantly become enterprise ready again.
It looks like Caucho use Drupal for their forums (I'm learning stuff all the time). I'd say at least someone in high places has a stake in making Drupal run well on Resin.
As part of Resins maturing process, they seem to be fixing lots of bugs that are found by running Drupal.
On Dec 4, 2007 11:11 PM, Anton anton.list@gmail.com wrote:
It looks like Caucho use Drupal for their forums (I'm learning stuff all the time). I'd say at least someone in high places has a stake in making Drupal run well on Resin.
Maybe they would be willing to help with Tom's problem or already know of it if it's Resin related?
Can't hurt to ask.
Regards, Skip
Thank God I drink! :-) a lot ....
I've download apache 2.2.6 (latest/greatest) ... downloading PHP 5.2.5 (lates/greatest) ... still have the latest/greatest Drupal 5.3.
Then I'll move over my modules and see if I get the same error.
Skip Taylor wrote:
On Dec 4, 2007 11:11 PM, Anton <anton.list@gmail.com mailto:anton.list@gmail.com> wrote:
It looks like Caucho use Drupal for their forums (I'm learning stuff all the time). I'd say at least someone in high places has a stake in making Drupal run well on Resin.
Maybe they would be willing to help with Tom's problem or already know of it if it's Resin related?
Can't hurt to ask.
Regards, Skip
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.14/1172 - Release Date: 12/5/2007 8:41 AM
On Tue, 04 Dec 2007 14:12:27 -0500 "Tom Holmes Jr." tom@tomholmes.net wrote:
one where both resin/drupal/mysql are all on my laptop ... and the other environment where resin/drupal and mysql are separate servers. The former works ok, the latter does not ... that makes me think there is something else wrong and it's not resin.
Why do you think that if one environment work and the other doesn't it is a Drupal problem? I mean... it may still be a Drupal problem... maybe something related to DB and session generation that goes "out of sync" when DB is not on localhost, but I wouldn't put the blame on Drupal for certain. Yeah, the fact that it happened before could be in support on your hypothesis... but still could you explain why you think that the difference in env is a clue of a Drupal problem?
Could it be a difference in php settings in the 2 environment? I don't know how Resin works in regard as stuff like php.ini. Could it be something related to clean urls?
But both you and Earnie seem to have this fixation that I did not test it out with Apache/PHP ... since this issue has been around since 4.73 with users presumably using Apache/PHP ... I thought logically ... that it was irrelevant.
Yep a clue... maybe they are two slightly different issues. In which version of Drupal was this problem reported? If you could reproduce it so easily it would be a more popular argument of complain. That's why the hypothesis of a problem in the environment seems a good one too. To be clear, I think no one that like Drupal would be sad to see Drupal happily running on one more environment. So that's not a way to say it is your business.
Maybe it's a combination on how I added those modules .... again who know's.
Sorry I didn't follow the whole thread... do you mean that it happens just when some modules are activated?
So ... I will continue testing with Apache/PHP and see if it still is an issue ... and I will experiment with adding the four modules that I did. And if it's still a problem ... I am going to either A) fix it myself B) drop Drupal as being an insufficent enterprise-ready CMS system
Drupal is actually one of the most promising CMS for the enterprise [1].
Don't get mislead by the heat.
[1] despite people sustaining that pgsql should be put to sleep eternally http://www.drupal4hu.com/node/64
both you and Earnie seem to have this fixation
Hey now, don't leave the rest of us out. I've been silently nodding along here as I presume others have.
For what it's worth I spent years leading enterprise java development projects in large corporations for uber-large clients. And I wouldn't have used php for any of those projects (and that has nothing to do with drupal or resin). It's simply still missing far too many of the things that are important in that environment. Enforcing clean development and documentation, robust IDEs, Control over threading/synchronous asynchronous transactions, robust logging and debugging capabilities, proprietary source code control through compilation to name just a few.
At this point though I'm much happier to be on this side of the fence and able to develop pretty robust and feature rich solutions for medium sized companies in a fraction of the time and at a fraction of the cost. It does come with the tradeoff of having to figure things out yourself sometimes, but you'll find a much larger and supportive community of people to help you do that than in java (presuming you don't piss those people that are helping for free off)
So ... I will continue testing with Apache/PHP and see if it still is an issue ...
sounds good, would love to hear about the results
and I will experiment with adding the four modules that I did.
And if it's still a problem ... I am going to either A) fix it myself
There you go, now you're half the way to being part of the open source community! Next step, offer a patch back to the community and/or help someone else with their problems. That's how it works.
B) drop Drupal as being an insufficent enterprise-ready CMS system
And that may be the answer.
.sander
p.s. - we do want to help
Quoting "Tom Holmes Jr." tom@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:
- 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.
- maybe expand on the error messages instead of the generic message
Maybe you haven't looked at all of the error messages yet.
- 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/
-
Anton -
Casper -
Earnie Boyd -
Ivan Sergio Borgonovo -
Michael Prasuhn -
sander-martijn -
Skip Taylor -
Tom Holmes Jr.