Support » Plugin: XML Sitemap & Google News » Error: An invalid form control with name=’xmlsf_priority’ is not focusable.

  • Resolved joneiseman

    (@joneiseman)


    This was reported 6 months ago. But I still see the problem even if I uncheck XML sitemaps in the screen options. When this plugin is enabled I am unable to update some older posts when using the classic editor. Clicking on the Update button does nothing and I get this error in the console:
    Error: An invalid form control with name=’xmlsf_priority’ is not focusable.
    Disabling this plugin fixes the problem.
    The problem only appears in some posts.
    Using the new block editor with the classic block works fine.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author RavanH

    (@ravanh)

    Hi @joneiseman thanks for reporting. To be sure, you are using plugin version 5.2.3 or later? It should have been fixed there… If you are using the latest version, then apparently in your case it is still happening.

    Problem is that I cannot reproduce the issue. Is there any chance I can take a look at it on your site? You’d have to create a temporary account for me and describe which post to edit so I can see exactly what is happening. If you would allow that, it’d be very helpful 🙂 Please contact me directly via https://status301.net/contact/ for the details (don’t publish them here!)

    Plugin Author RavanH

    (@ravanh)

    Question:

    But I still see the problem even if I uncheck XML sitemaps in the screen options.

    Are you saying when XML Sitemap is CHECKED in the screen options, the error appears too? That’s very strange…

    I’m saying that whether XML Sitemap is checked or not checked, I am unable to update the post and I get the error in the console. Only disabling the plugin allows me to update the post. I created an account for you with the Editor role so you can see the problem.

    Plugin Author RavanH

    (@ravanh)

    Thanks 🙂 see my response via email for details. Are you using the plugin https://wordpress.org/plugins/tabify-edit-screen/ by any chance? It seems to interfere with the normal Screen Options settings…

    Yes, you’re right, the problem was related to the tabify-edit-screen plugin. I removed that plugin and that solved the problem 🙂
    Once I did that, when I tried to update the post it jumped down to the “Priority” field for XML Sitemaps and I found it had the value 0.0. Once I removed the 0.0, I was able to update the post. When XML Sitemaps is not enabled in Screen options it’s not able to jump down to the field with the problem and it just prevents the update without showing the field.

    Plugin Author RavanH

    (@ravanh)

    When XML Sitemaps is not enabled in Screen options it’s not able to jump down to the field with the problem and it just prevents the update without showing the field.

    Indeed. Now with Tabify disabled, you’ll be able to make the XML Sitemap meta box show and you’ll no longer have the error. In the next release there will be a fix that will prevent the “0.0” appearing at all 🙂

    Thank you for your feedback and the opportunity to debug !

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.