4.7.5 (minor) API change, project_issue UI impacted: clear browser cache. ; )
hi folks. if anyone's been playing with core from the very tip of the DRUPAL-4-7 branch, you might have noticed a minor change in the API, regarding how FAPI renders #prefix elements from your form arrays. this can impact the UI of contrib modules, especially if you were trying to use css to modify the appearance of node forms. a) everyone who's messing with #prefix/#suffix around node forms should take a look at this: http://drupal.org/node/105960 b) the project_issue.css and project.css files had to change for 4.7.5 compatibility because of this. i just installed all of this on drupal.org, but you're going to have to clear your browser caches to get the new copy. ;) happy new years, -derek (dww)
I have mostly pages and a few stories. There is no obvious reasons why the ones that are stories are stories so I would like to convert them to pages. Obviously I can do this by pasting the story stuff into a new page. But then all the links will still go to the old story and I would have to find all the links and fix them. I have not seen any way of finding all the links to a particular node. What woud happen if I just went into PHPMyAdmin and changed the type field from story to page? Would this break anything?
Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table. So, you can execute this SQL (do a dump first): UPDATE node SET type = 'page' WHERE type = 'story'; On 1/1/07, Walt Daniels <wdlists@optonline.net> wrote:
I have mostly pages and a few stories. There is no obvious reasons why the ones that are stories are stories so I would like to convert them to pages. Obviously I can do this by pasting the story stuff into a new page. But then all the links will still go to the old story and I would have to find all the links and fix them. I have not seen any way of finding all the links to a particular node.
What woud happen if I just went into PHPMyAdmin and changed the type field from story to page? Would this break anything?
Thanks, I did read the code in both story.module and page.module and they are quite similar other than the help text and names of variables story vs page. However page has some additional code in hook_form dealing with logs of changes which looks useful. _____ From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Khalid B Sent: Monday, January 01, 2007 9:17 PM To: development@drupal.org Subject: Re: [development] Converting stories to pages Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table. So, you can execute this SQL (do a dump first): UPDATE node SET type = 'page' WHERE type = 'story'; On 1/1/07, Walt Daniels <wdlists@optonline.net> wrote: I have mostly pages and a few stories. There is no obvious reasons why the ones that are stories are stories so I would like to convert them to pages. Obviously I can do this by pasting the story stuff into a new page. But then all the links will still go to the old story and I would have to find all the links and fix them. I have not seen any way of finding all the links to a particular node. What woud happen if I just went into PHPMyAdmin and changed the type field from story to page? Would this break anything?
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement. Walt Daniels wrote:
Thanks, I did read the code in both story.module and page.module and they are quite similar other than the help text and names of variables story vs page. However page has some additional code in hook_form dealing with logs of changes which looks useful.
------------------------------------------------------------------------ *From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *Khalid B *Sent:* Monday, January 01, 2007 9:17 PM *To:* development@drupal.org *Subject:* Re: [development] Converting stories to pages
Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table.
So, you can execute this SQL (do a dump first):
UPDATE node SET type = 'page' WHERE type = 'story';
On 1/1/07, *Walt Daniels* <wdlists@optonline.net <mailto:wdlists@optonline.net>> wrote:
I have mostly pages and a few stories. There is no obvious reasons why the ones that are stories are stories so I would like to convert them to pages. Obviously I can do this by pasting the story stuff into a new page. But then all the links will still go to the old story and I would have to find all the links and fix them. I have not seen any way of finding all the links to a particular node.
What woud happen if I just went into PHPMyAdmin and changed the type field from story to page? Would this break anything?
Well, for 4.7.x page and story nodes, it's easy to implement. How easy would it be for Drupal 5 nodes, where every node is essentially a CCK node? Then add in actual CCK fields? Now it gets quite complicated indeed, unless you're OK with random data loss along the way. On Monday 01 January 2007 10:13 pm, Chris Kennedy wrote:
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement.
Walt Daniels wrote:
Thanks, I did read the code in both story.module and page.module and they are quite similar other than the help text and names of variables story vs page. However page has some additional code in hook_form dealing with logs of changes which looks useful.
------------------------------------------------------------------------ *From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *Khalid B *Sent:* Monday, January 01, 2007 9:17 PM *To:* development@drupal.org *Subject:* Re: [development] Converting stories to pages
Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table.
So, you can execute this SQL (do a dump first):
UPDATE node SET type = 'page' WHERE type = 'story';
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
I don't think this is worth of a core feature. The need for this is not very often, and if you are using anything other than 4.7 basic types (e.g. CCK for 4.7, or 5.0 onwards), then all bets are off. On 1/1/07, Larry Garfield <larry@garfieldtech.com> wrote:
Well, for 4.7.x page and story nodes, it's easy to implement. How easy would it be for Drupal 5 nodes, where every node is essentially a CCK node? Then add in actual CCK fields? Now it gets quite complicated indeed, unless you're OK with random data loss along the way.
On Monday 01 January 2007 10:13 pm, Chris Kennedy wrote:
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement.
Walt Daniels wrote:
Thanks, I did read the code in both story.module and page.module and they are quite similar other than the help text and names of variables story vs page. However page has some additional code in hook_form dealing with logs of changes which looks useful.
*From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *Khalid B *Sent:* Monday, January 01, 2007 9:17 PM *To:* development@drupal.org *Subject:* Re: [development] Converting stories to pages
Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table.
So, you can execute this SQL (do a dump first):
UPDATE node SET type = 'page' WHERE type = 'story';
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012
"If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
I agree not worth a core feature. In my case it is only 5 nodes that got "typed" wrong as stories. A quick cheap fix is fine. In a CCK world I can imagine types that have identical fields but are distinguished some other way such as have different themes. _____ From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Khalid B Sent: Monday, January 01, 2007 11:46 PM To: development@drupal.org Subject: Re: [development] Converting stories to pages I don't think this is worth of a core feature. The need for this is not very often, and if you are using anything other than 4.7 basic types (e.g. CCK for 4.7, or 5.0 onwards), then all bets are off. On 1/1/07, Larry Garfield <larry@garfieldtech.com> wrote: Well, for 4.7.x page and story nodes, it's easy to implement. How easy would it be for Drupal 5 nodes, where every node is essentially a CCK node? Then add in actual CCK fields? Now it gets quite complicated indeed, unless you're OK with random data loss along the way. On Monday 01 January 2007 10:13 pm, Chris Kennedy wrote:
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement.
Walt Daniels wrote:
Thanks, I did read the code in both story.module and page.module and they are quite similar other than the help text and names of variables story vs page. However page has some additional code in hook_form dealing with logs of changes which looks useful.
------------------------------------------------------------------------ *From:* development-bounces@drupal.org [mailto:development-bounces@drupal.org] *On Behalf Of *Khalid B *Sent:* Monday, January 01, 2007 9:17 PM *To:* development@drupal.org *Subject:* Re: [development] Converting stories to pages
Changing it in PHPMyAdmin should be a safe bet, since story and page have the same identical fields, and stored in the node table.
So, you can execute this SQL (do a dump first):
UPDATE node SET type = 'page' WHERE type = 'story';
-- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson
Op dinsdag 2 januari 2007 05:13, schreef Chris Kennedy:
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement.
Please search first. There is at least one issue (I participated in it, hence I know, but cannot find it anymore). Read up on the problems, and notice the reason why its not there yet (in short: not all nodes are title+teaser+body) Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
Quoting Bèr Kessels <ber@webschuur.com>:
Op dinsdag 2 januari 2007 05:13, schreef Chris Kennedy:
You should also submit a feature request for Drupal to have an interface for this. It would be handy and easy to implement.
Please search first. There is at least one issue (I participated in it, hence I know, but cannot find it anymore). Read up on the problems, and notice the reason why its not there yet (in short: not all nodes are title+teaser+body)
This thread reminds me of a recent post I made "Page vs Story - Again", I'm sure you all remember. I still contend that Story should be off on a new install to prevent the newbie not understanding the difference from needing to do a conversion in the first place. Statements were made that it had to do with workflow but a newbie doesn't realize how Drupal workflow works upon start. And worse, story isn't even listed in the modules for V5 to be turned on or off even though the node type can be deleted. Ok, I know about the dynamic "Content Types" and I understand the reasoning behind it and the fact that modules need to create a content type but upon installation there isn't an example in V5 of a module that creates a content type. IMO, Story needs to be a module inactive by default that users can activate once they learn what it can do for them. Earnie
On 1/2/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
This thread reminds me of a recent post I made "Page vs Story - Again", I'm sure you all remember. I still contend that Story should be off on a new install to prevent the newbie not understanding the difference from needing to do a conversion in the first place. Statements were made that it had to do with workflow but a newbie doesn't realize how Drupal workflow works upon start.
But they will, with documentation and differing workflow options. Page is not promoted, has comments disabled, and has revisions turned on by default. Story is promoted to the front page, has comments turned on, and no revisions.
And worse, story isn't even listed in the modules for V5 to be turned on or off even though the node type can be deleted. Ok, I know about the dynamic "Content Types" and I understand the reasoning behind it and the fact that modules need to create a content type but upon installation there isn't an example in V5 of a module that creates a content type.
Content types are used to describe any module which creates new node types. Whether CCK-like story or page. Blog module "creates" a content type on installation.
IMO, Story needs to be a module inactive by default that users can activate once they learn what it can do for them.
Earnie: I have seen zero comments from you in the threads that I repeatedly pointed to: http://drupal.org/node/104763 Story is NOT a module any longer -- in Drupal 5, we are in a transition phase with CCK-like functionality in core. We've streamlined the code that was almost a complete duplicate between Page and Story and added more flexibility along with an upgrade path from 4.7. in Drupal 6, the removal of even more module node types is possible -- e.g. blog and book are candidates here that have long been talked about, and folks are already working on an outline module that does book functionality. Hope that helps. Use issues and patches if you want to help enact change. Thanks, -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com
Quoting Boris Mann <boris@bryght.com>:
On 1/2/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
This thread reminds me of a recent post I made "Page vs Story - Again", I'm sure you all remember. I still contend that Story should be off on a new install to prevent the newbie not understanding the difference from needing to do a conversion in the first place. Statements were made that it had to do with workflow but a newbie doesn't realize how Drupal workflow works upon start.
But they will, with documentation and differing workflow options. Page is not promoted, has comments disabled, and has revisions turned on by default. Story is promoted to the front page, has comments turned on, and no revisions.
I am cool with that, I understand it all now; but it took me trial, error and postings to get it. Where are the UI and workflow changes being documented? E.G.: Where can I find in the documentation the explanation for the removal of the Moderation Queue workflow?
And worse, story isn't even listed in the modules for V5 to be turned on or off even though the node type can be deleted. Ok, I know about the dynamic "Content Types" and I understand the reasoning behind it and the fact that modules need to create a content type but upon installation there isn't an example in V5 of a module that creates a content type.
Content types are used to describe any module which creates new node types. Whether CCK-like story or page. Blog module "creates" a content type on installation.
Duh.
IMO, Story needs to be a module inactive by default that users can activate once they learn what it can do for them.
Earnie: I have seen zero comments from you in the threads that I repeatedly pointed to: http://drupal.org/node/104763
Subscribed now. There is so much activity from Drupal that it is hard to keep track of unless I actually subscribe and I can find it in "My Issues".
Story is NOT a module any longer -- in Drupal 5,
I am aware of that fact. Both Page and Story were modules in 4.7.x and their promotion to default profile nodes in 5.0 is going to cause some confusion.
we are in a transition phase with CCK-like functionality in core.
I don't know that I can appreciate the difference being as new to Drupal as I am but I know that I liked the functionality CCK provided. I am sure that this is a step in the correct direction.
We've streamlined the code that was almost a complete duplicate between Page and Story and added more flexibility along with an upgrade path from 4.7. in Drupal 6, the removal of even more module node types is possible -- e.g. blog and book are candidates here that have long been talked about, and folks are already working on an outline module that does book functionality.
I appreciate streamlining and flexibility and thank those that have been involved for it; hopefully I find some time to provide some of that streamlining and flexibility. I suppose that _my_ issue is I quickly went from 4.7 to HEAD and didn't realize the amount of work that had been accomplished since. There are a lot of good changes that have taken place.
Hope that helps. Use issues and patches if you want to help enact change. Thanks,
Using the issues and patches online forum is like teaching an old dog new tricks. Besides, I responded to an email. :) Earnie
participants (8)
-
Boris Mann -
Bèr Kessels -
Chris Kennedy -
Derek Wright -
Earnie Boyd -
Khalid B -
Larry Garfield -
Walt Daniels