This is a good question.

I'm putting on my thinking cap: In my book on Views 1, I've got a "Views worksheet" that might be helpful. Basically it's a one-sheet summary of Views options. Still a manual approach, but might make it easier to track what's going on in each view.

http://www.packtpub.com/drupal-5-views-recipes/book

(This D5 book will be available in a few weeks. We'll also do one for Views 2, but it'll likely be available next year. Have to write it first.)

If folks have automated Views upgrade approaches, I'm interested.

Margie

On Wed, Apr 8, 2009 at 9:13 AM, Shai Gluskin shai@content2zero.com 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/ ]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

Basically what I do during my upgrades is that I convert all the views and set them up for the new D6 environment. Then once I am happy with them I turn them into default views, and this will mean that when the site is converted the views will be there ready to go.

Default views are quite easy to create as you can just use views export to create all the code.

Gordon.

On 08/04/2009, at 11:13 PM, 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/ ]