Hello, Victor,
I have not tested the upgrade path, in large part because for our use cases upgrading from D5 to D6 will involve upgrading cck node types, and fields -- and the actual views are predicated on those fields -- so without the fields upgrading cleanly, the views upgrade is a less pressing concern.
I suspect that when we start upgrading from D5 to D6, we'll use update.php for CCK, but not for views, as I'd rather rebuild the views cleanly in D6. Will it take longer? Maybe, but it'll also run more smoothly, and we'll have the peace of mind of knowing that the views are clean.
I'd love to hear from anyone who has embarked on the scripted upgrade from D5 to D6.
Cheers,
Bill
Victor Kane wrote:
Hi Bill,
That sure sounds like good news! I am sort of embarked in the same thing...
Did you test upgrading Views 1 views to Views 2?
Victor
On Mon, Jul 21, 2008 at 1:45 PM, Bill Fitzgerald bill@funnymonkey.com wrote:
Shai Gluskin wrote:
<snip good stuff> As an aside... Drupal 6 is really awesome... but it's having a long ramp
up
time for many good reasons. In general, for someone seeking support, ease
of
use and is a "beginner" - I recommend D5 at this moment in time. Sounds
like
you may be pretty far in and it isn't worth starting over.
Three or four weeks ago I would have agreed with this. However, having spent some quality time recently with Views2, CCK, Date, Calendar, and OG, I'd say that the time of D6 has arrived. These modules have been working incredibly well in the testing we have been doing.
Views2 is phenomenal -- it was pretty amazing in the D5 version, but the D6 version is an amazing leap forward -- and, IMO, easier for a newcomer to use, especially with the Advanced Help module installed.
My .02
Cheers,
Bill
Shai
On Mon, Jul 21, 2008 at 12:03 PM, Steve Hays hays@ohio.edu wrote:
Shai,
Many thanks both for your help and your kindness.
Since you urge me not to knock my head against the wall too long, here's a problem I have probably spent 10 hours on and not produced a reasonable solution to--just a hacked work-around.
I want my students to be able to develop individual blogs. I have developed (via Views in Drupal 6.3) a page that lists all Member Blogs. I have added a blog_name field to the Profiles page, and obviously I would like that name to be linked to the individual blog. The blog's default url is (of course) blogs/$uid. I have constructed a blog_url field in Profile so I can pull it along with the blog_name in Views.
But that makes for an ugly page display: My_Blog http:// etc.
What I would like, of course is to use the $account_blog_url variable in an a href statement so the url address is invisible to the user, but I don't know how to get Views or Profiles to produce such a link.
Any ideas?
Thanks again,
Steve
On Jul 21, 2008, at 11:01 AM, Shai Gluskin wrote:
Steve,
Do NOT feel stupid. We've all been there and continue to be there in many ways.
It's way more efficient in use of the world's resources (which includes your brain power) for you to ask and get quick help -- it took me three minutes to write that email, than for you to bang your head, potentially for hours. People have helped me so many times and I'm sure you will help others -- or already have. No knowledge in Drupal is "comprehensive" -- you don't have to be a "ninja" or anything special to answer a question that you know the answer to.
Regarding your situation. Congratulations on figuring it out.
Indeed, no need to use the Drupal l() function.
Regarding the href-- there are different opinions on this, and sometimes it depends on whether you have a multi-site or not. But my strong preference for any single installation site is for all href's to pages inside the site to be "root relative." All references should start with a forward slash after the first quotes. In this case I would no need to provide any specific page path since it is the default home page. Here is how I would do the href:
<a href="/">
best,
Shai
-- [ Drupal support list | http://lists.drupal.org/ ]
--
Bill Fitzgerald http://funnymonkey.com FunnyMonkey -- Tools for Teachers ph. 503 897 7160
-- [ Drupal support list | http://lists.drupal.org/ ]