<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
<rdf:Description
rdf:about="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>"
dc:title="<{$story.title}>"
dc:identifier="<{$xoops_url}>/modules/news/article.php?storyid=<{$story.id}>" />
trackback:ping="<{$xoops_url}>/cgi-bin/tb.cgi/storyid=<{$story.id}>"
</rdf:RDF>
-->
This may sound crazy, or it may sound brilliant, depending on how you look at it... but I'm trying to implement Standalone TrackBack with the News Module of [URL=https://xoops.org/]XOOPs[/URL] CMS. I'm about 3/4ths of the way to making it work, too!
However, I am having a small problem. The script does just fine sending OUT TrackBack pings (tested it on my MT blogs). I cannot, however, get it to receive TrackBack pings. When I try, I get this error:
[CODE]Ping 'http://www.mydomain.net/content/cgi-bin/tb.cgi/storyid_1' failed: HTTP error: 500 Can't connect to www.mydomain.net:80 (Timeout)[/CODE]
I've checked, double-checked, and triple-checked all CHMOD permissions (this is a Linux server running on Apache). Permissions are all correct. I've checked the htaccess file, it's fine. MT on this server works perfectly, too.
The variables I've assigned to TB (specific to XOOPs) are as follows:
[CODE]<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
<rdfescription
rdf:about="storyid=<{$story.id}>"
dc:title="itemtitle=<{$story.title}>"
dc:identifier="storyid=<{$story.id}>" />
trackback:ping="http://www.mydomain.net/content/cgi-bin/tb.cgi/storyid=<{$story.id}>"
</rdf:RDF>
-->[/CODE]
One thing that is questionable is the dc:title variable. It tends to output the Topic : Title of the News story in the form of two HTML'd links. I've posted at the XOOPs forum asking for clarification of what that variable should be, in the hopes that that might be the main problem. I haven't gotten a response yet (still waiting).
The other two variables (using the same itemid) work fine. They have to be in that format in order to output the proper ID for the News "story" otherwise they just output the variables themselves and that, obviously, won't work.
It also appears that Standalone TrackBack is not writing any files to the tb_data or tb_rss directories, as it should do. There is nothing preventing TB from doing so, as far as I can tell, there is just nothing in those directories. CGI scripts can (according to my webhosts) run from anywhere on the server. All Standalone TrackBack files are in the proper directories and permissions are set correctly, as stated in the installation instructions. When checking for the TB ping url on a specific News story, I do get the properly formatted popup window with the TB url listed there.
Needless to say, I am currently stumped at this point. 3/4ths of the way to implementing TrackBack in a branch of the 'nuke tree. If I could make this work, it would give CMS developers some idea of what TrackBack is all about, and possibly open up all those 'nuke branches to being able to build TrackBack into their CMS's, connecting them to the rest of the blog world. Personally, I think that would be fantastic.
If anyone can be of help to me, I'd very much appreciate it.
Aine
*I've obscured the name of the domain I'm working on to preserve my privacy until I get it ready to open to the public. There is currently nothing to be seen there anyway, just some Lorem Ipsum.
TrackBack ID : "storyid={<$storyid>}"
Entry Permalink : "storyid={<$storyid>}"
Entry Title : "???something???={<$story.title>}"
You will need to download your images that start with the cav, I think, and see if any of them are the images that you uploaded.
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
