Technology Tools for Ministry

Community

Web-Empowered Church Developer's Community
All Categories > Developers > Extensions > wbloggar
Total Posts: 4 - Pages (1): [1]
Author: David Frazee
Posted: Apr 16 2008 - 12:41 PM
Subject: wbloggar
I'm getting a "server name cannot be resolved" error when I try to use wbloggar. The tutorial gives the example "/sandbox/index.php?id=100&type=200". My id for blog=81, single=82 and storage folder=83. The url when I clicked on the spyglass tool was http://www.cogkc.org/index.php?id=81. Is "/index.php?id=81" the path to the API endpoint? Which is whatever page timtab is loaded? In the template tool for the blog page, the path at the top is "Path: /Church of God K.../Our Community/Cog Blog/"? And the blog url when you scroll down is "{$constants.wec.siteURL}community/blog/", which I'm going to assume "{$constants.wec.siteURL}" retrieves the site url. How do all these relate? There is a community folder in fileadmin, but there isn't any blog folder within.

Thanks
Author: Jeff Segars
Posted: Apr 16 2008 - 12:54 PM
Subject: re: wbloggar
Hey David,
The key to the whole thing is the type=200 on the end. Each page that you see within the backend can have multiple types attached to it. The default type (0) is used to render the pages that a visitor to your site sees. You can also set up custom page types for printer friendly pages, RSS feeds, podcasts, and other things. It's basically an easy way to re-use the content on the page in a slightly different format and can be set up by a site administrator or an extension developer. In the case of type=200, it has been defined by the TIMTAB developer as the page type that listens for external blogging applications on a page where TIMTAB is already configured.

In your specific example, page id 81 is your main blog page and type 200 is the API page type. This means, you'll you'll want to point wblogger at index.php?id=81&type=200. You can also usee cogkc.org/community/blog/?type=200 and cogkc.org/community/blog/xmlrpc. These all end up at the same place but are variations on the original URL because of RealURL. The last one I listed is probably the most user friendly one to use.

Hope that helps get you started

Jeff
Author: Peter Schott
Posted: Apr 16 2008 - 01:00 PM
Subject: re: wbloggar
Here's an extract from my settings that may help you. Note that I've modified a couple of the settings - login, password, host name. Also, I'm using an alias of "blog" for my main blog page. This could easily be your id=### for your blog. You may also need to check the <page> setting as this ties to the actual location. If you're running on the root of your server, you should be good with this.

The only other oddity I've found with TIMTAB and blogging programs is the way the categories are configured. I eventually just used the same text for the Title and Description and it seemed to work okay. Without that I had unexpected behavior an awful lot where some external blogging apps would read the data and others would not.

FYI - I also had pretty good success with Windows Live Writer and came to prefer that a little bit as it does the job really well on a Windows machine.

-Pete


<blog>0</blog>
<alias>WEC Blog</alias>
<user>YourLoginHere</user>
<password>YourEncryptedPasswordHere</password>
<savepassword>1</savepassword>
<pingweblogs>0</pingweblogs>
<cms>0</cms>
<service>0</service>
<host>www.yourhost.org</host>
<page>/index.php?id=blog&type=200</page>
<port>80</port>
<secure>0</secure>
<postmethod>1</postmethod>
<getpostsmethod>1</getpostsmethod>
<categmethod>3</categmethod>
<templatemethod>0</templatemethod>
<multicategory>1</multicategory>
<titletag1><title></titletag1>
<titletag2></title></titletag2>
<categtag1><category></categtag1>
<categtag2></category></categtag2>
<moretexttag1><more_text></moretexttag1>
<moretexttag2></more_text></moretexttag2>
<timeout>30</timeout>
<useproxy>0</useproxy>
<proxyserver />
<proxyport>0</proxyport>
<proxyuser />
<proxypassword />
<deleted>0</deleted>
Author: David Frazee
Posted: Apr 17 2008 - 12:46 PM
Subject: re: wbloggar
Thanks Pete,

That worked. I didn't think that mattered after reading about it in part 3 of the tutorial.

"We add additional information here to test if the blog is accepting posts from an external editor. &type=200 is added to the address bar."

Good call on Live Writer.

You said there were some oddities with the categories. My archive menu works fine, but the category menu gets the following error message.

"Firefox can't find the server at {plugin.tx_timtab.homepid}"

So I figured the category menu wasn't pointed at the right page, but the return page was pointed at the main page at 81 and single was fine. So I cleared the cache, but I'm still getting the same results. So I figured I'd check in the settings.
The constants seemed fine.

plugin.tx_timtab.title = Pastor's Blog
plugin.tx_timtab.homepage = {$constants.wec.siteURL}community/blog/
plugin.tx_timtab.tagline = Pastor's Blog
plugin.tx_timtab.blogPid = 82
plugin.tx_timtab.homePid = 81
plugin.tx_timtab_pi2.pidStorePosts = 83
plugin.tx_timtab_pi2.pidStoreComments = 83
plugin.tx_timtab_pi2.enableBlogger = 1
plugin.tx_timtab_pi2.enableMetaWeblog = 1

So I checked the Settings

# ve_guestbook
plugin.tx_veguestbook_pi1 {
templateFile = {$page.file.template_ve_guestbook}
limit = 1000
sortingDirection = asc
_LOCAL_LANG.default {
form_firstname = Name
form_submit = Submit Comment
form_email = Mail
form_homepage = Website
}
_CSS_DEFAULT_STYLE >
}

# tt_news
plugin.tt_news {
templateFile = {$page.file.template_tt_news}
singlePid = {$plugin.tx_timtab.blogPid}
displayList.subheader_stdWrap.stripHtml = 0
dontUseBackPid = 1
catTextMode = 3
newsAmenuUserFunc =
useHRDates = 1
useSubCategories = 1
limit = 10

displayCatMenu {
mode = timtab
catmenu_stdWrap.wrap >
}
}

plugin.tx_timtab {
displayCatMenu.targetPid = {plugin.tx_timtab.homePid}
displayCatMenu.showCount = 0

gravatar.defaultImg = {$constants.wec.siteURL}/clear.gif
gravatar.size = 23
}

#list all posts of the current month when in archive
[globalVar = GP:tx_ttnews|year > 0]
plugin.tt_news.limit = 100
[global]
[globalVar = GP:tx_ttnews|ps > 0]
plugin.tt_news.limit = 100
[global]

# Provide an autodiscovery link to the RSS feed for news.
page.headerData.500 = TEXT
page.headerData.500 {
typolink.parameter = {$plugin.tx_timtab.homePid},100
typolink.returnLast = url
wrap = <link rel="alternate" type="application/rss+xml" title="RSS Feed" href="{$constants.wec.siteURL}|" />
}

# Provide an autodiscovery link to the XMLRPC pingback.
page.headerData.510 = TEXT
page.headerData.510 {
typolink.parameter = {$plugin.tx_timtab.homePid},200
typolink.returnLast = url
wrap = <link rel="pingback" href="{$constants.wec.siteURL}|" />
}

# advertise that we can receive Pingback
page.config.additionalHeaders = X-Pingback: {$plugin.tx_timtab.homepage}/xmlrpc


I changed displayCatMenu.showCount = 0 to 1, but that just showed how many were in each category; which makes sense now that I know that.

I'm fairly sure it's something in the settings, but I haven't found it.

-David
Total Posts: 4 - Pages (1): [1]
You must login to post a message to this conference.