Reboot the PHP filter talk
Hi! Wow. This one exploded. Let me sum up what we have and provide a summed answer so that the conversation remains focused. "I can create customized views into the data easily using PHP pages. It would take 10 times as long to write a custom module to do the same work." This quote nicely sums up what we have so far. However this is not true for Ber's nor for my proposal. I said: move the snippet into an inc. Same amount of work to _author_ the PHP code than the current solution. Upload is a bit harder. However, it seems that people are really want to enter PHP code in a webform so, I stepped a bit back and Ber's patch is preferred. I still doubt that if someone has the knowledge to author PHP, then he can't use FTP. Ber's patch is a true Drupal solution (mine is not). It factors out the PHP filter to another module and let's you decide whether you want a more secure site with this module off (even removed!) or you want to continue where you are currently. The two solutions, however, are complementary. If you do not have a PHP filter at all (Ber's patch) you could still want to use snippets quickly and easily. Regards NK
On Sunday 29 January 2006 17:14, Karoly Negyesi wrote:
Ber's patch is a true Drupal solution (mine is not). It factors out the PHP filter to another module and let's you decide whether you want a more secure site with this module off (even removed!) or you want to continue where you are currently.
Notwithstanding my earlier comments, I'm pretty much okay with this plan. Ber made a good point about the multi-site installation. I run a number of Drupal sites, but they are all on different hosts so I don't instinctively think in terms of multi-site installation. Installing one extra module is not that big a deal, if it brings a big benefit to other installation types. The one thing that I do feel strongly is that it *should* be possible -- if one wishes -- to do pages with embedded code, without having to write a module. I have several sites where I am the only administrator and need to do simple queries into other non-Drupal applications. I'd hate to have to maintain a module just to support a dozen lines of actual code, where that code isn't dependent on Drupal functionality. So I'll concede Ber's point as long as the separate module's installation puts me back where I am today. I find it interesting to see how many _qualitatively_ different ways there are to use Drupal -- that speaks well of Drupal's versatility. Scott -- ------------------------------------------------------------------------------- Scott Courtney Drupal user name: "syscrusher" http://drupal.org/user/9184 scott at 4th dot com Drupal projects: http://drupal.org/project/user/9184 Sandbox: http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher
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 |
Karoly, extending your idea of .inc files. How about making a filter for including PHP snippets. This way you could pass parameters to a snippet, we could copy all those PHP snippets on drupal.org into such .inc files. Regards Tadej On 1/29/06, Karoly Negyesi <karoly@negyesi.net> wrote:
Hi!
Wow. This one exploded. Let me sum up what we have and provide a summed answer so that the conversation remains focused.
"I can create customized views into the data easily using PHP pages. It would take 10 times as long to write a custom module to do the same work."
This quote nicely sums up what we have so far. However this is not true for Ber's nor for my proposal. I said: move the snippet into an inc. Same amount of work to _author_ the PHP code than the current solution. Upload is a bit harder. However, it seems that people are really want to enter PHP code in a webform so, I stepped a bit back and Ber's patch is preferred. I still doubt that if someone has the knowledge to author PHP, then he can't use FTP.
Ber's patch is a true Drupal solution (mine is not). It factors out the PHP filter to another module and let's you decide whether you want a more secure site with this module off (even removed!) or you want to continue where you are currently.
The two solutions, however, are complementary. If you do not have a PHP filter at all (Ber's patch) you could still want to use snippets quickly and easily.
Regards
NK
participants (4)
-
Bèr Kessels -
Karoly Negyesi -
Syscrusher -
Tadej Baša