Using 3.0D, I get the following error when posting a new Blog entry:

Use of uninitialized value in string eq at /var/www/localhost/cgi-bin/mt/lib/MT/Template/Context.pm line 762.

This could be caused by my Post_to_MT javascript, but before I dig in to it, has anyone else seen it?

TIA,

Woody

Kristine's been working a couple of these on our help tickets, and the QuickPost has come up both times I think in relation to it.

We've got an open bug report on it, and a developer offered this MySQL command as a possible fix:



Note that there are no guarantees offered here, so if you're not using MySQL or aren't comfortable with doing potential harm to your database, the error is just a warning and shouldn't affect performance while we look for the solid fix.

Do you have the checkbox for Allow Comments included in your QuickPost bookmarklet? If you do, create a new bookmarklet without it, and post at least one entry either through the regular interface or with the new bookmarklet (because the previous entry is involved), and then the next entry shouldn't get the errors (and should get your default setting for allow comments).

(Shelley: bug 1298)

Bump, also got this error, tried creating new quickpost without checking commentsopen as per philringnalda's post but TNA

the blog still works fine but the errors quite annoying

Eh, my "add two entries" thought was a little off: you'll still be rebuilding things like monthly and category archives and indexes that include those entries with null for allow comments. What you actually need to do is either change the nulls to 0 directly in the database, as Shelley said, or just edit and resave all the entries you've made through a bookmarklet, but in the regular interface this time. If you don't change anything, just edit, save, they'll get set to Comments: None, or you can change it to whatever suits you before saving.

My apologies for not getting back - I'm still looking at this. I get a similiar error when creating a new entry from the MT menu, but it may be a different line number in the error. Just finding time to spend any time on it is difficult!

The entries still go in fine, and I could easily turn off the perl warnings, but that would be cheating

If you guys come up with anything before I do, let me know!

Woody

Update: Tried this and it took care of all the problems. It turns out it was happening when I just did a site rebuild, or created a new entry or new quick entry. Ran the below sql and it updated 8 entries and it all went away.

Thanks!

Woody

Mt host does not support mysql dbase which yes I know is incredibly pants but there you go, anyway what does this mean for me as I am using the 'berkley standalone dbase' thingy (sorry I am not an expert) can i do the same thing?

I looked at my contex.pm file but i think the entry may have been different will update when i get home as no acccess to my files here.

cheers in advance for any suggestions