Re: [development] Reboot the PHP filter talk
If I can butt in here long after talks have calmed down, I believe this is a good move, but it could be better if you could have some sort of name.filter that is plugged in with the filter.module, don't you think? In other words, simply copy the new .filter file in the same folder as the module to make it work? Regards, Kobus
ber@webschuur.com 1/30/2006 11:33:25 AM >>> Op maandag 30 januari 2006 05:09, schreef Syscrusher: So I'll concede Ber's point as long as the separate module's installation puts me back where I am today.
Yes. This has never been opposed. I think the fact that I, and chx, made some strong points about why one might (or should) not run PHP from the database, made people raise te pitchforks. but: * there are no plans or proposals to remove the PHP input filter * We only want to make it more modular and a lot safer by default. Bèr -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com |
Op maandag 30 januari 2006 10:36, schreef Kobus Myburgh:
If I can butt in here long after talks have calmed down, I believe this is a good move, but it could be better if you could have some sort of name.filter that is plugged in with the filter.module, don't you think? In other words, simply copy the new .filter file in the same folder as the module to make it work?
I oppose to Yet Another Module System. we have the .module. What would be next .menu? .node? .user? etc. hooks are perfectly fine for this IMO. -- [ Bèr Kessels | Drupal services www.webschuur.com ]
participants (2)
-
Bèr Kessels -
Kobus Myburgh