I created a template but can't get it to work. I added a javascript slide show and a CSS menu bar. I noticed that the javascript onload code in the body tag is similiar to the php onload code and may be causing issues. I have posted part of the code here. If the whole code is desired I can post it let me know.
I created a template but can't get it to work. I added a javascript slide show and a CSS menu bar. I noticed that the javascript onload code in the body tag is similiar to the php onload code and may be causing issues. I have posted part of the code here. If the whole code is desired I can post it let me know.
My server has several domains on it with several installations drupal 4.7 being used. Lately my server has been hitting its privvmpages limit. I'm not sure if Drupal is the culprit or just my steady growth of traffic finally crossed over being too much. (I've grown to about 11,000 page requests a day for a 256mb ram on the server). So I was wondering if by chance anyone out there has experienced any problems with reaching their privvmpages limit on their server with drupal.
I'd just like to say that caching support kicks ass. My site (http://www.wii-linux.com/) was slashdotted and dugg at the same time yesterday, peaking at around 18,000 pageviews. The server is a dedicated single processor xeon running apache2/mysql on ubuntu breezy badger server with no special tweaks for speed. I had the cache set to 15mins, and throttled some of the more processor intensive stuff and there was only a slight slowdown in usability overall.
I've been evangalising PHP/MySQL in general and Drupal in particular for the basis of a website that's currently built on a mashup of technologies (PHP/MySQL/Java/JSP/Oracle, etc). We're currently doing between 5 and 6 million pageviews/month (around 200K / day), ans will be adding a bunch of social networking functions over the coming 6 months. We're achieving 99.9% (ish) availability (incl scheduled outages), with an agreed target of only 97%. My current (beta) tech strategy says that we'll move to PHP/MySQL as our sole environment, and is being met with various levels of acceptance up and down the food chain - but seems likely to be accepted and implemented at the moment.