Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COI think you hit the nail on the head with the panels, I've a feeling that's the issue. Re: node template, see this pic: http://imgur.com/04H3Z - do I need to click edit on that setting, so that I can choose "Node Body"? (Or is Node Body someplace else?) Reason I ask is because I don't see "Node Body" once I click "Edit", here's what I see: http://imgur.com/0klry I'm on Drupal version 7.12 so perhaps the admin menus are laid out differently in the version I'm using? The video you linked had different menus for panels... Once again, thanks very much for all your help and patience.
      singulars
    2. COPanels gives you great flexibility, but if you're a beginner it can be too much. If you want the node to display normally just disable that panel. Follow some tutorials on panels to learn more about it, but this should get your node showing if you disable it.
      singulars
    3. COthe panels were indeed the cause of all the heartache. I'm using them for another part of the site to display stuff. I've a decision now - do I attempt to separate out panels so it continues to work for the old part of the site and doesn't affect the blog adversely? Or do I disable Node Template and re-style the old part, using Views for everything? Anyway, thanks a million for the help, wouldn't have thought of checking out Panels as the cause of the problem in a million years. Would bump up your karma except I'm below the threshold.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload