So, I recently updated to MT 4.23 and created a new blog from this installation. I imported a bunch of content and all is well, but for some problems with the commenting system.

Initially, there was some problems using the default mt-comments document in that the URL ended up adding the path from one account to the end of the domain name that was being used in this installation. so I changed the "comments" template from this:



to this



So, now the comments fields appear. However, while I've got the comments setting to "Immediately approve comments from anyone" (and I've republished the site) but I'm still getting a registration error on the confirmation page.

Any ideas?

I'm the brother of the person posting the above query.

The site in question is mine:
http://www.masterstrack.com/

Just FYI:
We made sure that our comment glitch wasn't the same as this one:
http://forums.sixapart.com/index.php?showtopic=67553

Thanks for any guidance!

Latest wrinkle:

The problem is in the MT installation being told to NOT require registration, but it still does. The commenting scripts may be working correctly.

Haven't yet found the document where that registration preference is stored.

Can anyone help on this?

First thing I can see is that www.masterstrack.com redirects to masterstrack.com




Can you post the content of mt-config.cgi (xxxx user names and passwords)

Note that the blog in question is not under the taurus account, but rather at:
/usr/home/mtf/public_html/

Well if you are under two different accounts that can be a problem as /taurus/cgi-bin/mt/ does not exist under /usr/home/kensone/public_html/, correct?

I would think you would have a problem creating a symbolic link between to the two accounts so that /usr/home/kensone/public_html/taurus/cgi-bin/mt/ points to taurus/cgi-bin/mt/

Correct, though both of these accounts are on the same server. This has not been a problem for all of the MT versions over the past few years. We've been running off this configuration (sharing the server, but not the account) for a few years and quite a few MT versions.



That's exactly why I hard coded the link to mt-comments.cgi in the comments template in the masterstrack.com blog. I wonder if anybody can think of another location where that link is not finding the correct document such that the blog will not respond to the "allow everybody to comment" without registration.

I guess what you're suggesting is that I install a separate MT for the mtf account and one for the myaccount account. I was hoping to avoid that, seems redundant to me. Any other ideas?

Thanks!
-al.

Even if both accounts are on the same server, they should not have access to each others file system. That sounds like a security risk, is this a dedicated server or are there other peoples accounts as well?


Is this the path you hardcoded? http://masterstrack.com/taurus/cgi-bin/mt/mt-comments.cgi

Yes there are other accounts there, though the webserver doesn't allow one to navigate "above" the account's web-space.



Nope, the hard coded path is http://wawrra.pair.com/myaccount/cgi-bin/mt/mt-comments.cgi

On http://masterstrack.com/blog/005302.html#comments the path is http://masterstrack.com/taurus/cgi-bin/mt/mt-comments.cgi, have you rebuild the blog?




Also if taurus can write to kensone what is stopping userb?

We've got a third party trying to figure this out too, and he removed the hard coded path to the mt-comments.cgi. I'm going to fix that right now. Go back to http://masterstrack.com/blog/005302.html#comments and it should work "right" but still not accept comments even though it is set to accept from everybody.




Not sure what "userb" is. As I recall, there's an option in the MT setup to publish outside of the web root, something like that. I kind of figured that all is well with this sort of set-up. I guess that publishing outside of the web root is for archives only, but if you can do it for archives, why not an entire blog?

Just did a test post and it seems to have gone through OK and displaying.

userb is just another user on the same server.

You're right, however I may have to comment out the preview button. That seems to be causing problems. Can you try that, make a test comment but preview first? The preview displays correctly, but when you click on "submit" from that page, you're directed to our default 404 page.

Thanks again!

In http://masterstrack.com/mt.js there are lot references to http://masterstrack.com/taurus/cgi-bin/mt/mt-comments.cgi. This file contains all the heavy lifting Javascript for comments and is in the JavaScript template.

You will also need to change the path in the comment preview system template

Okay, so there were two references in the mt.js file pointing to "<$mt:CGIPath$><$mt:CommentScript$>" which I replaced with the hard coded URL. However the problems with that preview page still exist.

I seem to remember there was an option somewhere to turn off that preview page. It's nice to have, but if it is breaking the script, we can do without. Any other ideas?

Have you changed the comment preview system template?

I did now, and everything is working correctly. Thanks, OtherNiceMan, you're a credit to your hemisphere!

Seems like I did a global search within the templates for that CGIPath at one point, intending to replace <$mt:CGIPath$><$mt:CommentScript$> with the hard coded path to the mt-comments.cgi script. Don't know why that didn't come up with the mt.js and Preview Comment templates. Ultimately, that's what did the trick.

Thanks again!
-al.

no problem, glad it is all working.

A gazillion thanks to everyone involved!

Although my blog is "just a hobby," it provides an essential feedback forum for the niche sports of masters track and field (geezer athletics).

I noted the comments comeback here:
http://masterstrack.com/blog/005302.html

MT blog software is incredible, and I'm grateful to this forum as well.

ken