HI,<br>If a predefined node say a page, a story or any other content needs to be displayed as a result of search or displaying authors created list of stories, etc is there any way of modifying the default node_view. I mean is there any facility like node_view_alter or something so that i can change the way the content is getting displyed through my module ???????????/<br>
Vishnu<br><br><div class="gmail_quote">On Thu, Nov 12, 2009 at 5:30 PM, <span dir="ltr"><<a href="mailto:development-request@drupal.org">development-request@drupal.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Send development mailing list submissions to<br>
<a href="mailto:development@drupal.org">development@drupal.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.drupal.org/mailman/listinfo/development" target="_blank">http://lists.drupal.org/mailman/listinfo/development</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:development-request@drupal.org">development-request@drupal.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:development-owner@drupal.org">development-owner@drupal.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of development digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: PHP Standards Group (Naheem Zaffar)<br>
2. Re: PHP Standards Group (Daniel F. Kudwien)<br>
3. Re: PHP Standards Group (Cameron Eagans)<br>
4. Re: PHP Standards Group (Jeff Greenberg)<br>
5. Re: PHP Standards Group (David Metzler)<br>
6. Doing hook_update_N() when module is installed (Randy Fay)<br>
7. Re: Doing hook_update_N() when module is installed (Ken Rickard)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 11 Nov 2009 18:10:22 +0000<br>
From: Naheem Zaffar <<a href="mailto:naheemzaffar@gmail.com">naheemzaffar@gmail.com</a>><br>
Subject: Re: [development] PHP Standards Group<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID:<br>
<<a href="mailto:3adc77210911111010n462becbcs4ac0bd4a18c1d562@mail.gmail.com">3adc77210911111010n462becbcs4ac0bd4a18c1d562@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
2009/11/11 Alex Bronstein <<a href="mailto:alex@craftyspace.com">alex@craftyspace.com</a>><br>
<br>
> +1 for requiring PHP 5.3 for D8 (that's obviously not a community decision<br>
> yet, just me saying I'd support a GoPHP 5.3 project)<br>
><br>
<br>
-1 as it kind of involves abandoning a majority of the current user base.<br>
<br>
Let's see how the 5.2 thing is handled first - the latest RHEL release is<br>
still on 5.1.6 (with maybe patches that may or may not give it enough<br>
functionality). If RHEL 6 does not get a move on, there could be many users<br>
crying foul on the support forums, and this is with<br>
what-I-assume-is-a-special-case ultra extended 2 year development cycle for<br>
Drupal 7 instead of the previous 6 to 9 month cycles.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.drupal.org/pipermail/development/attachments/20091111/a04bcd88/attachment-0001.html" target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091111/a04bcd88/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 11 Nov 2009 20:37:37 +0100<br>
From: "Daniel F. Kudwien" <<a href="mailto:news@unleashedmind.com">news@unleashedmind.com</a>><br>
Subject: Re: [development] PHP Standards Group<br>
To: <<a href="mailto:development@drupal.org">development@drupal.org</a>><br>
Message-ID: <3b2d01ca6306$6ca1d820$<a href="mailto:0200a8c0@structworks.com">0200a8c0@structworks.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
> "we'll be involved in developing such standards and will<br>
> adopt them wherever feasible, but we do not commit to<br>
> following all standards if they are incompatible with<br>
> Drupal's basic architecture."<br>
><br>
> --Larry Garfield<br>
<br>
+1 Yes, that makes sense. I think it is what we (sometimes silently) did<br>
anyway. Some of our standards are self-made (for good reason), but there<br>
are also a couple that were directly derived from example code snippets on<br>
<a href="http://php.net" target="_blank">php.net</a>'s documentation pages. In some cases, when there was no consistent<br>
standard on <a href="http://php.net" target="_blank">php.net</a>, we even asked them for the proper standard and to fix<br>
their docs.<br>
<br>
I'm not quite sure how they can ignore an architecture like Drupal. I'm not<br>
sure whether I know of a PHP framework/CMS that is NOT extensible and<br>
doesn't support extensions to be placed in various locations, and therefore<br>
wouldn't support this strict filepath based namespacing.<br>
<br>
Thanks for staying involved, Crell!<br>
<br>
sun<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 11 Nov 2009 13:57:51 -0700<br>
From: Cameron Eagans <<a href="mailto:cweagans@gmail.com">cweagans@gmail.com</a>><br>
Subject: Re: [development] PHP Standards Group<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID:<br>
<<a href="mailto:b83a0f600911111257x725d71abpbddb5f20c4f6460c@mail.gmail.com">b83a0f600911111257x725d71abpbddb5f20c4f6460c@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I'm going to go out on a limb and say that any framework that anybody would<br>
really care about is extensible and will support extensions in different<br>
locations. And +1 to the thing about adopting standards wherever feasible.<br>
-----<br>
Cameron Eagans<br>
Owner, Black Storms Studios, LLC<br>
<a href="http://www.blackstormsstudios.com" target="_blank">http://www.blackstormsstudios.com</a><br>
<br>
<br>
On Wed, Nov 11, 2009 at 12:37 PM, Daniel F. Kudwien<br>
<<a href="mailto:news@unleashedmind.com">news@unleashedmind.com</a>>wrote:<br>
<br>
> > "we'll be involved in developing such standards and will<br>
> > adopt them wherever feasible, but we do not commit to<br>
> > following all standards if they are incompatible with<br>
> > Drupal's basic architecture."<br>
> ><br>
> > --Larry Garfield<br>
><br>
> +1 Yes, that makes sense. I think it is what we (sometimes silently) did<br>
> anyway. Some of our standards are self-made (for good reason), but there<br>
> are also a couple that were directly derived from example code snippets on<br>
> <a href="http://php.net" target="_blank">php.net</a>'s documentation pages. In some cases, when there was no<br>
> consistent<br>
> standard on <a href="http://php.net" target="_blank">php.net</a>, we even asked them for the proper standard and to fix<br>
> their docs.<br>
><br>
> I'm not quite sure how they can ignore an architecture like Drupal. I'm<br>
> not<br>
> sure whether I know of a PHP framework/CMS that is NOT extensible and<br>
> doesn't support extensions to be placed in various locations, and therefore<br>
> wouldn't support this strict filepath based namespacing.<br>
><br>
> Thanks for staying involved, Crell!<br>
><br>
> sun<br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.drupal.org/pipermail/development/attachments/20091111/8db82c12/attachment-0001.html" target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091111/8db82c12/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 11 Nov 2009 16:19:03 -0500<br>
From: Jeff Greenberg <<a href="mailto:jeff@ayendesigns.com">jeff@ayendesigns.com</a>><br>
Subject: Re: [development] PHP Standards Group<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a href="mailto:4AFB2A47.40001@ayendesigns.com">4AFB2A47.40001@ayendesigns.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
+1 to Larry for the reasons already enumerated.<br>
<br>
The only thing I have to add that may be of value, is an observation of<br>
the past. The appearance of a standard that does not appear to (a) be in<br>
the best interests of the product, (b) best interests of the user,<br>
and/or (c) make much sense other than a standard for standard's sake, is<br>
a phenomenon that happens from time to time.<br>
<br>
It makes every bit of sense in these cases to tread lightly, and not<br>
employ the standards that fall under (a) and (b), perhaps even (c),<br>
especially if (c) looks like it could cause unwanted limitations ongoing.<br>
<br>
The warning is I've seen this done with, for example, HP clinging to<br>
HP-UX when Linux was starting to get loaded on servers, IBM with DB2, QB<br>
with XML, and I could go on for a long time. Granted, some examples are<br>
come down to Open or Proprietary, but the rationale for being one<br>
instead of the other was the same (with the addition of (d) Revenue),<br>
and usually came down to a belief that the standard would probably go<br>
nowhere, and wherever it *did* go would be outweighed by (a) and (b).<br>
<br>
The result, though, in many cases was that by the time clients started<br>
griping about the solution not meeting a standard, and by the time it<br>
became a problem for the company's marketing that could not be ignored,<br>
they were way behind the curve in terms of meeting the standard,<br>
sometimes with disastrous results (for the original product and people<br>
who had lived it, at least).<br>
<br>
So, my advice is to look at whatever standard emerges with two<br>
corrective lenses, one for near-sightedness, and one for far-, but<br>
definitely not with tunnel vision...not that you would :-)<br>
<br>
Jeff<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 11 Nov 2009 18:43:49 -0800<br>
From: David Metzler <<a href="mailto:metzlerd@metzlerd.com">metzlerd@metzlerd.com</a>><br>
Subject: Re: [development] PHP Standards Group<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID: <<a href="mailto:8BBFF315-59F2-4283-8917-332850EBF6DB@metzlerd.com">8BBFF315-59F2-4283-8917-332850EBF6DB@metzlerd.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I agree whole heartedly with you on this.<br>
<br>
FYI: The document appears to have been removed. I'd be interested<br>
in reading it if it ever appears again.<br>
<br>
Dave<br>
On Nov 11, 2009, at 9:19 AM, <a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a> wrote:<br>
<br>
> It seems to cover fewer things than they used to, but the one it<br>
> does cover is the one that is least Drupal-friendly; specifically<br>
> it mandates a direct Java-style mapping from namespace and class<br>
> name to file name. I dislike that and find it fundamentally Drupal-<br>
> incompatible, but we'll see.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.drupal.org/pipermail/development/attachments/20091111/24793df0/attachment-0001.html" target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091111/24793df0/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 11 Nov 2009 21:08:31 -0700<br>
From: Randy Fay <<a href="mailto:randy@randyfay.com">randy@randyfay.com</a>><br>
Subject: [development] Doing hook_update_N() when module is installed<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID:<br>
<<a href="mailto:15c957090911112008m7bce90bg56e6733e4291170e@mail.gmail.com">15c957090911112008m7bce90bg56e6733e4291170e@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I'm doing a module for infrastructure which is all about applying<br>
configuration updates, and it does only configuration, nothing else.<br>
<br>
I'd like to create hook_update_N() functions, but I'd also like all of them<br>
to be run when the module is installed.<br>
<br>
Is there any "correct" way to do this? Many modules implement the<br>
functionality in both hook_install and hook_update_N, and that's fine for<br>
database-only issues, which is what these were built around (like schema<br>
changes). But it doesnt' really make sense for site config changes.<br>
<br>
Obviously, I can run the hook functions from hook_install(), in direct or<br>
indirect ways.<br>
<br>
Suggestions?<br>
<br>
Thanks,<br>
-Randy<br>
<br>
--<br>
Randy Fay<br>
Drupal Development, troubleshooting, and debugging<br>
<a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>
+1 970.462.7450<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.drupal.org/pipermail/development/attachments/20091111/969d2f57/attachment-0001.html" target="_blank">http://lists.drupal.org/pipermail/development/attachments/20091111/969d2f57/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Thu, 12 Nov 2009 10:35:38 +0100<br>
From: Ken Rickard <<a href="mailto:agentrickard@gmail.com">agentrickard@gmail.com</a>><br>
Subject: Re: [development] Doing hook_update_N() when module is<br>
installed<br>
To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
Message-ID:<br>
<<a href="mailto:25b45da00911120135i42e99d29h5f7d8ffbbe35493c@mail.gmail.com">25b45da00911120135i42e99d29h5f7d8ffbbe35493c@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
To run an action the first time a module is installed, use<br>
hook_enable() in D5 or D6.<br>
<br>
- Ken<br>
<br>
On Thu, Nov 12, 2009 at 5:08 AM, Randy Fay <<a href="mailto:randy@randyfay.com">randy@randyfay.com</a>> wrote:<br>
> I'm doing a module for infrastructure which is all about applying<br>
> configuration updates, and it does only configuration, nothing else.<br>
> I'd like to create hook_update_N() functions, but I'd also like all of them<br>
> to be run when the module is installed.<br>
> Is there any "correct" way to do this? ?Many modules implement the<br>
> functionality in both hook_install and hook_update_N, and that's fine for<br>
> database-only issues, which is what these were built around (like schema<br>
> changes). But it doesnt' really make sense for site config changes.<br>
> Obviously, I can run the hook functions from hook_install(), in direct or<br>
> indirect ways.<br>
> Suggestions?<br>
> Thanks,<br>
> -Randy<br>
> --<br>
> Randy Fay<br>
> Drupal Development, troubleshooting, and debugging<br>
> <a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>
> +1 ?970.462.7450<br>
><br>
><br>
<br>
<br>
<br>
--<br>
Ken Rickard<br>
<a href="mailto:agentrickard@gmail.com">agentrickard@gmail.com</a><br>
<a href="http://ken.therickards.com" target="_blank">http://ken.therickards.com</a><br>
<br>
<br>
------------------------------<br>
<font color="#888888"><br>
--<br>
[ Drupal development list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
End of development Digest, Vol 83, Issue 20<br>
*******************************************<br>
</font></blockquote></div><br>