11 Comments

  1. Ajay

    Fantastic plugin! I’ve been using a child theme for my website. The good part is the developer has made it with child themes in mind. However, one of the previous updates broke a few of my formatting elements on the site. Was quick to fix and it could have been worse.

    Report

  2. Ahmad Awais

    This is an incredible plugin. Tested it and installed it on a few sites, where I had been facing the same damn problem.

    Report

  3. David

    It is a great plugin! But we still need to raise awareness, themes should use a version header, so we are able to compare the versions of the parent and child templates.

    I haven’t checked, but somehow I doubt Avada as an example is using the version header?

    Report

  4. Mike

    ✅✔️?

    Report

  5. Vitor Madeira

    Great Scott! One has got to be “born again” from the moment you get to know such plugin. Ramen! :p

    Report

  6. Li-An

    Great plugin. Checking files with child themes updates was so frightening for me…

    Report

  7. Torsten Landsiedel

    Thank you very much for featuring our plugin :)

    But we still need to raise awareness, themes should use a version header, so we are able to compare the versions of the parent and child templates.

    This is true. It would be great if more theme devs would use that @version info in the header. And if you want to help me get this in the TwentySeventeen theme please watch this ticket:
    https://core.trac.wordpress.org/ticket/36972

    Report

  8. Tomas M.

    If we do not want “Theme Updates Induce Panic Attacks”, Theme Check Team should be more flexible. One thing comes to mind – do not force old themes to comply with the new rules that are not required for the security.

    In my example I have two themes with about 13K users. Now I was basically forced to change the text domain. Themes had numerous updates and suddenly I cannot submit update because there is a new rule, that requires text domain be the same as the theme slug. I was told that it is required for the new integration with translation service Glotpress, that I actually do not even use. I was also told that if I will not comply, theme may be dropped from the WP.org in the future.

    So let’s imagine what will happen for the international users after update – some fields will not be rendered in their language. Now it basically means that every one using a child theme (who cares if they have skills…) will have to go through functions.php and other files and change the text domain.

    It is sad, but that’s the price to be listed on WP.org…

    Report

  9. WPVKP

    I have tested it on some sites and it worked. But seems it sometimes break on sites with Genesis framework installed. After installing the plugin, the complete admin panel’s link becomes underlined. Might be conflict with some plugin. I will update once I find it out.

    Report

  10. Torsten Landsiedel

    The new Twenty Seventeen theme will be using the @version info for all PHP template files:
    https://github.com/WordPress/twentyseventeen/issues/72
    \o/

    Report

Comments are closed.

%d bloggers like this: