After updating from K2 2.6.7 to 2.6.8 (Joomla 2.5.19) the "Item must have a title" notice loads on the screen whenever a front-end user either creates or edits an existing item. It happens before the item form content fully displays.

This occurs on items that have been in the database (with a title) for months, and did not occur before the update to 2.6.8.

This message should only display if the user tries to save/submit the form without an entry in the title field, not before the form loads.

If the form is saved without a title, a 404 error displays in the modal window instead of the "Item must have a title" notice.

Any clues on what changes in 2.6.8 might be causing this error?

Thank you.

Hi. Do you have any third-party K2 plugins installed? Do you use any SEF extension? Also check your page for javascript errors. Finally ensure that you have not any overrides to the itemforn.php.

Re the 'item must have a title' error

this is caused by the submit button function being triggered as the modal popup closes and opens when the title has no value - this can be changed or removed in the itemform.php template override. Clearly there is a script conflict somewhere but I cannot find it.

I 'fixed' it by wrapping the offending if statement in another if statement as below, so the alert could only trigger on save. Hope this helps figure out what the problem is...

$document->addScriptDeclaration("
Joomla.submitbutton = function(pressbutton){
if (pressbutton == 'cancel') {
submitform( pressbutton );
return;
}
if (pressbutton == 'save') { // HERE is the extra condition that I wrapped the offending condition in
if (\$K2.trim(\$K2('#title').val()) == '') {
alert( '".JText::_('K2_ITEM_MUST_HAVE_A_TITLE', true)."' );
}
else if (\$K2.trim(\$K2('#catid').val()) == '0') {
alert( '".JText::_('K2_PLEASE_SELECT_A_CATEGORY', true)."' );
}
else {
syncExtraFieldsEditor();
\$K2('#selectedTags option').attr('selected', 'selected');
submitform( pressbutton );
}
} // obviously close the extra if statement
}
");

Hi! same issue, I found the problem here was "Little Helper in Status" module from "Little Helper" admin tools.
Just unpublished it and everything is fine again.

Just for the record.

@Luciano

Thanks for the feedback.

Hello,

I just stumbled upon this post thanks to a user notification, and fixed the issue in the latest 2.1.4 version of LittleHelper, which includes also the new favicon drag n crop features.

You may download it on fasterjoomla.com .

Please do inform the developers of any issue you find: unless you let them know, they won't be able to fix stuff. And it's always appreciated when you let us improve our software.