Hi evasion, I’m having trouble duplicating and seeing the problem.  Can you walk me through the steps to reveal the error?

In fact after a few test it doesn’t block the form (apologizes), but there’s still a javascript error.

Here’s two hints :

When enabling date tabs with comments disabled there is a javascript error :

document.getElementById(“comment_expiration_date”) is null

I guess the javascript is inserted altough comment are disabled (so comments expiration date isn’t displayed in the date tab).

When disabling both date tabs and comments for a weblog, there’s another javascript error :

update_calendar is not defined

This bug is related here : http://expressionengine.com/bug_tracker/bug/5211/

It’s not really critical, but javascript errors are bad anyway

By the way the blocked form problem appeared like this :

- Edit default weblog custom fields preferences
- Changed summary from text area to input text

It automaticly changed char limit to 0.

It’s not really a bug, but a quick fix to automaticly put it to some standard value (ie: 255) would help other people I hope.

Yes, javascript errors are bad, which is why I’m wanting to know the exact steps required to reproduce.  It’s possible that the fix put in place for when the date tab is disabled addresses the issue you’re seeing, but I’d rather not make assumptions.

When you say ‘comments are disabled’, do you mean the “Allow comments in this weblog?” setting in the Weblog Preferences?  Or do you have ‘Display Option Buttons’ set to no in your publish page preferences?

The ‘update_calendar’ error is indeed fixed per the bug report you link to.  However, I still cannot reproduce the error you are seeing, and I’m not certain that they would be related.  What version and build are you using, and are you running any extensions?  When comments are disabled, the comment_expiration_date field is still written, as a hidden input field, so I don’t see how the JS error would occur.

In fact there’s some hidden input named “comment_expiration_date” with no id specified :

<input type=‘hidden’ name=‘comment_expiration_date’ value=’’ />

Steps :
- Edit weblog preferences : Admin›Weblog Administration›Weblog Management›Edit Weblog
- Go to “Comment Posting Preferences”
- Allow comments in this weblog? tick “no”
- Go to “Publish Page Customization”
- Check if “Display Date Fields” is yes
- Go to Publish > new entry, or edit an existing entry.

I’m using latest EE release 1.6.4, latest build (downloaded yesterday to keep it up to date).

Comments module is not installed, but I’ve tried to reinstall it and same problem.

Thanks evasion, I overlooked a separate fix made in the subversion for this very bug report that was fixed internally.