September 2009 Archives

For many years, Adobe Contribute has been able to connect to commercially available popular blogging platforms such as Blogger or TypePad. I use Movable Type on my own server, and have wanted to get this going for some time.

There are a couple of configuration settings that make this all pretty easy, although the answers as to how to set them is not in one place. This entry serves as the one place.

First of all, you need to have Contribute CS4 installed, and your Movable Type blog needs to be up and running. You will need administrative access to the blog and to the paths where the cgi lives. With these in hand, we need to gather some information before making the connection.

Open your Movable Type administration panel and click on your name in the upper right hand corner. This will open your profile.

Having opened your profile, scroll down to the Preferences and click the reveal button to the right of the web services password. Write this down or copy it to your clipboard, as you will need it to connect to your blog.

Now, it's time to fire up Contribute. From Contribute, choose Contribute>My Connections... and select Create. Next, choose Blogs as the type of connection, and enter the URL for your blog.

You can also browse to your blog, which will open a little web browser for you. Browse to the top level of your site, and then click OK.

Click Continue to enter the connection settings, and this is where that password will come in handy. On this screen, you need to enter your userid, the web services password (not your regular login password), and the access point path.

The access point path is the path to where the Movable Type cgi files live. In my installation, I simply installed the entire MT folder in a folder on my web site, and created a second folder for the posted blog entries. This is pretty common, as most of us don't have access to the system-wide cgi folder. The item that's important is the file called mt-xmlrpc.cgi, which is the bit of glue that binds Movable Type and Contribute together. Having entered these three items, you are done. Click Finish to create the connection.

Having made the connection, you are ready to add or edit entries. There are some preferences you might want to set before you do, however.

Choose Contribute>Preferences and then select the Blog Defaults panel. You can choose to automatically allow comments and trackbacks here, and to create a new entry when you click the "New" button.

Under the Tagging panel, you may want to put the tags at the bottom of your entries so as not to clutter up the top. Contribute will automatically push your tags to the repositories you specify in the panel. Having made these changes, click OK.

Now, you're ready to blog with Contribute!

To create a new entry, click New Entry, or choose an existing entry from the menu at the right of the screen. This isn't about how to use Contribute to edit blog entries, so I'll leave that to you and your favorite training source.

I will say, though, that I enjoy seeing the blog entry rendered with the CSS and template of the blog. I also like the asset manager in Contribute, which consists of adding a picture to your blog entry, and Contribute will manage the rest. You can also use that built-in browser to browse to pages when adding links to your blog. That's handy when you can't remember the precise url, but you know the site that you want to reference.

If you need to set the entry aside, click Save for Later and then it will be available for you later to pick up where you left off. When you're ready to publish the entry, click Publish, and Contribute does all of the publishing for you.

Enjoy!

,,

A week of frustration followed my attempt at upgrading my XServe G5 Dual Processor from Tiger Server to Leopard Server. Silly me, I made the bold assumption that Apple would have the decency to leave the underlying server parts untouched and add their secret sauce for blogs, ical, collaboration, and the like, on top of what was proven. What do I mean by proven, you ask?

How about perl, or PHP, or MySQL? I used to have a perfectly acceptable Movable Type blog (this one, in fact) running happy as a clam on this server. I had never been able to get ImageMagick to properly install, though, as well as some convenience modules like Compress, but hey, Leopard was going to make everything all better. However, when we (props to my son Arthur, whose patience and tenacity led to success) "upgraded," nothing worked anymore. The web is full of complaints about various pieces of this puzzle, so I will leave it up to you to go digging. As for my blog and other data-driven and dynamic graphics-based sites that used to reside on this server, they were defunct. Dead. Doornail dead.

GD is important, as is DBI, DBI::MySql, ImageMagick, PerlMagick, and others. Without them, the Blog just doesn't go. Of course, the major technologies like MySQL and PHP are essential, but the versions provided by Apple were either just plain broken, or were inadequate for the tasks at hand. Of course, we reinstalled!

MySQL and PHP installers are available and we installed them according to the clear instructions provided by MySQL.com and Marc Liyanage, respectively. The tricky part was getting the built-in PHP to shut off and the new one to turn on, but judicious application of the "refresh view" button on the server manager cured that.

Then we turned to MacPorts to install the additional modules. What a disaster.  Not MacPorts, mind you, it performed admirably. None of the ports we installed appeared in the list of installed perl modules, despite getting successful reports from MacPorts. I admit that after a few days of banging my head against the wall, I had had enough. Giving up, we scrapped Leopard Server and went back to Tiger Server. But, we were still without some modules.

It turns out that Apple's installation location for the remaining items is not where the rest of the world expects them to be. In the case of perl, when we check our version with CPAN, it reports that we have the current version of perl, and that our modules are installed. We were successfully able to install modules, and they all appear to install without issue, except for PerlMagick, which reports a whole pile of errors. More on that later. When we run the mt-check.cgi from the Movable Type installation, however, we get paths to multiple perl installs, none of which are the current version. Clearly, there is some major confusion here.

The solution turns out to be easy: ditch Apple's mangled perl distribution and put in a link to the good, current installation in its place. The following two lines in the terminal move the old perl installation to a safe place where it can do no harm, and then create the appropriate symbolic link to the /opt/local/bin/perl folder, where we have all of our modules installed.

sudo mv /usr/bin/perl /usr/bin/perl.orig
sudo ln -s /opt/local/bin/perl /usr/bin/perl

Voila! All of my modules are now installed and available to MovableType. GD, DBI, DBI::MySQL, Compress, and all of the others we were lacking, except for PerlMagick.

Even though we used Ports successfully to install ImageMagick, PerlMagic fails, and it fails because of Apple's path problem. So, to install, download the tarball, then follow the instructions. Here's the key, though. 

Remember the /opt/... directory? In the makefile.pl file, locate the LIBS and INC entries and change "usr/" to "opt/" in all of the path references in those two lines. Then, build as normal. Double voila!

Now, everything works as we expect it to. I can upload images and get thumbnails, I can connect to databases from my web sites and blog, and I believe that I can detect the aroma of rose coming from the exhaust fans of the XServe right about now.
I spent some time with DimDim the other day. It's a low cost online collaboration platform based on Flash. It hopes to compete with Adobe Acrobat Connect Pro or Webex, but in my opinion, it's not ready for prime time. They have a good start, though, and I can see lots of possibilities for the platform. Education users have glommed on to it for its price point, which is low. As to whether it will ever be taken seriously by enterprise users remains to be seen.
My middle son, Teddy, brought home a permission form today that we must sign. This form permits him to watch President Obama's message to schools in school. I wonder how many of these forms were printed at how many schools across the nation. Honestly, folks, this is insanity. When I was a kid, when the President spoke, you listened. In school or at home, it made no difference. Respect of the office trumped politics, and truthfully, whether you were in the President's party or not didn't matter a whit, because what he had to say would have an impact on you personally. Period.

And I grew up with Richard Nixon, Gerry Ford and Jimmy Carter!
I am a Parallels Desktop user, and have been for many years. I have noticed that Parallels has been getting pokier over time, and even commented on this to my good friend, Joe Cerro, last week. Almost in response to my griping, Parallels goes and releases an update at the end of August, that automatically installed yesterday for me.

Wow! What a difference. The "unsuspending" process, which used to take two to ten minutes AFTER the VM had been restored, now is almost instantaneous, and files and applications start right up. If I notice anything else, I'll try to note it here.
I upgraded my MacBook's RAM from 2 GB to 3GB in anticipation of Snow Leopard. I haven't done the SL upgrade yet, but I am enjoying the overall performance improvement with the additional RAM. This particular MacBook won't see more than 3.3GB of RAM, so I opted to have asymmetry in the RAM sticks in favor of volume. It was a good choice.

Most noticeable is the improvement in Parallels. I upped the VM RAM to 1300 MB from 1000 MB, and whoosh! the machine runs cooler and faster due to reduced paging. Parallels has its max capacity (2148MB) allocated to it for overhead. I am sure there is some optimal tuning to be done, but that's a task for later.
Last week while working with a customer while riding the Amtrak Downeaster between Boston and Portland, Maine, I created a Version Cue CS4-based PDF review. This process has always worked great in CS3 and Acrobat 8, and this was my first attempt with Acrobat 9 and Version Cue CS4. Platform disclaimer: ALL MAC Leopard, CS4 & Acrobat 9. All up to date as is the OS. Network is DHCP on the train.

The review creation process went without a hitch, and I was able to log into the VersionCue server, open the PDF in the browser, add comments to the PDF, and exit the browser. I then opened the PDF again in the browser, logged in as another user, applied some more comments, and exited the browser. When I tried to open the PDF from the VersionCue management console (open PDF in Acrobat is the button), however, the PDF opened in the browser and I saw no comments. 

Intrigued, I tried to see whether the review had been added to my Tracker, and when I opened the Tracker, I was presented with a dialog asking if it was OK for Acrobat to use the keychain item related to the VC server. I agreed, and that's the last I saw of the Tracker. 

Now, the Tracker won't start up. Occasionally I got these keychain messages from Acrobat, so I assume that the Tracker was still trying to connect to the VC server, but I can't see the Tracker. Well, having uninstalled and reinstalled Acrobat in hopes that the Tracker might reset itself, and after discovering that Acrobat conveniently remembers all of the reviews with which it is associated even after a reinstall, I dug around and found the following file on my Mac:

 ~user/Library/ApplicationSupport/Adobe/Acrobat/9.0_x86/Collab/Workflows 

I found the browser-based review that was causing the problems and changed the server ip address to localhost, where the VersionCue server resides regardless of its DHCP situation. Restarting Acrobat, though, and Tracker would still not appear.

I had resolved to confuse the hell out of Adobe tech support, when another idea occurred: join another shared review (not browser-based review like VersionCue). So, I joined another shared review, and Acrobat opened and voila! the Tracker reappeared, but then died after I tried to delete the dead review from the list. Thinking more about this, I restarted Acrobat and disabled "Show Notification inside Acrobat" in Preferences>Tracker, and opened the Tracker. Now, the Tracker did not try to connect to the bad server, and I was able to try deleting the bad browser-based reviews. Selecting one of the bad browser-based reviews, I clicked the trash can and got this handy message:
DeleteAcrobatSharedReviewBadServer.png
Without any guidance from the interface, I decided to go for broke and chose "OK." It was the right choice. The bad Browser-based review is gone, and my Tracker is back. 

Lessons learned: don't try to start a browser-based review on a train.

About this Archive

This page is an archive of entries from September 2009 listed from newest to oldest.

August 2009 is the previous archive.

October 2009 is the next archive.

Find recent content on the main index or look in the archives to find all content.