I have a patch ready that makes a phpinput.module and removes all that code from core filter module. I need to reroll it against a more recent HEAD, for it has some conflicts. And since it will be post 4.7 I want to wait a bit more with it, because I will have to maintain it all along. Bèr Op zaterdag 28 januari 2006 22:57, schreef Karoly Negyesi:
Hi!
A good read is http://www.webschuur.com/node/409 . Some points I do not care of, but:
1) As Drupal moves forward, upgrading PHP nodes is cumbersome at best. (blocks are easier to be found) 2) The security aspect. PHP filter is just too powerful. I can debate to death that it's safe now, no matter what -- the mere presence of PHP filter will make baby Rasmus cry :D
However, it's true that defining a whole module is more complicated than a php node. Is it? I submitted a patch http://drupal.org/node/46857 which adds an 587 bytes module to core which lets you save a PHP into something.inc and then view it at the path pages/something. It just can't be simpler.
Also, defining a block is more difficult than just using a snippet. Is it? No. The necessary module is a lot complicated this time, 690 bytes :) .
Kind regards
Karoly Negyesi
-- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com |