No-Module-Required Static Content in ExpressionEngine

Here’s a “back to basics” tutorial for newcomers to ExpressionEngine - how to build a static portion of a website, with no plugins, extensions, or modules required.

While this has always been possible in EE, I think the popularity of Mark Huots “Tome” Module or the availability of the native EE Pages Module has mislead some folks into thinking that these modules are required for presenting static content in EE. 

Nothing could be further from the truth - and in fact there are some advantages to sticking with native EE functionality for static content.

 
Download the EE Code for No-Module-Required Static Content in ExpressionEngine

This tutorial is meant in no way to disparage the Tome module - I’ve used it and do appreciate many aspects of it including the site-map based UI, the easy breadcrumbs and nice URL’s.  I also appreciate the authors contribution to the EE community and will readily confess that his coding skills are on another plane from my own…

Having said that, using native EE code for building a static section of content has a number of advantages over the Static Page module.  I’ll cover those after taking you through how to build a static content section using the native EE code approach. I do also want to note that there is an entry on the EEWiki regarding static content outside the Pages Module, but I felt it could be improved upon - especially for newcomers to EE.

When finished with this build approach adding a page to this section of a site is just a matter of publishing a new post to the designated weblog.  Need to delete a page?  Just delete that post and the page is gone from the site.  Want a page to show up on a certain date?  Just publish the entry with a Entry Date set to the future date required.

OK - with the disclaimers out of the way let’s proceed.  In the following tutorial I’ll show how to build a simple static section with a default Index page and some subpages.  I’ve posted both a working example of this approach so you can see it in action.

For this native-EE static content approach you’ll need a new weblog, field group, content, and a new template.

Note on Links/URL’s
Here on Train-ee.com “courseware” is my renamed EE index.php.

Weblog Setup

  • In the EE control panel, navigate to Admin >  Weblog Administration >  Weblog Management
  • Click the “Create a New Weblog” button and create a weblog to hold the content.  I’ve called mine “Static”.

Field Group Setup

  • In the EE Control Panel, navigate to Admin >  Weblog Administration.  Click on “Custom Weblog Fields”, then the “Create a New Weblog Field Group” button.  Name your new field group - I’ve created one called “staticpage”.
  • Now click the “Add/Edit Custom Fields” link by your new Field Group and add a new field.  I have just one field in the group, called “static_page_content” - which is a textarea with 12 rows.  This assumes my static pages are very simple, with a title and paragraphs of text.
  • Now back under Admin >  Weblog Administration >  Weblog Management, click the “Edit Groups” link by the “Static” weblog.  Assign the new field group to the weblog and save.

Content Entry

  • Index Content
    This approach assumes the the Index page (or section default page) content is entered first - so click the Publish tab and choose your new weblog.  Enter your Index content and save the entry.
  • Subpages
    The next posts entered in the new weblog will become our sub-pages, so create a new post for every sub-page you’ll need. I’ve entered 6 posts for six subpages.

No worries if you enter the content out of order - you can always tweak the publish dates to push the Index content to be the oldest entry.

Template Coding
For the purposes of this tutorial, I’ve created a new template group and called it “static”.  All we’ll need is the index template that EE provides by default.  For reference, download the text version of my template.  Copy/paste anything you need - just tweak for any path or name differences.

The template uses two weblog:entries tags—one to build the left navigation, and one to display the page content.

  • Left Navigation
    For left navigation we want links to all the sub-pages, but not a link to the Index page.  This is done by using the “sort=“asc” parameter to put the oldest post (our Index content) last, then using the “offset=“1” parameter to drop that one from the list.  The “dynamic=“off” parameter is important here - if you don’t use it you will lose the subnavigation as soon as you click one of the links to a sub page.  Note that using a date-sort on this tag means the left navigation list can be ordered in any way just by tweaking the pubish date of the entries.
  • Page Content
    A second weblog:entries tag brings in the page content.  The “limit=1” parameter ensures that we will only see content from one post. The “sort=“asc” parameter ensures that, if no url-title is passed to this template by one of the subnavigation links (like a link from your main navigation bar), the Index content will be loaded.

That’s really all there is to building a simple, two-level static section of content with ExpressionEngine.  And this is just one approach - as with anything ExpressionEngine there are always multiple ways to achieve your goals.

Advantages
There are a few advantages of using this approach over the Tome module:

  • An obvious one - no additional software to install or update, or worry about when upgrading EE
  • Adding subpages is easier - all you (or your clients) need to do is publish a new entry to the Static weblog and it will immediately appear in the subnavigation.  No creation of categories is required.
  • Removing pages is easier - you can either close out pages (great for content that’s being edited) or just delete the post from the weblog.  No deleting categories requried.
  • All native EE segments and conditionals are available for more advanced template coding.

Category Navigation

Next Entry >>

 

Previous Comments

Picture of Addison Hall

by Addison Hall

Date: Wednesday, November 26th, 2008
Comment: #1

Sorry I’m late to this—great article. Just to make sure I understand correctly, you’d have to create a new weblog for each main section of your site, correct? I’m trying to see this in the scope of an entire site…

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, November 26th, 2008
Comment: #2

Yes - but that’s an approach I take generally anyway.  I like the pubish&edit;menus to reflect the same main navigation as the rest of the site.

Picture of Addison Hall

by Addison Hall

Date: Wednesday, November 26th, 2008
Comment: #3

This is beautiful. I’m about to revise a small site now and ditch the static pages module.

Can you recommend a good dynamic method of generating the top-level navigation? I’m guessing I could assign a special category and use the “not” parameter to leave out weblogs I don’t want included.

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, November 26th, 2008
Comment: #4

I don’t make top-level nav dynamic, as for the sites I’m working on it’s hardly likely to change.  I just implement it usually with an unordered list, which only takes a few seconds to update if need be.

And - if top-level nav is changing other EE work is likely required anyway.

Picture of Addison Hall

by Addison Hall

Date: Wednesday, November 26th, 2008
Comment: #5

Good point—thanks!

Picture of Geof Harries

by Geof Harries

Date: Wednesday, December 17th, 2008
Comment: #6

This is the same method in which I always build static pages, as long as they don’t go more than two levels deep, in which case things get more complicated. The Pages module is just too limiting when it comes to parameters and variables. I love this site, Mike.

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, December 17th, 2008
Comment: #7

Thanks Geof!

Picture of pab

by pab

Date: Tuesday, April 14th, 2009
Comment: #8

Excellent tutorial. really enjoyed the way you explained everything.

Thanks

Picture of Jay Lee

by Jay Lee

Date: Tuesday, April 14th, 2009
Comment: #9

Great stuff!  I was wondering how you could get the first weblog entry to display as the default content that shows up when someone goes directly to the static index section.  Right now, the last entry shows (6th entry) when no URL-title is passed, but I’m trying to create an “overview” entry to show if someone goes directly to the static section index (i.e. the “/static/” page).

Mike Boyink

by Mike Boyink (Author)

Date: Tuesday, April 14th, 2009
Comment: #10

Hi Jay—
Essentially you just use the sort parameter to get the right one to show by default.  It only gets used when the page is loaded without a URL title

Picture of pab

by pab

Date: Tuesday, April 14th, 2009
Comment: #11

Hi, i was wondering if it was possible to use mark huot’s translation plug in with this

i have to set up 5 different teams with 20 players each and in 2 languages

i currently have this but it wont let me switch to the french content

{exp:weblog:entries weblog=”{exp:translator:simple weblog=“team_2”}”  sort=“asc” offset=“0” dynamic=“off”}
              <li>{title}</li>
          {/exp:weblog:entries}

Picture of pab

by pab

Date: Wednesday, April 15th, 2009
Comment: #12

*update

got the content to switch but not the titles

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, April 15th, 2009
Comment: #13

Pab - I have no experience with that plugin, but consider this to be about the simplest EE template you’ll ever use in a production site.  If the plugin can’t work with it I’d look to another method of doing a multilingual site.

Picture of pab

by pab

Date: Wednesday, April 15th, 2009
Comment: #14

Thanks Mike, i found another method that i will try out. do you have any tips for multilingual sites,

Mike Boyink

by Mike Boyink (Author)

Date: Thursday, April 16th, 2009
Comment: #15

Hi Pab - there’s been a fair amount of discussion around multilingual sites so a search of both the EE forums and Wiki should prove fruitful.

Picture of Jay Lee

by Jay Lee

Date: Thursday, April 16th, 2009
Comment: #16

Hi Mike, I just implemented your method and it works great!  I was wondering if you had a recommendation on how the left navigation can be coded so that a “selected” class can be added to improve usability.

Mike Boyink

by Mike Boyink (Author)

Date: Thursday, April 16th, 2009
Comment: #17

Hi Jay

If you go to the little static site linked to in this example there is a version there that handles the active class using URL segment variables and a conditional.

Picture of Janesse

by Janesse

Date: Thursday, April 30th, 2009
Comment: #18

I am a total beginner who sort of got pitched into EE. I have really appreciating both your free and downloadable resources.

I tried this tutorial particular using the same names and got the navigation to appear, but I get a 404 error when I click on any of the items.

I started from scratch using my own content but get the same problem exactly the same problem. What might I be doing wrong?

Mike Boyink

by Mike Boyink (Author)

Date: Friday, May 1st, 2009
Comment: #19

Hi Janesse -

Have you compared the link that EE is generating vs. your install directory, template group and template names?

Picture of Janesse

by Janesse

Date: Friday, May 1st, 2009
Comment: #20

Is there a summary somewhere of how to troubleshoot generated links? (I’m a Communications person and I’m really having trouble getting my head around this stuff. I don’t find the documentation all that helpful.)

Link:

http://actra.ehclients.com/index.php/contact/index/

Content:

<div id=“content_main”>
      {exp:weblog:entries weblog=“about” limit=“1” sort=“asc”} <h2>{title}</h2>
      {static_page_content}
      {/exp:weblog:entries}
</div>

Structure:

Weblog/Short Name/Template/FieldGroup/Custom Field Name

Contact/contact/contact/Contact/Contact

Mike Boyink

by Mike Boyink (Author)

Date: Saturday, May 2nd, 2009
Comment: #21

Hey Janesse -

My degree is actually in Communications as well, so take heart- there is hope..;)

I will say that if you aren’t pretty savvy with HTML/CSS in general then trying to learn EE may be a bit too much at one time.  It’s hard to troubleshoot when you’re not sure where one ends and the other starts.

I followed your link - and just to make sure, its the nav on the right that isn’t working?

The link is rendering out looking for a template group named “static”, and either a template name of “staff_list” or using the index template and pulling a weblog entry with a url_title of “staff_list”.

If that’s not where those links need to connect to then the pathing needs to change in the weblog:entries loop that builds that right-column nav.

Picture of Janesse

by Janesse

Date: Monday, May 4th, 2009
Comment: #22

Thanks so much, Mike, that points me in the right direction.

I’m okay with HTML and learning CSS, so if I can’t make it work I’ll this way I’ll just surrender and use a different navigation set-up.

Picture of Craig

by Craig

Date: Saturday, April 24th, 2010
Comment: #23

Hi Mike, not sure what I’m doing wrong here.

When i update the index content it proceeds to display its hidden subnav link at the bottom of the left navigation?

It then removes it as the default index content.

Mike Boyink

by Mike Boyink (Author)

Date: Sunday, April 25th, 2010
Comment: #24

Hey Craig -

Sounds like the entry date is getting changed - if that’s what your sorts depend on make sure the index entry is again the oldest in the bunch.

Picture of Craig

by Craig

Date: Sunday, April 25th, 2010
Comment: #25

Thanks Mike. That sorted it out.

Picture of Richard Wiggins

by Richard Wiggins

Date: Wednesday, May 5th, 2010
Comment: #26

Hi Mike,

Firstly, great article!

I’m new to EE but just starting a couple of client sites using it.

One requires a lot of ‘static’ type pages so I was planning on using your method of having a weblog for each section of the site.

Not sure if this is possible, but for some of the site sections, a unique template will be required.

e.g. I’ll have a section called ‘Industrial’ with various sub-pages. The sub-pages will most likely have the same template but the initial section page would require it’s own unique template.

How would you suggest I handle this?

Thanks, Richard

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, May 5th, 2010
Comment: #27

Hey Richard - thanks for the comment.

Another template is no sweat - you’ll just have an index template that main nav will link to, and a different template that your sub nav would link to.  Create embedded templates for common elements.

Picture of Richard Wiggins

by Richard Wiggins

Date: Wednesday, May 5th, 2010
Comment: #28

Hi Mike, thanks for the quick response - super quick!

Okay, think that makes sense. Just getting myself a bit confused at the moment. Just need to get my hands dirty I think.

Cheers.

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, May 5th, 2010
Comment: #29

You might check out the Small Business series - in the Products section and how it goes from a /list/ template to a /detail/ template - very similar to what you are wanting to do.

Picture of Richard Wiggins

by Richard Wiggins

Date: Wednesday, May 5th, 2010
Comment: #30

Thanks Mike, will do.

Mike Boyink

by Mike Boyink (Author)

Date: Thursday, May 6th, 2010
Comment: #31

Hey Richard -

I’m off for the rest of the day - but quickly:

Put all your entries in one weblog.  Create two templates. 

One template - overview - would just pull a specific entry from the weblog.  You can specify that one entry by it’s url_title, or arrange the entry dates so that specific entry is the oldest and pull by date, or you can pull by entry ID.

Then in the second template use the reverse logic to ignore that one entry. 

Same thing with sub-navigation in this section—just make sure to use weblog:entries parameters to ignore the one entry that drives the index content.

Mike Boyink

by Mike Boyink (Author)

Date: Thursday, May 6th, 2010
Comment: #32

Now that you have the concept - use code from your overview template in the index template for that template group.

Mike Boyink

by Mike Boyink (Author)

Date: Friday, May 7th, 2010
Comment: #33

Well - let’s step back a bit.  Make sure you have an understanding of EE’s approach to constructing URLs

I think what you are running into is that you can only have one template that loads by default from a template group - the index template.  This is the only template that you can omit from the URL and still have things work.

So you have three choices:

1. mysite.com/index.php/section/—loads the overview (and omits the template name)

mysite.com/index.php/section/detail/sub_page_url_title/—loads a specific detail page


2. mysite.com/index.php/section/overview/ - an overview template in the section template group.

mysite.com/index.php/section/sub_page_url_title/—using the index template loads a detail page (and omits the template name).


3. mysite.com/index.php/section/ - loads the index template (and omits the template name)

mysite.com/index.php/section/sub_page_url_title - also loads the index template (and omits the template name)

This option requires that your index template uses segments and conditionals to analyze the URL and load the appropriate template design.

To pull off #3 the essential approach is

{if segment_2==""}
  load the overview HTML 
and content here
{
/if}
{if segment_2 
!=""}
  load the detail HTML 
and content here
{
/if} 

#3 offers cleaner URLs but makes for a more complicated index template - moreso the more different your overview and detail HTML is. It essentially becomes 2 templates in one.

You can see this in action bv comparing Train-ee to Boyink.com.  Here on Train-ee the page you are reading is at free-tutorials/comments/entry_url_title - the index of free-tutorials loads the more abbreviated blog view, comments is the name of my detail template that displays an entire post and the comments with it - so this is an implementation of #1 above.

On Boyink.com my blog index is:
http://boyink.com/write/

And a detail page URL is:
http://boyink.com/write/expressionengine-certification-program/

Here I essentially used the #3 approach - working entirely within the index template of the /write/ template group, using logic to pull the right HTML and content based on the URL contents.

Picture of Henk

by Henk

Date: Wednesday, May 12th, 2010
Comment: #34

Thanks Mike, I had the same problem as Richard. You interact so well with your users, it’s like a second tutorial in the comment section. It’s a pleasure to post something to this blog.
You are doing a really good job. I follow you!

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, May 12th, 2010
Comment: #35

Thanks—appreciate the comment!

Picture of Ralph

by Ralph

Date: Wednesday, June 9th, 2010
Comment: #36

Sorry for being really stupid about this, but I don’t understand the use of the word “static” in this article. I think of weblog/channel entries as anything but static. To me, that’s all dynamic—a static site being one that’s hard-coded in HTML with no CMS at all.

Could I just clarify why you are calling the above approach “static”, as I see this a lot and am befuddled by it.

PS This is not to take anything away from the great content here. It’s a question I’ve been troubled by. I’m obviously missing something quite basic.

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, June 9th, 2010
Comment: #37

In this case static means less likely to change, less often added to, not a blog, etc.

Picture of Ralph

by Ralph

Date: Wednesday, June 9th, 2010
Comment: #38

Thanks Mike. It suddenly dawned on me last night that this must be what it means. Up until now I’ve though of static content as text etc simply built into the template, but I guess it’s kind of pointless to use the word that way for EE, as the CMS is not really intended for that scenario anyway.

Thanks again.

Picture of Ralph

by Ralph

Date: Sunday, June 13th, 2010
Comment: #39

Hi Mike, I tried this method and it works a treat. Except… I wanted to use this method with the index template of the default group (which I’ve called “home”). In this case, while the index template appears at mysite.com/, the sub pages appear at mysite.com/home/subpage.

Is there any way around this? I couldn’t see this issue mentioned above, but apologies if it’s there.

PS
I’m using EE2.

Mike Boyink

by Mike Boyink (Author)

Date: Monday, June 14th, 2010
Comment: #40

No - no way around this without resorting to something like the Pages Module—especially if you want good 404 handling as turning on strict URL’s would enforce EE needing to see a valid template group name in that first segment position.

Picture of Ralph

by Ralph

Date: Monday, June 14th, 2010
Comment: #41

OK, thanks Mike. When I think about it now, what I was trying to achieve was unreasonable, but it was easier to find out by trying and failing. The client was hoping to omit the template group name, so I’ll consider the Pages Module, but perhaps just for a few select pages, as I much prefer your method—even with the group name showing. Many thanks again.

Picture of Chris F

by Chris F

Date: Thursday, July 8th, 2010
Comment: #42

Hey Mike,

I’ve used this method in my site and it works a treat. But I’m just wondering if there is a way to highlight each sub nav button when it becomes active? Could it be some kind of conditional variable which checks for the site url?

Hmmmm…not sure!

Thanks,
Chris.

Mike Boyink

by Mike Boyink (Author)

Date: Thursday, July 8th, 2010
Comment: #43

See the links here where it mentions an alternate version with an active class applied to the selected item.

Picture of Matt

by Matt

Date: Tuesday, October 26th, 2010
Comment: #44

Hi,

Thanks for the great article! Is it possible to show comment entries on individual Blog posts if I use the Pages module to set a more SEO friendly URL for the article?
For example: domain.com/article_title
Because when I try to do this the comments won’t show…but when I visit the original longer url, then they are there.
Any suggestions about this? (Using EE 1.6.8)

Thanks in advance!

Best Wishes,
Matt

Mike Boyink

by Mike Boyink (Author)

Date: Tuesday, October 26th, 2010
Comment: #45

I don’t use the pages module much but it’s not intended to be used with dynamic content like blog entries (just the opposite). You’d be better off running your single entry template from the default template group and letting EE work with the entry URL titles like it wants to.

Picture of Ryan Ricci

by Ryan Ricci

Date: Friday, October 29th, 2010
Comment: #46

Can I use this if I have a Main navigation > Sub Navigation (pages) > sub pages of the sub navigation?

Thanks in advance,
Ryan

Mike Boyink

by Mike Boyink (Author)

Date: Friday, October 29th, 2010
Comment: #47

No. See the “three tier options” in the right nav.

Picture of Ryan Ricci

by Ryan Ricci

Date: Friday, October 29th, 2010
Comment: #48

Thank you Mike!

Picture of Daniel Goulding

by Daniel Goulding

Date: Thursday, January 20th, 2011
Comment: #49

Hi Mike,

Thanks for a great blog article.

I was just wondering if it was possible to make a series of URLs like “mysite.com/about”, “mysite.com/contact” etc, all from the same static page template? I.e. I know all these pages are going to be static, and I want to use the same template for them. The thing that will change will be the body copy and title, which I’d like to edit through the content publisher.

Thanks,
Dan

Picture of Boyink

by Boyink

Date: Thursday, January 20th, 2011
Comment: #50

Hey Dan -

You can have URL’s like that only two ways:

1. Use the index page of the site and so some conditionals to pull other content if there is a value in the segment_2 position, otherwise load the home page content.

2. Use the Pages module for this content, which lets you assign a URL and choose an “output template”.

Picture of Daniel Goulding

by Daniel Goulding

Date: Thursday, January 20th, 2011
Comment: #51

Thanks Mike,

I’d like to go for the pages approach, but if I do, how would I get the page content from the url?

the url_title cannot be the same as the pages URI, so my segment_1 is not going to be usable with the channel:entries tag.

Cheers,
Dan

Picture of boyink

by boyink

Date: Thursday, January 20th, 2011
Comment: #52

With the Pages Module you don’t (can’t actually) use segment variables.  And wouldn’t need to in this case.

The Pages Module provides the routing of specified URI to template to output on the site.

It’s a pretty straightforward Module - install it, read the docs, give it a try..

Picture of Daniel Goulding

by Daniel Goulding

Date: Thursday, January 20th, 2011
Comment: #53

Thanks again for your response.

I’ve set up and I’m now using the Pages module.

If I want to use the same template for all my static pages, with dynamic content coming from custom fields I’ve set up, how do I get the right content out for the right page?

I appreciate this approach might be going slightly against the grain, but I thought it would be a nice way to enable static pages to be edited through the content publisher.

Thanks again,
Dan

Picture of Daniel Goulding

by Daniel Goulding

Date: Thursday, January 20th, 2011
Comment: #54

I figured it out - if the Pages URI is present in the url, it will automatically limit the entry to that particular pages entry, provided you don’t have dynamic=“no” set as a parameter.

I’m new to EE, and didn’t realise this functionality before.

All working very nicely now.

Thanks for your help Mike.

Dan

Picture of Boyink

by Boyink

Date: Friday, January 21st, 2011
Comment: #55

I actually held back hoping you’d figure it out on your own..;)  Glad you got it sorted!

Picture of Anders

by Anders

Date: Wednesday, January 26th, 2011
Comment: #56

Hey, I have created a “static” main navigation bar with the following coding for my multilanguage site:

<ul id=“nav”><li>HOME</li>
      <li>ANGELSPORT & NATUR</li>
      <li>REISEN</li>
      <li>ÜBER</li>
      <li>BUCHUNG</li>
      <li>FORUM</li>
      <li>HILFE</li>


</ul> 

I have attached the proper CSS coding and it looks pretty good. The main navigation won’t really change (as you pointed out yourself it is easy to change), however it could be quite a deal of subpages that would be needed to be attached to this navbar. If I use your method above then for example my “reisen” template would be my index and then the sub pages would follow when I publish a new post to the designated channel. However I don’t understand how to call the subpages into a dropdown menu. Don’t I need to manually specify a <li> tag for every sub item in my nav code? As in the following example:


  <ul>
    <li>sub menu 1</li>
    <li>sub menu 2</li>
    </ul>

Is there a code that fix this so it automatically add sub menu 3,4 etc to the nav bar when a new post has been published, or am I going at this the wrong way? How would this code look in my example?

Best regards,
Anders

Picture of Boyink

by Boyink

Date: Wednesday, January 26th, 2011
Comment: #57

Deeper parts of the menu can be created dynamically with a channel:entries, channel:categories, category:archive or possibly other EE tags depending on how the content is structured in the system.

The post you are commenting on has one such example.

Picture of Andy

by Andy

Date: Monday, August 15th, 2011
Comment: #58

Hey Mike,

Im using EE2 and have replaced the “weblog” with “channel” as well as making the new channels and custom fields to match the tut.

When I click the links, generated from the post titles, the url changes but content remains the same (as in stays on the first post entry).

Any idea where I might have gone wrong?

Mike Boyink

by Mike Boyink (Author)

Date: Monday, August 15th, 2011
Comment: #59

Hey Andy -

I suspect you have “dynamic=“no” on the EE tag that fires the main content area of the page.

That property needs to be set on the EE tag that builds the navigation, but not on the main content area as that one does need to read the URL to know what entry to pull.

Picture of Andy

by Andy

Date: Monday, August 15th, 2011
Comment: #60

Hi Mike,

Thanks for the fast response.

Still can’t seem to get the content to change. It just sorts it in asc, rather than pulling the entry.

I did have dynamic=“off” for the nav tag, changed that to dynamic=“no”. And my main content area is like your file:

{exp:channel:entries channel=“static” sort=“asc” limit=“1” }
<h2>{title}</h2>
{static_page_content}
{/exp:channel:entries}

Not sure if this is right? Or if there is something else that needs to be added for EE2?

Thanks for your help,
Andy

Mike Boyink

by Mike Boyink (Author)

Date: Monday, August 15th, 2011
Comment: #61

No - this is all pretty basic and other than the weblog to channel terminology change should all work in EE2.

What’s the name of your template group, and the name of your template?

What’s the URL when you load the template in default mode, and what’s the URL after you click a navigation link?

Picture of Andy

by Andy

Date: Tuesday, August 16th, 2011
Comment: #62

Ah that is it! My template group name was called “index”, but changed it to “static” and it works.

Just realised the url link corresponds here.

Thank you for your help and excellent set of tutorials.

Picture of ThisOnlineThing

by ThisOnlineThing

Date: Wednesday, February 29th, 2012
Comment: #63

Thanks! “dynamic=“no” on the EE tag was what I was overlooking! I’m glad I skimmed through all the comments!

Add Your Comment

Commenting is not available in this channel entry.

Unless otherwise stated all content is © Michael Boyink of Train-ee.com & Boyink Interactive. Please don't steal - I've got kids to feed...

dy>