Karoly Negyesi (chx)

Drupal 6 modules typically defined their own tables, had their own code to maintain them and then used nodeapi to hook into the system. Or, defined node types but still maintained their own tables. In Drupal 7 instead you should just create fields, instance them on node types you want to work with. Instead of altering a form directly you can write a widget. Display your data with a formatter. Don't worry about data storage, field API handles that for you. And then there is the EntityFieldQuery class to help with finding things.

It seems that some theme stuff (like the favicon and the logo and probably unaggregated CSS/JS) is passed as Drupal paths into file_create_url while aggregated CSS and JS is served from public://. So we need to implement file_url_alter and override the getExternalUrl of the DrupalPublicWrapper class

Computers as running only closed applications controlled by operating system vendors–

Are we going to be the ruling elite who controls the world? Do not be so naive. We will be hated by the powers that be because we still have that spark and because they rely on us to program the masses. The unwashed masses are going to look at us with suspicion because we think so differently. Hated by everyone, weeping for the lost freedom, that's our future.

If not resisted, probably. Open source free software!

Slap #access = FALSE on form elements you dont want to see in the current step and then set up the Next button with #limit_validation_errors set to the elements you are about to see. The Prev button should get an empty #limit_validation_errors. Should field validation errors bother you, you can nuke those in hook_field_attach_validate.

As teached by many excellent usability books, confirm forms are wrong, they become habitual and are just a nuisance instead of protecting you from mistakes. The computer should just do what its operator says and make it possible to revert easily.

Here here!!

How to debug the "Fatal error: Exception thrown without a stack frame in Unknown on line 0" error message with try-catch.