11th Apr, 2008

Errors! Gasp! Feedback!

It turns out that the 2.7 documentation has some “oversights”. Other people would call them errors but this a marketing pitch so I don’t say ‘dumb ass errors’. A courageous Manila site owner has been attempting to run the 2.7 MvManila scripts in OS X and he asked for some help. Of course, I’ll help. That’s almost as much fun as getting paid. Seriously.

Issue #1. It might not be clear in the documentation that RubyGems has to be installed. It’s not the easiest thing to install because you have to google the correct set of instructions for your particular OS & version. I’m not picking on OS X. It was a minor challenge for me to get Gems installed in Ubuntu Linux. Too many ways to do it, some of them wrong. It’s a challenge.

Issue #2. Fixurl.tcl will probably croak with an error message like (but not identical)

.....
can't read "msgmap(13)": no such element in array
    while executing
"set newnum $msgmap($msgnum)"
    ("while" body line 6)
    invoked from within
"while {[gets $sf line]>0} {
        set msgnum [lindex $line 0]
        set path [lindex $line 2]
        #puts stderr "$msgnum $path"
        if {$path != "stories"} {
                ..."
    (file "./fixurl.tcl" line 245)

I’ve seen this problem. The cure is to edit the ’structure’ file and remove the line with “nnn {About} about” where nnn is a different number for everyone. Then rerun fixurl.tcl.

You might ask ‘why don’t you fix the code and documentation’ instead of posting a blog entry? Do you want the long version or the short version?

Short Version:
It’s easier to delete that ‘about’ line in the structures file than to fix the scripts and documentation.

Long Version:
I don’t run the 2.7 scripts because I have 3.0 versions and you don’t. Actually, it’s real a bitch to test modifications to the 2.7 scripts without a live working Manila site to test against. There are fewer and fewer Manila sites wanting conversion. Only a fewer of the few will grant me access to test. That’s just how it is, the pool is drying up. It’s not worth the effort to make a 2.7.1. A business decision.

29th Jan, 2008

PhotoMv Dream

I had a brain cramp followed by some proof of concept coding accompanied by great gulps of learning.  The goal is to be able to move or convert your photo’s meta data around from website to website, one app to another, desktop to server and vice versa.  There’s a tie in to MvManila. Quite a few linkages if you have a blog on one server and a picture server somewhere else.  Or multiples of either and you want to move from one to another.  Keep the blog at a.b.c.com but move the photos from Flickr to Picassa or your own web server (or all of the above) and you want your blog posts fixed up to where the picture moved to. You’d also like to take you tags/keywords, categories, and comments with you. Perhaps merge them.

I have a design or scheme or architecture in mind. It’s early and it will change as needed by user feedback and actual practice. This  single page PDF  will give you the basic idea  if you don’t get all picky about the detail, or the presentation.

Version 2.7 of MvManila has been released. It features improved handling of newsItems, fewer bugs, support to find and get Gems. It even handles some reluctant Manila hosts better.

MvManila 2.7 documentation is now the current “Online Doc’s”. The older downloads have the older documentation inside should you need it.

MvManila 2.7 is probably last public release of MvManila unless there’s feedback. There are no plans to release Version 3.0 - It’s almost a complete rewrite, much more powerful and even more confusing for the average person.

Categories