We have been manually upgrading views between D5 and D6. The architecture of Views 2 allows for more efficiency in how you set up views -- for example, set up a default view, and then generate multiple blocks/pages off that view -- this is possible in D6, where it wasn't in D5. Recreating the views manually allows us to make sure that the D6 upgrade actually leverages the advantages D6 brings.
Cheers,
Bill
Shai Gluskin wrote:
I've upgraded about 3 sites from D5 to D6. In each case I had to recreate the views. I didn't troubleshoot the issue because there were so few that it was no biggy to just re-do them. But I'm gearing up to upgrade a site that has a lot of views.
Is there a trick or tricks to coaxing the Views upgrade path from D5 to D6 to actually work? What has your experience been?
Shai Gluskin
On Apr 8, 2009, at 3:52 AM, Roberto Gorjão roberto@asenseofdesign.com wrote:
I found it, finally. Views -> Add fields -> node:link. Views is in deed a great module.
Roberto
Roberto Gorjão wrote:
Hello,
I have a block on the front page of a website which is populated by a list created by Views. Each node of the list is composed by several fields create in CCK. I would like to have at the bottom of each node a link to the node page.
I know that I could, using Views, link one of those fields to the node page but none of them is really convenient for that purpose. So, I just would like to have a static piece of text wrapped by an <a> tag with its href attribute pointing to the node... The problem is that it seems impossible to theme the block using a variable like $node_url, which was my original idea... It just doesn't work. Could anyone point me the right direction on this one?
Thanks!
Roberto
[ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]
-- [ Drupal support list | http://lists.drupal.org/ ]