Need help with subtitle field...getting it in the right place
Hi everyone,
Firstly, I want you to know that I am trying my VERY best to work out things on my own before coming here! :) Only when I have exhausted all resources and am ready to pull my hair out, do I come here to harass you with my questions;)
Okay... here is what I am trying to do...I want to be able to have subtitles to stories that:
1. Appear ONLY in the full node and not in the teaser and
2. Appear in the right place, directly under the main title (not under the "submitted by..." or anything else.)
And so, I first created the field using CCK...but after many struggling futile attempts with playing around with the weights in the CCK module seettings, I couldn't get it to move above "submitted by":(
Next, I put together a "node.tpl.php" (with the help of borrowing one from the Zen theme and making slight modifications after many searches here on the Drupal site and in Google) and further below is the code for that:
Now, unless I go into the "Display fields" in CCK and choose to hide all instances of the subtitle, it will appear TWICE in the full node.
So making it hidden seems to solve the problem for the full nodes but now it also appears in the teasers (because of the way I have node.tpl.php set up).
I really don't know what direction to go in from here to make it work the way that I want:( Can you help?
Thanks a lot in advance...very much appreciated!,
Christine
<div class="node <?php print $node_classes; ?>" id="node-<?php print $node->nid; ?>"><div class="node-inner">
<?php if ($page == 0): ?>
<h2 class="title">
<a href="<?php print $node_url; ?>"><?php print $title; ?></a>
</h2>
<?php endif; ?>
<?php if ($field_subtitle): ?>
<div class="field-field-subtitle">
<?php
print $node->field_subtitle[0]['value']
?>
</div>
<?php endif; ?>
<?php if ($unpublished): ?>
<div class="unpublished"><?php print t('Unpublished'); ?></div>
<?php endif; ?>
<?php if ($picture) print $picture; ?>
<?php if ($submitted): ?>
<div class="submitted">
<?php print $submitted; ?>
</div>
<?php endif; ?>
<?php if (count($taxonomy)): ?>
<div class="taxonomy"><?php print t(' in ') . $terms; ?></div>
<?php endif; ?>
<div class="content">
<?php print $content; ?>
</div>
<?php if ($links): ?>
<div class="links">
<?php print $links; ?>
</div>
<?php endif; ?>
</div></div> <!-- /node-inner, /node -->
I forgot to include the URL so you can take a look...
http://74.220.215.68/~leemagaz/article
Logic flow
Christine,
If you're looking at a page ( a single node) and not a view (a list of multiple nodes), you do NOT print the headline, but you DO print the subhed in node.tpl.php. (The headline is printed by the page template.)
If you're looking at a view and not a simple page, you DO print the headline in node.tpl.php, but (according to your spec) you do NOT print the subhed.
So:
<?php if ($page == 0): ?><!-- this is a list or view, not a single node -->
<h2 class="title">
<a href="<?php print $node_url; ?>"><?php print $title; ?></a>
</h2>
<!-- now you want to reverse the logic, so change "endif" to "else" -->
<?php else: ?>
<?php if ($field_subtitle): ?>
<div class="field-field-subtitle">
<?php print $node->field_subtitle[0]['value']; ?>
</div>
<?php endif; ?> <!-- end of the code dependent on existence of the subtitle -->
<?php endif; ?> <!-- the is the end of the whole $page scenario. including the "else" -->
I haven't tested this but I think it's right. Personally I prefer to use braces "{ ... }" rather than the label-colon "if ...: ... else: " notation.
...
woops wrong spot... see other post
Worked perfectly!
Yelvington, thank you!
This worked perfectly and helped to clarify things further! I have played around with this in http://74.220.215.68/~leemagaz/columns if you wanted to take a look at all:)
Have a wonderful day!
Christine
Hi Christine
Hi Christine -
I'm pretty sure I know what you're asking for. Hang tight and I'll give ya a nice "David solution" (tm) ... :)
Edit: I'm writing it as a full article this time so I can add it straight to Drupal docs :D
-- David
absolutecross.com
You're a very welcome sight Drupal superhero:)
David, Thank you for coming to my rescue yet again!!
I really like those "David solutions" as they always really fit the bill and I can easily understand them:)
I will check back in the next couple of days then....have a wonderful Sunday evening:)
Christine
P.S. (If and ONLY if you have the time, can you take a sneak peek at my other post: http://drupal.org/node/290672 and let me know if you have a solution for it...it is regarding user images with posts of specific content type & not all posts.... I would like to know if there is an alternative other than using the contemplate module as was suggested)
No prob... I've been meaning
No prob... I've been meaning to write an article about this since the question gets asked a lot, and I've typed various answers in IRC, AIM, etc and always wished I had a solid A-Z lesson to just point people to haha :)
-- David
absolutecross.com
Article about 1/2 to 2/3 done...
Christine -
It's not complete yet, but if you'd like to have a look at what's done thus far, feel free: http://www.davidnewkerk.com/book/18
There's still a number of additional pages to write, but this should get you up and running with your CCK type, and part way through setting up the Views you need. Remaining is finishing the Views part of the lesson and writing the theming part.
-- David
absolutecross.com
That looks WONDERFUL!
David,
I took a quick glance at your documentation... that looks WONDERFUL! Really excellent documentation! Thank you for pointing me to it... I am going to dive into it over the next couple of days:)
Christine
Update
Just letting you know that I completed the "Views" section of the guide (which has turned out to be a rather nifty Views 2 tutorial by the way): http://www.davidnewkerk.com/book/21
All that remains to be written is a short section on enabling the Block display (optional), and the section on theming the Page: Articles View, and the node-articles.tpl.php file.
If you happen to be going through the guide, feel free to let me know about any areas that are unclear so that I can perfect them, any mistakes or typos if you notice them, etc.
-- David
absolutecross.com
Thanks David!!
WOW...now that is a TREMENDOUS & very valuable resource for all of us Drupalees:) It is WONDERFUL the way you have put all of that together, I am telling you! (I even like the musical note favicon too;)
What I am going to do is start with your tut on CCK and then go into the views, from start to finish, and will set up my second content type "columns" & the views for the "columns" using your methods.
Or actually... I may just obliterate my article content type, and it's corresponding view and start fresh with everything I think:) What I currently have there was just gobbledeegook as I was testing everything;)
(Emmm....ahem...can I ask you one more thing? Yikes. I know how busy you are....so again, this is ONLY if and when you have the time. I promise...It is a VERY simple issue regarding CSS for the avatars....over here at http://drupal.org/node/291109
Just thought I'd ask you in case anything immediately came to mind. I can get by the way it is now but wanted a better solution if possible.... I know you are so much more of a pro at all of this than I am. No rush!! I am sure you must be starting to feel like "Davecyclopaedia," no doubt ;)
Have a wonderful Tuesday!
Christine
Results
Okay David...I went through everything from start to finish exactly as specified in your instructions!:)
Before I do anything further... I have left the results as is so you can take a look:)
Here are my notes/questions:
****FIRST SEE UPDATE BELOW. I CHANGED THE URL TO "http://74.220.215.68/~leemagaz/article" instead****
1. When I go to http://74.220.215.68/~leemagaz/articles it correctly goes to the articles page with the teasers (I have to restyle this somehow so it looks like it did earlier, with the teasers similar in appearance to the teaser on the front page, if you scroll down to bottom.... with the option of having the user avatars on the teasers). If I click on one of the teasers and it takes me to the actual article...why does the URL then change to:
http://74.220.215.68/~leemagaz/article/whateverstory
instead of
http://74.220.215.68/~leemagaz/articles/whateverstory
This forces me to add CSS styles for both section_article and section_articles:((
I remember now when I was doing my own testing a couple of days ago I ran into this issue and could only fix it by naming everything either "article" or "articles"...by this I mean naming both the views page path AND the content type "article" or both "articles". Does this make sense?
(Mental wheels grinding away here. Hmmm....I think that either I should change the Views path to "article" instead of "articles" or I should have named the "machine name" of the Article content type "articles" instead of "article" and I think that would fix the issue. But that means I will have to dump the content type and start over:( Your thoughts? Knowing me, I could have messed somewhere else but I was so careful to go through this step by step...)
***UPDATE*** Okay, I just changed the Views path to "article" instead of "articles" and all is well:)
2. Back to the issue with the subtitle.
Take a look at http://74.220.215.68/~leemagaz/article/incredible-article-title
The first line "This is the absolutely incredible article subtitle " is the subtitle. (Please note that this is currently unstyled!! Only once I work this out will I finalize the styles:) How can I get that to appear above the "submitted by" line and directly below the main title? Do I need to write a custom view for this as well? The only way I have been able to get this to work is by modifying the node.tpl.php and then hiding the subtitle field in the article content type. I certainly don't mind going the node.tpl.php approach:)
3. When adding the text content for the teaser as I create an article.... I have given it a limit of 300 characters. Is there a way somehow that I can set it so that it automatically just cuts off at the 300 character mark instead of it just notifying me that I have exceeded the 300 character limit? This way I have to keep manually removing an estimated number of characters until I am under 300. This is not a huge deal as I can just remove the limit and always input an estimated number of text characters as I do now with the original static website:)
4. What would you suggest is the best way to set things up so that I can have the option of inserting user avatars with the posts (teasers and full posts)? Should I use the contemplate module for this or should I set this up with modifying the teaser View somehow?
And...ding ding ding...
The LAST question for the evening:
5. For styling purposes, is there a way to group the fields on the Articles teaser page "http://74.220.215.68/~leemagaz/article" so that each field is not it's own "island"?.
By this I mean, INSTEAD of:
<TITLE DIV><END TITLE DIV><TIME CREATED DIV><END TIME CREATED DIV>
<TEASER TEXT DIV><END TEASER TEXT DIV>
<TITLE DIV><END TITLE DIV>
<TIME CREATED DIV><END TIME CREATED DIV>
<TEASER TEXT DIV><END TEASER TEXT DIV>
I could have something like:
<TEASER GROUP 1>
<TITLE DIV><END TITLE DIV>
<TIME CREATED DIV><END TIME CREATED DIV>
<TEASER TEXT DIV><END TEASER TEXT DIV>
<END TEASER GROUP 1>
<TEASER GROUP 2>
<TITLE DIV><END TITLE DIV>
<TIME CREATED DIV><END TIME CREATED DIV>
<TEASER TEXT DIV><END TEASER TEXT DIV>
<END TEASER GROUP 2>
Have I boggled your mind yet? I KNOW I have;) (yikes)
Have a wonderful evening!
Christine
Hi Christine - 1. Regarding
Hi Christine -
1. Regarding the odd paths issue, without knowing the details of your setup my initial guess is you probably had pre-exisiting Path aliases for the content type, either manually generated or (hopefully) automatically via Pathauto module. The "node" pages receive their path by means of the Path or Pathauto module, separately from your View which defines its own path without Pathauto. The two are not actually interconnected internally (they only appear seamlessly connected to the site visitors, assuming the path of the View is the same as the "parent" of the node... e.g. consistently "articles" or "article"... the article/ part of the path when you make a new Article node has nothing actually to do with the node... you just set it up that way so those nodes appear connected to their parent listing page, which is the View... this also behaves logically the way a visitor would expect it to, being able to remove the end of the node's path and arrive at the index).
You could create a CCK type named "Article" and with Pathauto give nodes of that type a path of article/title-of-page OR articles/title-of-page (point being, Pathauto's setting determines this).
Since you already likely had pre-existing paths set up for nodes of that CCK type, if your View's path doesn't match, you'd need to clear those old paths first (with Pathauto installed: admin/build/path/delete_bulk) and rebuild them admin/build/path/pathauto (by checking the "Bulk generate aliases..." option within Node, Taxonomy, etc, and submitting). Don't be afraid to delete paths aliases if they are all generated by Pathauto - any aliases Pathauto made it can remake.
2. Regarding your second question... that's exactly what I'll be covering in the theming part of the lesson... and "all shall be revealed" haha :D Your "articles" View (teasers of the content) will be themed exactly the way you want, and the theme of your Article nodes will be under your complete control down to the last HTML tag (well pretty much haha) :)
3. This does work correctly if your field is a single line "Text field"... however I just tested this on a "Text area (multiple rows)" and this type of HTML form field evidently does not support the maxlength element (this is an issue of HTML itself I believe not just Drupal). If you have a single line "Text field" then you would see this in the input form field if you view the source:
maxlength="300". My understanding is that multiple line form fields can only have their length controlled by means of javascript (the way the Maxlength module works... which unfortunately only applies to the Title and Body fields, and is not ported to D6 yet anyhow). It should be possible to either adapt some code from Maxlength module or load in a little snippet of Javascript in your theme to handle this though, so I will look into it. As mentioned in the guide though, I very much prefer "Text field" for this kind of situation, and recommend that if possible. I'll look into the Javascript to work around it though.4. Not sure yet, but I will be sure to address this when I come to that point in the theming section of the lesson.
5. If I'm understanding you correctly, sure... that will be covered in the theming part of the article (Views theming portion).
Thanks for the feedback and questions... hope to have the article done within a few days.
-- David
absolutecross.com
Yet again so many things fall into place in the "mental boggle"
David,
First of all, THANK YOU for all of your patience with my zillion questions. You cannot believe how much I have learned in the past few weeks, thanks to you! Also, to be honest, I am quite glad I had all these issues that I have had (including last night's issues) as it has helped me to understand things even MORE:)
After reading your answers, a LOT more suddenly "clicked into place" and I found myself saying "duh" (to myself) a few times because they certainly took their time to "click"!;) (Prolly my miniscule sleep of late is to blame!)
SO.... here are my replies to your replies, simply for the sake of updating you....no questions this time, can you believe it!!!:)
1. Yes... my settings in the path auto module were to blame! After I had followed another tutorial a couple of weeks back that I found on the web I had plugged
[type]/[title-raw]into the path pattern field for the article paths, under "Node path settings" in the URL aliases, so that this would be the default. Boy, was the noise loud when the penny dropped on THIS one!;) I have now changed that toarticles/[title-raw]as well as changing the path in Views for the articles back to "articles" and all works PERFECTLY now!! Again, had I not had this issue, things would not have been as clear to me as they are now:) It's also great to know about that option to delete path aliases. Had you not told me, I would not have known that.... I am so wary of touching things I know nothing about...which is a good thing too:) It's wonderful knowing that they can be rebuilt too!2. I think you are going to be teaching me about the "Contemplate module" here? :) I installed that and took a look at it... it looks WONDERFUL!!
Also, I experimented with creating a "Columns" content type now and Views for it, along with modifying the "node.tpl.php" (which will affect only the columns at this point in time) using the php code suggested by Yelvington above and that works great too:) I did this for the sake of experimentation right now so at least I know this option is available too as a backup plan (The subtitles appear only in the node itself and not in the view). I want to follow along with the rest of your tutorial in the "theming "part of the lesson for the articles:)
3. If "Text field" will take care of it than I will definitely use that instead as recommended. It's definitely good to know this about the text area though!:) No need to look into the Javascript then:)
4. From everything I have learned... I am thinking the "contemplate" module will take care of this and/or views OR modifying the node.tpl.php. It would be nice to have the option with each individual post of whether to plug in the user avatar but I think that is asking for things to be a whole lot more complicated than they should be. We may decide to have the avatars with all posts as there are regular writers for the articles. The only thing is that when a user does NOT have an avatar (if we want to post general content), then the post has a nasty little square where it is assuming the avatar should be, as in http://74.220.215.68/~leemagaz/articles/really-fantabulous-incredulous-t...
I am just speaking my thoughts aloud here....:)
5. Okay... I shall wait on the theming part of your article:)
David, please take your time with the rest of the article... I mean that! I want you to know that there is definitely no rush on this as I know it is right in the middle of the work week too. You have no idea how much I appreciate all that you have already done!! This has been like a tremendous crash course for me and I wouldd not have learned the incredible amount that I have, had it not been for your incredible patience and very VALUABLE detailed answers & tutorials:)
Have a wonderful Wednesday!!
Christine
Posted this in the wrong place...
Oopsy
I just realized that...
Other than saying how wonderful your tutorials were, I hadn't really commented much on the whole presentation or given feedback as I thought I had done...and so here goes...
The way you presented everything was REALLY excellent. Very very clear explanations indeed! What was ESPECIALLY helpful were the detailed pieces of information you provided for alternative/additional options other than the ones you recommended as you went through the steps, and this was throughout your tutorials. You practically explained what each and every option meant, which was INVALUABLE, especially for someone who had no prior experience of the modules/methods used. By the time I completed the tutorials I definitely felt I had a much clearer, and at the very least, a basic understanding of how everything worked... and I understood the whole purpose for taking this route/using these modules to begin with. I finished with the feeling of "Wow...what incredibly useful & versatile modules those are~! I cannot imagine how any "Drupaleer" could get by without them!" And you're right, that WAS quite the "nifty" Views tutorial:)
The oooonly thing that I feel needs to be included somewhere in all of this is some info about the pathauto module and URL aliases in general... even if you just extract some text from that paragraph you wrote in your reply to my question about the odd paths issue. That reply you wrote for question 1 really cleared things up a lot for me.
That said, I had just wanted to make sure and stop back in just to point out how well presented I thought your tutorials were...especially from someone coming from the other end of the spectrum (a Drupal newbie who is doing the learning by reading all the content you had so meticulously put together...) because I know that must have taken a verrrrrrrry long time to put together:)
Just my 2c:)
Best regards & have a wonderful Thursday!
Christine
Hi Christine - Just wanted
Hi Christine -
Just wanted to update you... I've added a whole new page detailing, as you wisely suggested, the ins and outs of Drupal URL paths/aliases. I also added in info on Custom Breadcrumbs here, as it's a good related spot to introduce them:
http://www.davidnewkerk.com/book/24
Let me know what you think... does it all make sense, any way I can explain more clearly, more succinctly, etc? As usual I've tried to cover every angle and address every question before it needs to be asked, though let me know if it "works" :)
I've also gone through the whole guide and added standardized formatting to make it more clear what is a link, what's a setting to adjust, what's something that needs to be typed, etc. See the "legend" on the main page of the guide.
It's not complete, but the theming portion of the guide is underway: http://www.davidnewkerk.com/book/23
I'm very excited about this guide... can't wait to complete it and share with the Drupal community at large :D I'm currently trying to think of a better name for the guide, since it obviously has surpassed its original intent.
-- David
absolutecross.com
Just took a look...
Hi David,
I popped on here and saw your post so, before turning in, took a (VERY quick) look at the new additions ... you must have read my mind because I had (secretly) been saving a question about the breadcrumbs for later on down the road, if I couldn't find sufficient documentation...And now here it is! :)
I am going to be reading these from top to bottom over the next couple of days. Again, they look excellent ! (and I am very eager to dive in & continue learning:) I can tell you now right off the bat that I know everyone here is going to make a LOT of use of all of this. It is REALLY difficult to hunt down really good sources of information on most of this... and here it is all together in one package too:)
(Very quick mini question about WYSIWYG editors, since you had very briefly mentioned them...
Is there any WYSIWYG editor that you are partial to, or do you prefer doing without them altogether? On my test Drupal installs on my home putr', I had very briefly played around with TinyMCE and FCKeditor. I did have a few issues but haven't yet gotten back to doing any further or troubleshooting. I thought I would just get your input before installing one onto Lee Magazine:)
Have a wonderful Tuesday!
Christine
Thanks
Hi Christine -
Thanks for the comments :) I'm glad this will be helpful for people (it's my goal to knock days, weeks, or even months worth of learning time -aka figuring things out the hard way- for people). I'd like to even create a "series" of guides which, when strung together back to back, essentially take you from square one to the point of a highly custom "core" of a site and knowledge/understanding of all the most important "key" tools/modules needed to put together a Drupal site (of course that's just the beginning, since there's countless other things you can do from that point). I think this guide plus the front page one already are putting a big dent in that goal haha :P Ideally, I'll also include groups of links to related information for each page of the guide when applicable (e.g. helpful Handbook pages, screencasts that relate to the page the reader is looking at, etc).
One change I made tonight was to "group" things into 3 separate sections of the guide, clearly defining which parts cover CCK, Views, and Theming.
WYSIWYG editors...
Well on aguaviva.com and firehousekidz.com I used TinyMCE. Not really because I prefer it or think it's better, but at the time it had the best support for add-on buttons to include (for instance) the Image Assist plugin, and I was most able (at the time) to get it to produce clean HTML. Right now however I have come to dislike it more and more though. Nail in the coffin was when the developers of TinyMCE itself closed their support forums, and still to this day there's not an official version of TinyMCE for Drupal 5 that supports TinyMCE 3 (which is critical for Safari users).... I "think" the dev version works, maybe. It still appears to be the only one that has support for Asset module (which is a promising module)... hopefully support for other editors will be added to Asset.
Right now for "clients" I am using FCKeditor, and after a bit of configuration I like it quite a bit... it produces clean HTML and works in every browser I've tested. It is more difficult to customize the toolbar than TinyMCE since you have to edit a configuration file to do it (not super easy, but not bad once you stare at the way the button-creating code is put together for a few minutes and it becomes clear... you may also have to hard refresh the page or even clear your browser cache to get new button configurations to show up). It supports integration with Image Assist (haven't tested) and IMCE (have tested, works well). I've come to avoid Image module at any cost so I no longer use Image Assist. You may want to toggle FCKeditor's settings to show "only" on the pages/sections you specify, since by default it goes hog-wild and goes on just about every textarea it can find in the Drupal admin area, which can cause problems. The FCKeditor developer is also a Drupal user, so you can bet on its continued availability in future Drupal versions.
For myself, I use BUEditor, which is basically just a toolbar of buttons (and a settings panel that lets you add more custom buttons), that simplify the process of adding HTML to plain textareas. It also has a preview button to instantly toggle the editor area into a rendered preview of the HTML, so you can get a quick look and make sure things are working the way you mean them to. I also use BBCode extension for Firefox, that adds a right click context menu that gives you quick access to wrap selected text with various HTML or BBCode tags (I leave just XHTML mode one, and also define a few custom HTML tags as it permits you to do). I haven't looked into how to include it on Drupal, but the markItUp jQuery plugin has caught my eye (I know it can be done as it's used on webmaster-forums.net). If/when FCKeditor gained enough of my "trust" that it wouldn't garble any of my custom HTML I might add, I'd consider using it myself (the hand-coding and designer sides of me battle it out like the Force versus the Dark side haha).
-- David
absolutecross.com
Thanks again for that very helpful info!
David,
After reading your post, I read a bit more about BUEditor and found a screencast/demo of it at http://www.usingdrupal.com/screencast/screencast-using-bueditor and it looks really good! I think I will give this a try.... it just looks really straightforward, very quick and "clean":) I remember my issues now with FCKEditor now.... I had problems with getting it to work properly with Image Assist ... I put my troubleshooting those issues on hold because I first had other bigger fish to fry and had to attend to those other issues that were more important. Since so many people use it with great success tho', I am sure all that was needed was prolly just a minor tweak on my end:)
I am curious as to why you don't like to use the image module, and avoid it? (Regarding the image assist, I was having a few frustrating issues of my own when using that to insert images. During testing, I had to manually tweak the html quite a bit to get things to work/look exactly the way I wanted as I placed images so, since then, I have been considering whether to upload images the old fashioned way. Just load them into specified image folder/subfolders and link to them as I add content, just adding in the html tags & classes as I would when putting together regular static pages, and then also using Lightbox in addition. It also seemed that doing it the "Image Assist" route took a bunch of extra steps that I could avoid, going the other route. Again, this may have just been a matter of tweaking things on my end.)
Back to your tutorials... David, you will indeed be knocking weeks & MONTHS off users' learning time...because it is just SO hard to find tutorials like yours...and such detailed/explanatory tuts to boot! Take your tuts on Views & CCK for example... I had SUCH a hard time finding sources of info!! Everything I found after doing searches (& searches & searches & searches & searches & searches & ....) were mainly links back to the same couple of tuts & a screencast that were nowhere NEAR as detailed, so I had to do a ton of guesswork on top of it when I initially experimented with those modules.
You know, by the time you are done here, I am sure you will be able to get a new Drupal book published too!:) There is a severe "Drupal drought" out there in the book department and this is something that would REALLY be needed out there, especially because of the way Drupal is becoming as popular as it is, and is so widely used.
(I am curious to know which part of you you consider to be the "Dark side" and which you consider to be the "Force" :) Designer=Force and Hand-coding="Dark side" ? I have a feeling it's the other way around actually...:)
**UPDATE** I LOVE BUEditor, if only I could get it to work properly. I got it going on one test site of mine but cannot get it going on Leemag:( But that's another issue entirely which I'll post on the boards. My question for you is whether you are able to use it with lightbox at all on your own site? (Where one can have just the thumbnail image with the post, that then enlarges into the usual "Lightbox overlay" with the original/larger size image, when clicked upon.) If this is possible and you have done it...then at least I know it can be done and I will do more research into it:)
**UPDATE** Note to self: Perhaps this is the answer for BUEditor/Lightbox here
**FINAL UPDATE** That was not the answer and I REALLY should have this question in a separate thread altogether... so I have gone ahead and done exactly that:)
Christine
WONDERFUL!!
Hi David,
I spent part of the evening going through your guide again... WONDERFUL the way you have updated it!! I picked up a lot of additional "insight" as I went through it again. I really played around with views last night a lot and feel very comfortable with it right now, thanks to all of the additional information you included. (I think back to when I first took a look at it, and the CCK module, and my heart skipped three beats as I wondered how I was going to be able to wade through all of that ... & ever understand it. Your guide changed all of that & made it very simple & easy to understand! And so, yes, it definitely "works" :)
I am so glad you included that about the Custom Breadcrumbs too, I cannot tell you just HOW much that was frustrating me before I modified it for the "Articles" (and columns) as per your instructions:)
It was also VERY GOOD to know about not hitting that "submit" button with the contemplate module. Had you not included that tip, I certainly would have done so in my future playing around with it.
Excellent info about the pathauto too!! Just in case, and only if you thought it was necessary, I wondered if you would like to include a link to this page on potentially "dangerous" pathauto patterns.
Have a wonderful Wednesday!
Christine
Hi Christine - Thought I'd
Hi Christine -
Thought I'd point you to a post I made tonight that may be helpful until I complete the Views theming portion of the guide:
http://drupal.org/node/299406#comment-978324
You'll recognize some of the text comes from an earlier post to you :) Though I've edited and expanded on it to be the basic framework for the Views theming part of the guide (obviously not complete yet, to my exacting standards at least haha). But in case you're waiting on that, this might get you a little further until I get to that part of the guide.
Oh and yes, I'll add a bit to the Path/Pathauto discussion to cover dangerous paths as well as info/link about "raw" paths (since Pathauto clearly wants you to use raw paths, "Use -raw replacements for text to avoid problems with HTML entities." and info, yet it says "warning" next to them... a bit confusing).
-- David
absolutecross.com
[new guide/lesson in progress: Creating a CCK and Views powered Drupal site - feedback welcome]
Thanks David... it was GREAT to find out about that:)
I would have had no idea about the "Theme: Information".... that is really wonderful to know!!
Thanks a lot,
Christine
**UPDATE**
Just thought I'd add an update for anyone who may visit this thread in the future, and in case it would be of any help and interest:)
(I noticed that a lot of people are trying to get to the site via the old links in these threads and those don't work properly, for the most part)
I have finished the new site in Drupal and we are REALLY glad we used Drupal...we love it!!
The new Drupal site is at http://www.lee-magazine.com.
The original (static) one can still be seen at http://www.lee-magazine.com/leemag/index.html
Christine
Love affair?
Is everyone (David etc) having a love affair in this post LOL.
Nice work Christine btw!
Tim
Drupal & Multimedia Developer, SO OUT THERE Music Producer
http://www.TimJones.ca | www.SoOutThere.com