Frontend "Save" button not working

Question

I have Joomla 3.4.3 with the standard protostar template for the frontend. When my site is offline and I'm logging into the frontend (not the adminstrator backend), then I can browse and edit articles.

When I try to save the article by clicking the Save button, nothing happens. The Cancel button does work. On further inspection I found out that there is an

Uncaught TypeError: Cannot read property 'isValid' of null

that is thrown at the outer if condition

Joomla.submitbutton = function(task)
{
    if (task == 'article.cancel' ||
        document.formvalidator.isValid(document.getElementById('adminForm')))
    {
        if (tinyMCE.get("jform_articletext").isHidden()) {tinyMCE.get("jform_articletext").show()};
        Joomla.submitform(task);
    }
}

I tried finding some solution or related issues, but the only thing that turned up between the clear you browser cache kind of noise was this old issue in an akeeba bug report:

• Formvalidation broken in Joomla 3.2.rc1 #199

Any ideas what I can do to fix the issue?

Update

It seems that this issue only affects my "About me" article, which is the default article you see when you navigate to my site. Other articles don't seem to have this problem and I can save them from within the front-end.

Answer 1

I can't reproduce this on a clean install with protostar and TinyMCE.

Is it happening only when site is offline?
On all pages, or on a few or only a single page?

If it's only on a specific pages, see what other extensions exist on that page as it can be a conflict with these. Disable those extensions, clear caches and try again.

Also make sure you have error displaying and debugging set to off when you are trying, as this sometimes may be the cause of such issues.

Answer 2

According to the error, document.formvalidator (media/system/js/validate.js) is not instantiated.

This may be caused by a Javascript conflict in the page or a loading error.

Check if you have any browser console error (for example, a conflict caused by a third-party tinyMCE plugin) or any issue loading the Javascript file.

Answer 3

Funnily enough we had this occur yesterday on a site we're migrating from 2.5 to 3.4.2 (in that case it occurred after updating the template to a point release that came out yesterday).

Clearing both Joomla's cache and the browsers cache resolved the problem for us.

Answer 4

I'm unable to replicate your problem at my end, even by editing the featured and first article. I'd suggest you to delete that About Me article and recreate it again.