Many folks have also advocated for this so you are in good company. Since Steven will have to bless this patch, I suggest getting buy in from him on a use case. See his comment at http://www.acko.net/blog/drupal-filter-formats#comment-78 Also see an old patch at http://drupal.org/node/11225. There may be others around too. On 4/12/06 2:21 AM, "Gordon Heydon" <gordon@heydon.com.au> wrote:
Hi,
On Tue, 2006-04-11 at 09:53 +0200, Bèr Kessels wrote:
Op maandag 10 april 2006 01:40, schreef Gordon Heydon:
Also is it possible to have a filter that is allowed only in certain situations as I would like to turn all the ecommerce emails into filtered fields, but this does not really relate to a node at all.
You may want to look at blocks. They are not node (ugh) and still use the filters.
I have taken a look at this, and it was what I expected.
check_markup() is good if you want to call it in total isolation, ie so what is contained within the content don't really need to know where it is being called from.
In the case of a node with php content you can generally work out what the node is and do a node load to get the data. By this is really a little inefficient, because before calling the check_markup() from node_prepare() we already have the node object, so it would be nice if you can have the $node as a local variable so that you can use it.
Also with the filters it would be nice if they can be more content type oriented. I would like to be able to classify filters so that they only get used on certain types of content. So the current filters would be considered a global filters and would appear on everything, but for E-Commerce I could create a transaction filter class and this will only be display on the emails that are sent from ecommerce, and not in other areas like nodes.
Also when the filters are getting run we would be able to pass through a an array of variables which can be used by the filters.
I think that I have my 4.8 project.
What do people think.
Thanks in advance. Gordon.