14 - Implementing the Weblog Comments Template

In this chapter I’ll show how to implement the weblog/comments template that will display the full weblog post as well as visitor comments.  This is a pretty straightforward ExpressionEngine implementation with the exception of creating some additional embedded templates.

 
Download the EE Code for 14 - Implementing the Weblog Comments Template

While the weblog/index template got fairly involved (and started to creep away from my tendency to create more simpler templates than fewer complex ones), implementing a template to display an entire weblog post and allow visitors to add comments is much simpler.  This is one of those “all roads lead here” situations in that no matter how the visitor chooses to use the index template to find a particular post, once they click through to read the full weblog post this template will be used.

The work, however, will start in the weblog/index template.  Since I’ll want to have the same left-column options of category and archive navigation on the single entry/comments pages, I want to create embedded templates to hold the code that generates those links.  I can then embed those new templates back into both the weblog/index and weblog/comments parent templates. 

I also like to handle the actual comment display and comment entry form in an embedded template - so that if you implement comments elsewhere on the site you can just re-use the same form.  It’s usually a bit of work to style comments and the form so I don’t want that code to exist in multiple places.

So overall the work at hand today is:

  • Edit weblog/index to remove the category navigation code and place it in a new embeds/weblog_category_nav template
  • Edit weblog/index to remove the archive navigation code and place it in a new embeds/weblog_archive_nav template
  • Copy weblog/index as a starting point for weblog/comments
  • Edit weblog/comments to remove category and date heading code
  • Edit weblog/comments to remove links to itself
  • Create a new embeds/comments_form template
  • Edit weblog/comments to use embeds/comments_form

As usual I will provide you with a zip archive containing all the finished versions of these templates later on in this post.  For the moment I want to work through the process of creating them.

Creating embeds/weblog_category_nav
Open weblog/index for editing and select the entire “navcontainer” div that contains the code to build the category navigation:

<div class="navcontainer">
    <
h3>Categories</h3>
    <
ul class="navlist">

         
{!--This tag will build the left-column subnavigation --}
        {exp
:weblog:categories weblog="weblog" style="linear"}
            
<li>
                <

                     {
!--This conditional will cause the link to the currently-viewed category to be highlighted --}                                    
                    {if segment_3
==category_url_title}
                        
class="active"
                    
{/if}
                    href
="{path=weblog/index}">{category_name}
                
</a>
            </
li>
        
{/exp:weblog:categories}

         {
!--This conditional will display a "show all" link when template is loaded in a category mode --}                                    
        {if segment_2
=="category"}
            
<li><a href="/index.php/weblog/">Show All Posts</a></li>
        
{/if}
    
</ul>
</
div

Copy this, and create a new template in your embeds template group.  Name it “weblog_category_nav”.  Once the template is created paste in the code and save it. Now go back into weblog/index and replace that chunk of code with:

{embed="embeds/weblog_category_nav"

Repeat that process for the code that builds the archive navigation - again grabbing everything in the navcontainer div.  Name the new template weblog_archive_nav.  Your weblog/index template should now have only this in the left column:

<div class="content_page_left">
{embed="embeds/weblog_category_nav"}
{embed
="embeds/weblog_archive_nav"}
</div

Verify that the page still functions correctly in the browser.  Sometimes I grab a bit more or less code than I intended and end up with a div structure mismatch.  If it functions correctly then you can move onto creating the comments template.

Create weblog/comments
Create a new template in the weblog template group, but not a blank one this time.  In the “Default Template Data” area choose to duplicate weblog/index.  Click Submit to create the new template.

Edit weblog/comments
The index template is a good starting point for the comments template, but there is quite a bit of unnecessary code here.  You can remove - both from the embed statement that builds the page title and anywhere further into the code - the category_heading and the date_heading tagset.  For the page title, what’s needed is the static word of “weblog” and the entry title. 

Here’s the revised page-title building code of my weblog/comments template:

{embed="embeds/html_header" 

     
{!--The my_title value will always be used. --}
    my_title
="Weblog | 
    
     {!--This being a single entry page we just need the entry title --}
    {exp:weblog:entries weblog="
weblog" limit="1
    disable="
custom_fields|trackbacks|member_data|pagination|categories"}
        {title}
    {/exp:weblog:entries}
"


Further into the code you can also remove the conditional that creates the “Full Post” link and just display the full_post custom field.  You can also edit any of the links that point to the comments template - what I’ve done is change them to point at a bookmark instead—so the link will jump users down to where the comments actually start.

Here is the revised main content area of my weblog/comments template:

<div class="content_page_right">
     
{!--This is the main weblog:entries tag that will return individual blog posts.  The category links and archive links function as a filter on this tag. --}
    {exp
:weblog:entries weblog="weblog" disable="trackbacks" limit="1"}
        
<div class="post">
            <
h3>{title}</h3>
            <
div class="post_meta">
                
By {url_or_email_as_author}  on {entry_date format='%F %d, %Y'} in 
                {categories} 
<a href="{path=weblog/index}">{category_name}</a> &nbsp;&nbsp;{/categories}
                {if allow_comments}
({comment_total}) <a href="#comments">Comments</a>{/if}
            
</div>
            
{teaser}
            {full_post}
        
</div>
    
{/exp:weblog:entries}
</div


Save your changes and load your weblog/index page in the browser.  You should be able to click any “full post” link and bring up the new weblog/comments template, and it should display the entire post.

Displaying and Accepting Comments
At this point you have a functioning single entry page; but it won’t show any comments or display the form needed to accept new comments.  Let’s add that.  But first, a word on my approach here.  For me the styling of both comments and the comment form is time consuming, and especially so with the template approach we’ve taken here.  If the template set doesn’t come with weblog templates (as this one didn’t) then there are a fair number of items to style.  It can get tedious, and once done I don’t want to have to mess with it again.  With a site that’s likely to allow comments in multiple places, it just makes sense to put the comments display and form into an embedded template so we can pull it from anywhere on the site.

First I need to create the embedded template.  I’ve named mine “comments_form”, and here’s the code it contains.  Give it a read-though, then I’ll cover the highlights:

<a name="comments" ></a>
{exp:comment:entries weblog="{embed:the_weblog}" limit="1"}
    {if total_results 
>0}
        
<div class="info"><h3>Previous Comments</h3></div>
    
{/if}
{
/exp:comment:entries}

{exp
:comment:entries weblog="{embed:the_weblog}" limit="100"}
    
<div class="comment_entry">
        <
h4>#{count} from {url_or_email_as_author} on {comment_date format='%F %d, %Y'}</h4>
        
{comment}
    
</div>
{/exp:comment:entries}

<div id="comment_entry_form">
    
{exp:comment:form}
        
<h3>Add Your Comment</h3>
        
{if logged_out}
            
<div class="comment_label">
                
Name:
            </
div>

            <
div class="comment_field">
                <
input type="text" class="textbox" name="name" value="{name}" />
            </
div>
            
            <
div class="comment_label">
                
Email:
            </
div>

            <
div class="comment_field">
                <
input type="text" class="textbox" name="email" value="{email}" />
            </
div>

            <
div class="comment_label">
                
URL:
            </
div>
    
            <
div class="comment_field">
                <
input type="text" class="textbox" name="url" value="{url}" />
            </
div>
        
{/if}
        
        
<div class="comment_label">
            
Comments:
        </
div>

        <
div class="comment_field">
            <
textarea name="comment" cols="60" rows="12">{comment}</textarea>
        </
div>

        
{if logged_out}
            
<div class="comment_field">
                <
p>
                <
input type="checkbox" class="check" name="save_info" value="yes" {save_info} /> 
                
Remember me?
                </
p>
            </
div>
        
{/if}

        
<div class="comment_field">
            <
p>
            <
input type="checkbox" class="check" name="notify_me" value="yes" {notify_me} /> 
            
Shoot me an email when someone responds?
            </
p>
        </
div>

        
{if captcha}
            
<div class="comment_label">
                
Enter this word:
            </
div>
            <
div class="comment_field">
                <
p>{captcha}</p>
            </
div>
            <
div class="comment_label">
                
Here:
            </
div>
            <
div class="comment_field">
                <
p>
                <
input type="text" class="textbox" name="captcha" value="" 
                
size="20" maxlength="20" style="width:140px;" />
                </
p>
            </
div>
        
{/if}

        
<div class="comment_field">
            <
p>
            <
input type="image" class="comment_submit" 
            
src="{site_url}images/interface/send-button.gif" name="submit" value="Submit" />
            </
p>
        </
div>

    
{/exp:comment:form}
</div

My starting point for this code was the default templates that install with EE.  What I’ve added/changed is:

  • Put an HTML bookmark at the top so that I can link directly to this portion of the page both from weblog/index and the article portion of this template
  • Added an initial comment:entries[/url] tag for the sole purpose of displaying the “Previous Comments” header only if there are, in fact, previous comments.  This is done by using the count variable in a conditional
  • Changed the CSS selectors to match what I created in my own stylesheet

The rest of the template is pretty straightforward and “out of the box” so I won’t cover it in detail here.  All that’s left is to go back into weblog/comments and add the embed statement to pull in this new embeds/comments_form template.  This goes right after the closing weblog:entries tag in the main content div:

{embed="embeds/comments_form" the_weblog="weblog"

And note that we’re passing in the required weblog parameter.

Comment Permissions
I also want to point out that there are two ways to enable or disable commenting.  You can do it at the weblog level by editing your preferences at Admin >  Weblog Administration >  Weblog Management >  Edit Weblog > Comment Posting Preferences.

You can also set it at the member group level by editing those preferences at Admin >  Members and Groups >  Member Groups >  Edit Member Group > Comment Posting Privileges. 

Here on Train-ee I have the member groups configured such that you have to register and be part of the “Members” group or higher to post comments.  The Guests group has comment privileges disabled.  On the Church site, I set it up such that the comment form will display to guests but comment submissions by guests will generate an error.  This is by design - to be able to show the comment form and it’s styling, but not open up the site for spam issues.  Once this site is done and auctioned off I will reconfigure that to suit the needs of the new owner.

That about does it for a working weblog with index, category, archive views and commenting.  Up next?  I’ll start in on the Ministries section.

Category Navigation

<< Previous Entry   

Next Entry >>

 

Previous Comments

Picture of parsoncraig

by parsoncraig

Date: Monday, June 30th, 2008
Comment: #1

Mike,
I have followed you so far, but I noticed url problems when I did lesson 13 in that the navigation buttons (categories and archives) did not go to the correct url’s to display filtered entries.  After completing this lesson, I was frustrated to discover that the full page entries similarly goes to the same weblog.

I think this has something to do with configuration of the new EE site.  I am hosted by EE themselves, and I have the multi-site feature like you but have not yet set up domains.

I paid attention to the url’s as you suggested.  When I hover, Safari displays the numeric url’s you suggest, but they actually go to the same display of my overall site weblog (the one installed when EE is installed.

Here are some sample url’s that appear in the browser:

God sightings     http://mysitename.pmhclients.com/index.php/weblog/C9/

CHurch NEWs       http://mysitename.pmhclients.com/index.php/weblog/C7/
From the pastor   http://mysitename.pmhclients.com/index.php/weblog/C7/

FULL POST example
http://mysitename.pmhclients.com/index.php/weblog/comments/gnosticism_glorified/

I notice, however, that the Weblog I created in the earlier lessons is displayed properly.  But it’s url is:
WEBLOG         http://mysitename.pmhclients.com/index.php/site/weblog-index/

or

http://mysitename.pmhclients.com/index.php/page-comps/weblog-index/


I thought I followed your instructions painstakingly.  Any idea where I went wrong?

Mike Boyink

by Mike Boyink (Author)

Date: Monday, June 30th, 2008
Comment: #2

Craig - you haven’t told EE to use category url titles rather than category ID’s.  The setting is found under Admin

Picture of parsoncraig

by parsoncraig

Date: Monday, June 30th, 2008
Comment: #3

You were right about that, but that did not address the problem, but merely changed the data:

Notice that the url of the weblog page I created has the word “site” in the url.  The others are looking at a different directory.

Weblog url
http://mysitename.pmhclients.com/index.php/site/weblog-index/

God sightings   http://mysitename.pmhclients.com/index.php/weblog/category/god_sightings/

CHurch NEWs
http://mysitename.pmhclients.com/index.php/weblog/category/church_news/

From the pastor
http://mysitename.pmhclients.com/index.php/weblog/category/from_the_pastor/

Archives
http://mysitename.pmhclients.com/index.php/weblog/2008/06/

Full Post
http://mysitename.pmhclients.com/index.php/weblog/comments/gnosticism_glorified/

It seems like something is supposed to located in a different location.  Because the above urls all display the contents of the original installation weblog called “default_site_weblog” rather than mine called “weblog.”

Mike Boyink

by Mike Boyink (Author)

Date: Monday, June 30th, 2008
Comment: #4

Ah - you created your weblog index template in the “site” template group, named “weblog-index”.

Instead you need a template group named “weblog”, with a template named “index”.

Keep in mind with EE these are no longer directories names but rather are template group and template names.

Picture of parsoncraig

by parsoncraig

Date: Sunday, December 21st, 2008
Comment: #5

Mike,
Can you please tell me where to edit the CSS for the comment_field tags that are in your comment_form. I need to change it so that it is visible against the background but I can’t find it anywhere.  I also need to figure out how to make the form for when not logged in align so that the labels are all to the left.  In Firefox, they seem to have an odd layout with the labels and input forms aligned vertically with respect to each other and not in a consistent fashion. I want it to look like yours here on your blog but can’t locate the CSS that is referenced in the html.

Mike Boyink

by Mike Boyink (Author)

Date: Sunday, December 21st, 2008
Comment: #6

Sorry - I’m not quite sure what you’re asking.  Are you not finding where in the church site templates the comment form CSS is? 

Or you can’t find the comment form styling in the CSS here on Train-ee?

Picture of parsoncraig

by parsoncraig

Date: Sunday, December 21st, 2008
Comment: #7

Sorry for the confusion. My bad.  I checked the code and realized I wrote the wrong thing.

In comments_form, I am referring to comment_field.  I cannot field where this is styled.  It is not a tag in the CSS file, as far as I can tell.  The items that are a problem for me all have that id. E.g., “<div class=“comment_field”>”

Mike Boyink

by Mike Boyink (Author)

Date: Sunday, December 21st, 2008
Comment: #8

Ah - looks like I might have added some classes and then not used them.

All that styling is done with this CSS:

#comment_entry_form {
    
padding15px 10px 15px 10px;
    
width:475px
    
border:2px solid #74220C; 
    
}

    
#comment_entry_form .comment_label {
        
width:105px
        
font-weight:bold
        
text-align:right;
        
floatleft;
        
padding3px 5px 0px 0px;
        
margin5px 0px 5px 0px;
        
}

    
#comment_entry_form textarea { 
        
border:1px solid #74220C; 
        
background#fff; 
        
padding:2px 0px 0px 5px;
        
margin5px 0px 5px 0px;
        
height:130px
        
width338px;
        
}
    
    
#comment_entry_form .textbox {
        
width341px;
        
margin5px 0px 5px 0px;
        
}

    
#comment_entry_form p {
        
margin5px 0px 10px 110px;
        
}

    
#comment_entry_form .comment_submit {
        
margin10px 0px 0px 0px;
        
Picture of parsoncraig

by parsoncraig

Date: Sunday, December 21st, 2008
Comment: #9

Then there must be some inheritance issues.  Because I can change those styles all day long and it does not affect those field labels in terms of color or placement.

Mike Boyink

by Mike Boyink (Author)

Date: Sunday, December 21st, 2008
Comment: #10

Ah - those are no fun to figure out.  I suggest installing the “Favelet Suite” for Firefox - or possibly Firebug.  Those tools will show you the trees for a given object to help figure out where styling is being applied.

Picture of parsoncraig

by parsoncraig

Date: Sunday, December 21st, 2008
Comment: #11

Thanks, Mike.  What a lesson. Evidently there must be a precedence in inheritance rules that I did not realize.  Perhaps you can explain.  It is drawing from a CSS object that is a “form” type ( form {color: DADADA} )  rather than the .div object called #comment_entry_form.  I had no idea it was doing that or why.

Mike Boyink

by Mike Boyink (Author)

Date: Sunday, December 21st, 2008
Comment: #12

Actually I’d recommend getting a good book or two on CSS - as we’re starting to veer off from the purpose of Train-ee.com. 

I don’t know CSS as well as EE - but understand the inheritance to be related to both the structure of the HTML and order of CSS rules in the stylesheet.  I know only enough to be dangerous, and it usually takes some experimentation to get the results I want.

Just make sure you’re applying the CSS you think you are (looking for case or spelling errors), and making sure the rules you want are located in the CSS after the rules for the higher up objects (so the CSS is general to specific in nature).

Picture of parsoncraig

by parsoncraig

Date: Sunday, December 21st, 2008
Comment: #13

Yeah.  Thanks, Mike.  I have a couple already but read them at a different stage.  Time to see if I can soak in more. The Firebug tip helped a ton. Thank you.

Picture of Gaurav

by Gaurav

Date: Tuesday, December 23rd, 2008
Comment: #14

Hi Mike,

For some reason I am not able to see all the comment fields except for a couple of fields. Why do you think that is? The link to my test website is: http://giantworldtelecom.com/ee/index.php/weblog/comments/weblog_post_six/

Mike Boyink

by Mike Boyink (Author)

Date: Tuesday, December 23rd, 2008
Comment: #15

It’s because you are logged in, and the form calls for some of the fields to be hidden from logged in users (because you have entered those fields while registering). 

View your site with another browser that are you not logged in with and all the fields will be there.

Picture of Gaurav

by Gaurav

Date: Wednesday, December 24th, 2008
Comment: #16

Yes, got it. Thanks.

Picture of Keith Heustis

by Keith Heustis

Date: Friday, January 9th, 2009
Comment: #17

This serious is so great. Thanks so much for doing this Mike!!!

Picture of Gaurav

by Gaurav

Date: Friday, January 16th, 2009
Comment: #18

Hi,

Is it OK if I put Categories and Archive in the same embedded template instead of seperating them in two embed files?

Mike Boyink

by Mike Boyink (Author)

Date: Friday, January 16th, 2009
Comment: #19

It’s your site..;)

Just the more you do things differently than what I have here the less I can help when issues come up.

Picture of Marcus Mucha

by Marcus Mucha

Date: Friday, January 23rd, 2009
Comment: #20

Hi Mike,

As expected, I’m getting the additional form fields when logged out, and fewer when logged in. However for some reason, I get the “You are not authorized to perform this action” error upon submit… even when I’m logged in.

I’ve checked my Comment Posting Preferences for the “weblog” weblog, and everything’s fine. Also double-checked my personal account settings and my member group settings and all is well here too.

Any ideas what I should try next?

As always, thanks for the excellent work.

Mike Boyink

by Mike Boyink (Author)

Date: Friday, January 23rd, 2009
Comment: #21

Hi Marcus -

Take a look at this KB article.  If that doesn’t get you anywhere, search the forums for the text of that error.  IIRC I’ve also gotten that error trying to submit a comment with the same content as an existing comment (usually “testing comments” etc..)

Picture of Gaurav

by Gaurav

Date: Friday, January 23rd, 2009
Comment: #22

Hi,

Where do we look for comments in the admin backend? What if we want to delete/ edit user submitted comments?

Mike Boyink

by Mike Boyink (Author)

Date: Friday, January 23rd, 2009
Comment: #23

There are links on the CP home page to latest comments, otherwise in the center area of the list of posts under the edit tab.

Picture of Diane

by Diane

Date: Tuesday, March 10th, 2009
Comment: #24

Hi Mike!  I am working with the Core module to get through as much as the tutorials as possible.  My Comment Form does not show at all.  I copied the <h3>Add Your Comment</h3> before the {exp:comment:form} I get that h3, but not the one afterwards (so I know it is doing the embed). 

When I view the source, all I have is
<div id=“comment_entry_form”>
  <h3>Add Your Comment</h3>
</div>

The documentation says that Core includes the Weblog module and the Comment module. Suggestions?

I re-copied/pasted your text, so I am pretty sure they are right.  And I double cked the Comment Permissions on both the weblog and the members/group.

Picture of Diane

by Diane

Date: Wednesday, March 11th, 2009
Comment: #25

Hum…  today it works for weblogs and ministries!  It is a mystery!

Picture of Chris

by Chris

Date: Thursday, March 19th, 2009
Comment: #26

Hi.  Your tuts are so good!  Thank you for doing these!

Question:  Do you have info (or could point to info) on how to create user comment functionality for an existing ee core site - instead of having to build the example church pages/content first?

Thank you
Chris

Picture of Pat Dryburgh

by Pat Dryburgh

Date: Sunday, May 3rd, 2009
Comment: #27

I am slowly working through EE, and have really enjoyed the tutorials here on this site.

The only issue I am having so far is posting comments. For whatever reason, when ever I click submit (either logged in or not), I get the following message:

“The following errors were encountered
You are not authorized to perform this action”

I went to the demo page for the church site this tutorial is working in, and when I tried to submit a comment there, the same message came up. So, now I’m even more confused.

Is this an EE problem, or a me problem?

Thanks for the help!

Mike Boyink

by Mike Boyink (Author)

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

Hey Pat -

That usually happens when EE doesn’t like something about your comment submission - your IP is blocked, etc.  You can see the KB article on it here.

You got this comment to go through though…so the actual cause isn’t clear.

Picture of Pat Dryburgh

by Pat Dryburgh

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

Hmm… that didn’t help.

The only other consideration is that the site is hosted on my localhost server. Could that be why it’s not working?

Thanks for the help!

Mike Boyink

by Mike Boyink (Author)

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

Oh sorry, I think I misunderstood. Is it train-ee that isn’t working or your site?

Would you happen to be submitting a comment that is already in the system?

That one has bitten me before.

Picture of Pat Dryburgh

by Pat Dryburgh

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

I am sorry, I meant I cannot post a comment on my own site. I’m trying to follow this tutorial :)

I don’t currently have any comments in my system. I’m not able to post any comments at all. The reason I mentioned not being able to leave a message on the church test site is because it brought up the same error message I am getting on my site, which seemed very weird to me.

Mike Boyink

by Mike Boyink (Author)

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

Hey Pat -

That does sound odd - you should be able to post comments on a localhost based site.  Typically you just wouldn’t get the email notifications to work.

I’d experiment with the Security and Session Preferences—turning off secure mode for forms, etc and see what happens.

If that doesn’t work then your next best step is probably EE tech support.

Picture of kris Utter

by kris Utter

Date: Tuesday, June 2nd, 2009
Comment: #33

I’m not seeing the capcha on my weblog when I’m logged out. Am I missing something?

Mike Boyink

by Mike Boyink (Author)

Date: Tuesday, June 2nd, 2009
Comment: #34

Hey Kris -

Make sure the images/captcha directory permissions are set to 777.

Picture of kris Utter

by kris Utter

Date: Friday, June 5th, 2009
Comment: #35

Thanks for the quick response. I noticed that I didn’t have the permissions correct in the Comment Posting Preferences. Great tutorial!!!!

Picture of Ryan Lenerz

by Ryan Lenerz

Date: Friday, October 2nd, 2009
Comment: #36

I am working through this lesson to add comments to a website and have found that I am running into the same issue comment #8 spoke of - namely that your embed uses <div class=“comment_field”> but the CSS sheet you attached to comment #9 above does not contain that class.

Also, I have the same exact issue as comment #25 above.  It appears that the browser is not reading any of the code inside the {exp:comment:form} brackets.

The post I am trying to comment on allows comments, the weblog allows commenting and I stripped out the conditions for being logged in.

What might be going wrong?

Picture of Ryan Lenerz

by Ryan Lenerz

Date: Friday, October 2nd, 2009
Comment: #37

I figured out my issue.  For comments to work, the string {exp:comment:form} has to know which weblog and enty_id it is attached to.  I first hard-coded {exp:comment:form weblog=“my_blog” entry_id=“12”} and found that it all worked.  From there, I worked backwards to make sure the parameters were being passed correctly so that I could remove my hard-coding.

Picture of olliejen

by olliejen

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

Hi Mike,

  I have an easy question;

I do not have the send-button.gif image file in the src path, hence no pretty button.

<input type=“image” class=“comment_submit” src=”{site_url}images/interface/send-button.gif” name=“submit” value=“Submit” />

I have an interface folder, but it’s empty.  When is this folder created/populated?

TIA,
—oliver.

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, June 30th, 2010
Comment: #39

Hey Oliver - that happened in chapter 1 (Upload the Template Images).

Mike Boyink

by Mike Boyink (Author)

Date: Wednesday, June 30th, 2010
Comment: #40

Eh - sorry.  Chapter 6.

Picture of olliejen

by olliejen

Date: Thursday, July 1st, 2010
Comment: #41

Holy cats, what a space cadet I am!  I’m 33% following along, 33% cherry-picking to get our church’s site close to the wireframe pin, and 34% figuring it out as I go along, so apologies for the scatterbrained Q. 

Helpful isn’t even the right word for this series; EE GPS for Dummies is closer, but not quite right either.  Thank you so much!

Picture of Bryan

by Bryan

Date: Wednesday, September 29th, 2010
Comment: #42

Hey Mike,

Can you please provide me with the “embeds/html_header” file?

Picture of Dan

by Dan

Date: Thursday, October 7th, 2010
Comment: #43

Hi Mike,

Thanks a lot for the great tutorials. I have (what I hope to be) a simple question.

I am creating a guestbook. I thought it would be as simple as creating a weblog, allowing comments to the weblog and displaying the comments? Is this so?

Unfortunately, I have found it really hard to find documentation on creating a commenting form for a weblog, not sure if you have any advice or links for commenting and displaying comments on weblogs?

I have tried to manipulate your above tutorial to do this but have not had much success.

Thanks,
Dan

Picture of Edwin

by Edwin

Date: Sunday, May 1st, 2011
Comment: #44

Great Tutorial. Thanks so much.

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>