answered question

I thought there was a simple setting to handle this, but couldn't recall it. Over on the Drupal.org forums, helpful soul ambientdrup set me straight: the solution is as quick as heading to the Error Reporting settings at admin/settings/error-reporting, and setting errors to write to the log only, not both screen and log. The screen messages are helpful while you're developing a site, but once you launch, it's a good idea to turn them off.

And that's it. My thanks to ambientdrup!

Yes, I was fundamentally mistaken in my understanding of what I need to do to have a Views-generated image trigger Lightbox.

Re-reading the Lightbox2 settings more carefully, I see the key phrase "Choose how URLs for [such-and-such] images will be automatically handled" repeated for many settings.

Ah, that may be what I was skipping over. Perhaps Lightbox2 is looking for URLs, not certain classes, attached to the images. Going back to the Views settings for my random image block, I found the desired setting under the Fields section, where I had specified "Image: Image" as the field to appear in the View. The settings for that field include the option "Link this field to its node". I had originally left this unchecked, as I don't want clicks on images taking users to a page built on the image node. But, as I soon confirmed, that's not a worry; with a link URL in place on the images, Lightbox2 intercepts those links and performs its magic, opening a big floating image on the same page. Boom!

Now, what about inline images in my general nodes, the ones embedded helter-skelter amidst node text via my WYSIWYG text editor (TinyMCE and IMCE, if you must know)? I was getting no Lightbox2 click love there either. "Ah", I brilliantly surmised after enough tequila, "Perhaps you want a URL there as well, Lightbox2?" Ever so gently, I adorned my inline image with – for lack of a better idea – a link to its actual location in the file system (files/image.jpg or whatever).

"Now you understand me", breathed Lightbox2, and graced my inline with that old popup hoodoo. She/he/it have been like this (crosses fingers) ever since. 

I don't know that the above is the way to best work Lightbox2 into a site, but as a quick solution to what I was looking for, it did the trick for me.

Once again, the forums to the rescue. Here's the thread that helped:

http://drupal.org/node/134505

And the comment with the solution that worked for me:

http://drupal.org/node/134505#comment-219661

I went to phpMyAdmin, called up my site database, and ran the indicated SQL query. Shazam, things worked!

I'll have to leave explanation to the pros; this is the kind of wizardry that still rings esoteric to my ears. But it did the trick, and I am grateful to solution poster briandelicata, as well as everyone posting in the thread. Great stuff!

(Oh, and one note: Before playing with your database per this solution, be sure to BACK UP THE DATABASE!)

More notes 

Here's a claim that the taxonomy_access module can cause the problem too: http://drupal.org/node/239951 

I'll answer this question as quickly as I ask it – because I just tested it out while moving Drupally questions of various breed into a single node type on this site, the node type called "Drupal Questions" I created for my Question Bank. (It's a nice CCK-created node type with fields for the question, for the answer if available, and for a related URL.)

I had an old blog entry on a certain Drupal puzzle, and thought that node should be reworked into a Drupal Question. I was prepared to simply copy its content into a brand new node. But lo, that blog entry had a couple of comments, and I'd hate to lose those. How would I also move the comments from the old node to the new node I'd be creating? I dunno.

Hmm, a better idea: instead of making a new node, how about transforming the old blog entry node into a new type? I seemed to recall a module claiming that transfigurational wherewithal...

And here it is: Nodetype. http://drupal.org/project/nodetype

I downloaded the module and, before touching anything else, backed up my site database! That done, I installed Nodetype. It offers no admin options, and only shows up when you edit a node: you see a simple drop-down list of node types into which you can change the current node (complete with nice warning to only change the node type if you "know what you are doing"!)

In my case, I selected my custom node type "Drupal Questions" from the list. Doing a Preview of the node showed no changes, but hitting Submit put the change into effect. It worked great, and – the thing I was most hoping for – left the node's comments attached and intact. Nodetype, you swinging switch-hitter, you're all right by me!

You can see my results here:

http://www.drupalace.com/blog_entry_trick_bin_hiding_node_title_2007_07_03

That node was a Blog Entry but is no longer; only its URL alias hints at its original configuration. (Kind of like the Adam's apple on "Lucy" in that Phuket night clu... no, the Ace is speaking too much here. Full stop.)

Now, I haven't used Nodetype enough to give out any handy tips, but the following safety procedures would seem wise:

1) Back up your database before dabbling in node DNA like this.

2) Your target node type may have different fields from your original node type, and I would imagine that data gets lost when a field gets dropped. Copy all major text field data from your original node before changing its type, to avoid loss.

3) Experiment first with a dummy node, if you really want to be safe before operating on the real thing.

If you've ever agonized over what node type to use for some piece of content, worried about getting "stuck with" the wrong decision, you can relax a bit with Nodetype in your arsenal. Bring out the tranny in your nodes! Good stuff.

Time for this newbie to take the plunge, and touch... oh, sweet mother of mercy... touch PHP!

A Drupal.org forum visitor asked about displaying the date and time on a site. I know there are countless ways to do this using web technologies, including any number of "widgets" available out there. For all I know, there may be a Drupal module that tosses up a block or something, too.

But I know this is the sort of task one can also do easily using PHP, the real guts of Drupal (well, part of the guts, anyway... maybe the pancreas). And it should be easy, too. So as a farewell to my... ahem... chastity with regards to PHP, let me take this oh-so-newbie challenge upon myself.

Google turns up all kinds of stuff. Like this couldn't-be-more-basic, one-size solution: http://www.totallyphp.co.uk/code/display_date_and_time_with_php.htm

Besides some code comments, there's just one line of key code there:

<?php  echo date("l, F d, Y h:i" ,time()); ?>

Let's try! I make a new block... turn off rich-text input (TinyMCE)... select PHP as my input format... and paste in the code. I save the block and make it display... and there it is, to the left! Stupendous!

Now, that's the barest of starts; I'll add more to this page as I play with more formatting and other options. (Like time zones: that's pretty important!) But wow, I'm now PHP-experienced and it didn't hurt at all. Before long I'll be up for CSS/HTML/PHP themeing three-ways til the break of dawn. Mmm, break out the mango love butter.