ICEcoffee

I've spent many hours building my project with Drupal, without digging in deep to the API. As I said I don't require massive CMS functionality, the standard Drupal blog and forum modules are lacking (common knowledge), I've uninstalled CCK and views modules because there were massive behemoths. I started with Drupal because I thought it would save me loads of man hours/coding, but some of the problems I have experienced.... I'm starting to question my initial decision.

CORRECTION: should be: Drupal is know for horrendous amounts of db calls just to serve up even a SIMPLE page.

@Anti-Moronic: thanks very much for the fullness of your reply. I was thinking the same. I don't need nor desire my fixed content pages to be served up by a database. Other data - fine, because they would be input from users ie submitting comments. Drupal is know for horrendous amounts of db calls just to serve up even a page. The most complicated thing on the site would be a simple e-commerce section which interfaces with PayPal IPN, and that I'm sure I can hook in with a class from PHPclasses. I thought it would be sensible to get some feedback from others, perhaps more experienced than myself, before making a a decision. Coding my own would mean I am very familiar with the code and there would be more satisfaction at the end result.

Hi all I have run into several critical issues with Druapl. I have spent months (I'm a sole, inexperienced developer) working on a project for myself, but have been vexed at the following: white screen of death: result - my app just stops working, displaying only a white screen. This is a PHP memory issue (I'm on shared hosting - though with generous settings ie 128MB PHP_memory available). I also find I can't search for PHP code within nodes Drupal is slow as a dog - the built in caching helps. Now, I have toyed with the idea of coding my own app. I have limited knowledge in PHP, HTML, CSS etc though I have been developing for over five years. I thought of doing my own site from scratch, as I don't really need a full on CMS/community app. I mainly need to serve pages (probably includes), with minimal MySQL for user / authentication. I don't mind starting off with less functionality and thought that I could simply 'bolt-on' classes/functions from scripting sites, till I get up and running. Can I please have your opinion. I know I've given limited background info, but can supply more if required. I just want to see if I'm being arrogant and stupid.

Hi, I am in the early stages of developing a web app in PHP/MySQL. It is predominantly procedural (with type of MVC approach)in coding style though I do have some classes included(). ATM, I have my navigation links going straight to a bare-bones file that sets up variables for that page, such as: $pageAuthLevel, $metaPageTitle, $metaPageContent, $metaPageKeywords. Also defined in this page is the include paths for the actual html content file, the pages controller and lastly the pages view. I know I could include all this data in a MySQL db table and the include files from within the controller. The advantage of doing it the way I have it currently, is that the links are already written in an SEO friendly manner eg: /about-this-site.php and saves me from having to learn and setup mod_rewite in an .htaccess file. The disadvantage is that I have an additional file for every 'content' file, but the filesize is small and disk space is cheap. My question is though, which method is more efficient in terms of performance, scalability and security?