Das eez kaput! Sometime around 2002 I spaced the entire database table that mapped individual entries to categories. Such is life. What follows is a random sampling of entries that were associated with the category. Over time, the entries will be updated and then it will be even more confusing. Wander around, though, it's still a fun way to find stuff.
What's really telling in this example is that the community promptly hacked their own uglier version of mixed content back into RSS, even though the original developers had tried to avoid it.
A "trailing slash" redirect is issued when the server receives a request for a URL http://servername/foo/dirname where dirname is a directory. Directories require a trailing slash, so mod_dir issues a redirect to http://servername/foo/dirname/.
Dude, where's my cookie?style messages. Unfortunately, the only thing anyone seems to be saying in response is :
Dude, just delete your cookies!Sure, thanks Wonder Bread. Anyway, eventually it dawned on me to actually look at the cookie and I discovered that the
Path
field contains a fully formed URI. Which explains why the cookies are
failing but not why they're being set incorrectly. Line 374 of
MT::App.pm reads :
if ($path =~ m!^https?://[^/]+(/.*)$!i) {
where $1 (the first set of matching brackets : that would be everything
after the first forward slash
following
the standard URI
[insert protocol here]://
stuff) is assigned as your cookie's
Path
. Which means that unless your Movable Type
CGIPath
config variable contains a trailing slash, the program will seriously
bork your cookies. DWIM-ing and user-centric idiot-proofing aside, I am
inclined to think that this is a documentation bug rather than a
problem with the code. Apache happens to do
"trailing slash" redirectsout of the box which is nice but probably not reason enough to expect every other web programmer to do the same thing. Now you know.
Why, why do I know how to do all of this shit?These stylesheets extend those included with the XML Résumé Library to add better support for external links and to support a small number of elements that are not part of the DTD.
http_proxy
-ing hooks to Net::Blogger now too...
rssUpdate
method. As always, while waiting for the CPAN listings to update, you
can grab a copy
over here
. see also :
docs
;; This packages enables you to create new posts and edit old posts on ;; your Movable Type Weblog. It may be expanded so that any weblog ;; tool that supports the metaWeblog API can be used.
sub main {
my $mt = Net::Blogger->new(engine=>"movabletype");
$mt->Proxy("http://yaddayadda.com/mt-xmlrpc.cgi");
$mt->Username("asc");
$mt->Password("*****");
$mt->BlogId(123);
$mt->newPost(postbody=>\&fortune(),publish=>1)
|| croak $mt->LastError();
my $id = $mt->metaWeblog()->newPost(title=>"test:".time,
description=>&fortune(),
publish=>1)
|| croak $mt->LastError();
my $categories = $mt->mt()->getCategoryList()
|| croak $mt->LastError();
my $cid = $categories->[0]->{categoryId};
$mt->mt()->setPostCategories(postid=>$id,
categories=>[{categoryId=>$cid}])
|| croak $mt->LastError();
print &Dumper($mt->mt()->getPostCategories(postid=>$id));
return 1;
}
sub fortune {
local $/;
undef $/;
system ("fortune > /home/asc/tmp/fortune");
open F, "</home/asc/tmp/fortune";
my $fortune = <F>;
close F;
return $fortune;
}
We will get a common API, one of these days, by hook or by
crook...Collude \Col*lude"\, v. i. [imp. & p. p. {Colluded}; p. pr. & vb. n. {Colluding}.] [L. colludere, -lusum; col- + ludere to play. See {Ludicrous}.] To have secretly a joint part or share in an action; to play into each other's hands; to conspire; to act in concert. If they let things take their course, they will be represented as colluding with sedition. --Burke. web1913
collude v : act in unison or agreement; "These two factors conspired to cause the stock market to fall" [syn: {conspire}] wn
That said, I'm considering the additional of an embed tag (except that it's not a very good name) for version 1.1 of the DTD. The syntax, attributes and children would be the same as the xref element, except that there would be no expectation that the thingy on the other end is an otlml widget. How it is rendered would be left up to whatever is rendering the parent document; this would be a good place for individual document types to define entity declarations/attributes.see also : <xsl:if test = "@style"> and XLink, Who Cares?
ReCIPprocal--for drinking situations.
ex. Our drinking was resiprocal at the party.
An obviously too tight piece of clothing.
ex. Come on, that`s a bit of gripper. We don`t want to see that.see also : gripper dict-ified
print sightly( { Shape => 'camel', SourceFile =>
'helloworld.pl', Regex => 1 } );
"