How to disable updates in WordPress themeChild theme grabbing wrong location fo parent theme filesRemoving parent theme CSS without editing parent themeGive priority to child theme stylesheetCreating a child theme after numerous edits to parent themeStrange Theme Error - parent style occasionally showing though child themeUpdating my Wordpress.org version will cause my site to break… What can I do to avoid this?If a theme will undergo major changes would it be better to clone the parent instead of writting a child theme?WordPress Child Theme PHP Code Change IssuesWant to create Child theme, but already edited Parent theme css files and some php filesAbout wordpress child themes

Preventing the ears from getting clogged on descent to Barcelona

Plot irregular circle in latex

All numbers in a 5x5 Minesweeper grid

Lumens specs when buying a flashlight/torch. Why maglite has only 680lm but cheap ones have 900,000?

What is Cousin Itt in The Addams Family?

Carroll's interpretation of 1-forms

Can we have a C++ function with multiple return types? ( C++11 and above)

How often is duct tape used during crewed space missions?

Is there an in-universe reason Harry says this or is this simply a Rowling mistake?

Social Encounters in a West Marches Campaign

What is the origin of the “clerics can create water” trope?

How long to wait to change jobs after closing on a home

Why would a fighter use the afterburner and air brakes at the same time?

Is it safe to put a microwave in a walk-in closet?

Why do we need to use transistors when building an OR gate?

Can I separate garlic into cloves for storage?

Plausibility and performance of a composite longbow

Amiga 500 OCS/ECS vs Mega Drive VDP

How would you design and build an American Civil War Steam Gun?

What exactly is a web font, and what does converting to one involve?

Is a global DNS record a security risk for phpMyAdmin?

Did slaves have slaves?

Very lazy puppy

Secondary characters in character-study fiction



How to disable updates in WordPress theme


Child theme grabbing wrong location fo parent theme filesRemoving parent theme CSS without editing parent themeGive priority to child theme stylesheetCreating a child theme after numerous edits to parent themeStrange Theme Error - parent style occasionally showing though child themeUpdating my Wordpress.org version will cause my site to break… What can I do to avoid this?If a theme will undergo major changes would it be better to clone the parent instead of writting a child theme?WordPress Child Theme PHP Code Change IssuesWant to create Child theme, but already edited Parent theme css files and some php filesAbout wordpress child themes






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















I am working on a WordPress website. Earlier before me, there was one another guy has worked on that website.



Now he has done all his changes in parent theme without creating a child theme. Now, what should I do to prevent updating theme?



Also, I know it is nearly impossible but If anybody can suggest me any step to separate both changes. that would be more helpfull.



Theme is twentyseventeen










share|improve this question
































    2















    I am working on a WordPress website. Earlier before me, there was one another guy has worked on that website.



    Now he has done all his changes in parent theme without creating a child theme. Now, what should I do to prevent updating theme?



    Also, I know it is nearly impossible but If anybody can suggest me any step to separate both changes. that would be more helpfull.



    Theme is twentyseventeen










    share|improve this question




























      2












      2








      2








      I am working on a WordPress website. Earlier before me, there was one another guy has worked on that website.



      Now he has done all his changes in parent theme without creating a child theme. Now, what should I do to prevent updating theme?



      Also, I know it is nearly impossible but If anybody can suggest me any step to separate both changes. that would be more helpfull.



      Theme is twentyseventeen










      share|improve this question
















      I am working on a WordPress website. Earlier before me, there was one another guy has worked on that website.



      Now he has done all his changes in parent theme without creating a child theme. Now, what should I do to prevent updating theme?



      Also, I know it is nearly impossible but If anybody can suggest me any step to separate both changes. that would be more helpfull.



      Theme is twentyseventeen







      child-theme updates






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 28 at 12:54









      fuxia

      94.9k13 gold badges195 silver badges379 bronze badges




      94.9k13 gold badges195 silver badges379 bronze badges










      asked Mar 28 at 12:23









      hardikhardik

      133 bronze badges




      133 bronze badges























          3 Answers
          3






          active

          oldest

          votes


















          6
















          First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked.



          So the long-term solution would be to:



          1. Check the version of modified theme.

          2. Download that version from official repository.

          3. Compare the original files with modified ones.

          4. Create a child theme containing only necessary modifications.

          If you need to disable the updates for a few days, there is an easy way to do it - just change the version of your theme to 9.9.9 - WordPress will think that it is newer than the one in repository and it won't get updated. (BUT... Don't think of this hack as a solution - it's just a dirty temporary fix and you still should perform the process from points above).






          share|improve this answer
































            2
















            I would agree with what Krzysiek already said - you should first be using a child theme (which is incredibly simple to set up, so there's zero reason not to do this as a best practice) and that avoiding theme updates is a recipe for eventual disaster (that goes for plugins and core, too).



            That being said, while changing the version number to a ridiculously high value is a workable and very simple solution, it doesn't really avoid updates if the developer actually releases something above that version - or if they change their version numbering to something non-standard.



            Here's an alternative method that handles it via the update transient. The first example would just disable all theme updates (assuming you don't have other themes installed that you DO want to allow updates for):



            add_filter( 'site_transient_update_themes', 'remove_update_themes' );
            function remove_update_themes( $value )
            return null;



            If you want to do this for just a specific theme, then you need to search the response value for your theme's slug:



            add_filter( 'site_transient_update_themes', 'remove_update_themes' );
            function remove_update_themes( $value )

            // Set your theme slug accordingly:
            $your_theme_slug = 'your-theme-slug';

            if ( isset( $value ) && is_object( $value ) )
            unset( $value->response[ $your_theme_slug ] );


            return $value;






            share|improve this answer

























            • We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

              – Krzysiek Dróżdż
              Mar 28 at 13:19


















            1
















            If the question is to prevent editing the theme (and plugins) directly through the editor. You can make the following changes through wp-config.php



            1. Open up your wp-config.php file in a text editor.


            2. Anywhere above the line in that file that says



              /* That's all, stop editing! Happy
              blogging. */



            add the line define( 'DISALLOW_FILE_EDIT', true );.



            1. Save and upload the file. Check your WordPress dashboard, you should no longer
              see (even on an Administrator account), the links at “Appearance >
              Editor” and “Plugins > Editor”.





            share|improve this answer

























            • ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

              – Rick Hellewell
              Mar 28 at 17:43













            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "110"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );














            draft saved

            draft discarded
















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f332837%2fhow-to-disable-updates-in-wordpress-theme%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            6
















            First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked.



            So the long-term solution would be to:



            1. Check the version of modified theme.

            2. Download that version from official repository.

            3. Compare the original files with modified ones.

            4. Create a child theme containing only necessary modifications.

            If you need to disable the updates for a few days, there is an easy way to do it - just change the version of your theme to 9.9.9 - WordPress will think that it is newer than the one in repository and it won't get updated. (BUT... Don't think of this hack as a solution - it's just a dirty temporary fix and you still should perform the process from points above).






            share|improve this answer





























              6
















              First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked.



              So the long-term solution would be to:



              1. Check the version of modified theme.

              2. Download that version from official repository.

              3. Compare the original files with modified ones.

              4. Create a child theme containing only necessary modifications.

              If you need to disable the updates for a few days, there is an easy way to do it - just change the version of your theme to 9.9.9 - WordPress will think that it is newer than the one in repository and it won't get updated. (BUT... Don't think of this hack as a solution - it's just a dirty temporary fix and you still should perform the process from points above).






              share|improve this answer



























                6














                6










                6









                First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked.



                So the long-term solution would be to:



                1. Check the version of modified theme.

                2. Download that version from official repository.

                3. Compare the original files with modified ones.

                4. Create a child theme containing only necessary modifications.

                If you need to disable the updates for a few days, there is an easy way to do it - just change the version of your theme to 9.9.9 - WordPress will think that it is newer than the one in repository and it won't get updated. (BUT... Don't think of this hack as a solution - it's just a dirty temporary fix and you still should perform the process from points above).






                share|improve this answer













                First of all, it is a very bad idea to modify the original theme without creating a child theme. Disabling updates of such theme is even worse idea, because without updates, your site may get infected or attacked.



                So the long-term solution would be to:



                1. Check the version of modified theme.

                2. Download that version from official repository.

                3. Compare the original files with modified ones.

                4. Create a child theme containing only necessary modifications.

                If you need to disable the updates for a few days, there is an easy way to do it - just change the version of your theme to 9.9.9 - WordPress will think that it is newer than the one in repository and it won't get updated. (BUT... Don't think of this hack as a solution - it's just a dirty temporary fix and you still should perform the process from points above).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 28 at 12:42









                Krzysiek DróżdżKrzysiek Dróżdż

                20.3k7 gold badges36 silver badges55 bronze badges




                20.3k7 gold badges36 silver badges55 bronze badges


























                    2
















                    I would agree with what Krzysiek already said - you should first be using a child theme (which is incredibly simple to set up, so there's zero reason not to do this as a best practice) and that avoiding theme updates is a recipe for eventual disaster (that goes for plugins and core, too).



                    That being said, while changing the version number to a ridiculously high value is a workable and very simple solution, it doesn't really avoid updates if the developer actually releases something above that version - or if they change their version numbering to something non-standard.



                    Here's an alternative method that handles it via the update transient. The first example would just disable all theme updates (assuming you don't have other themes installed that you DO want to allow updates for):



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )
                    return null;



                    If you want to do this for just a specific theme, then you need to search the response value for your theme's slug:



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )

                    // Set your theme slug accordingly:
                    $your_theme_slug = 'your-theme-slug';

                    if ( isset( $value ) && is_object( $value ) )
                    unset( $value->response[ $your_theme_slug ] );


                    return $value;






                    share|improve this answer

























                    • We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                      – Krzysiek Dróżdż
                      Mar 28 at 13:19















                    2
















                    I would agree with what Krzysiek already said - you should first be using a child theme (which is incredibly simple to set up, so there's zero reason not to do this as a best practice) and that avoiding theme updates is a recipe for eventual disaster (that goes for plugins and core, too).



                    That being said, while changing the version number to a ridiculously high value is a workable and very simple solution, it doesn't really avoid updates if the developer actually releases something above that version - or if they change their version numbering to something non-standard.



                    Here's an alternative method that handles it via the update transient. The first example would just disable all theme updates (assuming you don't have other themes installed that you DO want to allow updates for):



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )
                    return null;



                    If you want to do this for just a specific theme, then you need to search the response value for your theme's slug:



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )

                    // Set your theme slug accordingly:
                    $your_theme_slug = 'your-theme-slug';

                    if ( isset( $value ) && is_object( $value ) )
                    unset( $value->response[ $your_theme_slug ] );


                    return $value;






                    share|improve this answer

























                    • We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                      – Krzysiek Dróżdż
                      Mar 28 at 13:19













                    2














                    2










                    2









                    I would agree with what Krzysiek already said - you should first be using a child theme (which is incredibly simple to set up, so there's zero reason not to do this as a best practice) and that avoiding theme updates is a recipe for eventual disaster (that goes for plugins and core, too).



                    That being said, while changing the version number to a ridiculously high value is a workable and very simple solution, it doesn't really avoid updates if the developer actually releases something above that version - or if they change their version numbering to something non-standard.



                    Here's an alternative method that handles it via the update transient. The first example would just disable all theme updates (assuming you don't have other themes installed that you DO want to allow updates for):



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )
                    return null;



                    If you want to do this for just a specific theme, then you need to search the response value for your theme's slug:



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )

                    // Set your theme slug accordingly:
                    $your_theme_slug = 'your-theme-slug';

                    if ( isset( $value ) && is_object( $value ) )
                    unset( $value->response[ $your_theme_slug ] );


                    return $value;






                    share|improve this answer













                    I would agree with what Krzysiek already said - you should first be using a child theme (which is incredibly simple to set up, so there's zero reason not to do this as a best practice) and that avoiding theme updates is a recipe for eventual disaster (that goes for plugins and core, too).



                    That being said, while changing the version number to a ridiculously high value is a workable and very simple solution, it doesn't really avoid updates if the developer actually releases something above that version - or if they change their version numbering to something non-standard.



                    Here's an alternative method that handles it via the update transient. The first example would just disable all theme updates (assuming you don't have other themes installed that you DO want to allow updates for):



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )
                    return null;



                    If you want to do this for just a specific theme, then you need to search the response value for your theme's slug:



                    add_filter( 'site_transient_update_themes', 'remove_update_themes' );
                    function remove_update_themes( $value )

                    // Set your theme slug accordingly:
                    $your_theme_slug = 'your-theme-slug';

                    if ( isset( $value ) && is_object( $value ) )
                    unset( $value->response[ $your_theme_slug ] );


                    return $value;







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 28 at 13:12









                    butlerblogbutlerblog

                    2,4322 gold badges15 silver badges29 bronze badges




                    2,4322 gold badges15 silver badges29 bronze badges















                    • We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                      – Krzysiek Dróżdż
                      Mar 28 at 13:19

















                    • We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                      – Krzysiek Dróżdż
                      Mar 28 at 13:19
















                    We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                    – Krzysiek Dróżdż
                    Mar 28 at 13:19





                    We're talking about twentyseventeen, so I don't think they will change the version numbering ;) But yes - your solution will work just fine. The only problem I have with it - base on my experience - it tends to be less temporary fix ;)

                    – Krzysiek Dróżdż
                    Mar 28 at 13:19











                    1
















                    If the question is to prevent editing the theme (and plugins) directly through the editor. You can make the following changes through wp-config.php



                    1. Open up your wp-config.php file in a text editor.


                    2. Anywhere above the line in that file that says



                      /* That's all, stop editing! Happy
                      blogging. */



                    add the line define( 'DISALLOW_FILE_EDIT', true );.



                    1. Save and upload the file. Check your WordPress dashboard, you should no longer
                      see (even on an Administrator account), the links at “Appearance >
                      Editor” and “Plugins > Editor”.





                    share|improve this answer

























                    • ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                      – Rick Hellewell
                      Mar 28 at 17:43















                    1
















                    If the question is to prevent editing the theme (and plugins) directly through the editor. You can make the following changes through wp-config.php



                    1. Open up your wp-config.php file in a text editor.


                    2. Anywhere above the line in that file that says



                      /* That's all, stop editing! Happy
                      blogging. */



                    add the line define( 'DISALLOW_FILE_EDIT', true );.



                    1. Save and upload the file. Check your WordPress dashboard, you should no longer
                      see (even on an Administrator account), the links at “Appearance >
                      Editor” and “Plugins > Editor”.





                    share|improve this answer

























                    • ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                      – Rick Hellewell
                      Mar 28 at 17:43













                    1














                    1










                    1









                    If the question is to prevent editing the theme (and plugins) directly through the editor. You can make the following changes through wp-config.php



                    1. Open up your wp-config.php file in a text editor.


                    2. Anywhere above the line in that file that says



                      /* That's all, stop editing! Happy
                      blogging. */



                    add the line define( 'DISALLOW_FILE_EDIT', true );.



                    1. Save and upload the file. Check your WordPress dashboard, you should no longer
                      see (even on an Administrator account), the links at “Appearance >
                      Editor” and “Plugins > Editor”.





                    share|improve this answer













                    If the question is to prevent editing the theme (and plugins) directly through the editor. You can make the following changes through wp-config.php



                    1. Open up your wp-config.php file in a text editor.


                    2. Anywhere above the line in that file that says



                      /* That's all, stop editing! Happy
                      blogging. */



                    add the line define( 'DISALLOW_FILE_EDIT', true );.



                    1. Save and upload the file. Check your WordPress dashboard, you should no longer
                      see (even on an Administrator account), the links at “Appearance >
                      Editor” and “Plugins > Editor”.






                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 28 at 15:46









                    Ray MitchellRay Mitchell

                    79911 silver badges29 bronze badges




                    79911 silver badges29 bronze badges















                    • ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                      – Rick Hellewell
                      Mar 28 at 17:43

















                    • ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                      – Rick Hellewell
                      Mar 28 at 17:43
















                    ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                    – Rick Hellewell
                    Mar 28 at 17:43





                    ...unless the (IMHO brain-dead) developer uses FTP to update the files... Although turning off editing is a good idea, again IMHO.

                    – Rick Hellewell
                    Mar 28 at 17:43


















                    draft saved

                    draft discarded















































                    Thanks for contributing an answer to WordPress Development Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwordpress.stackexchange.com%2fquestions%2f332837%2fhow-to-disable-updates-in-wordpress-theme%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

                    Swift 4 - func physicsWorld not invoked on collision? The Next CEO of Stack OverflowHow to call Objective-C code from Swift#ifdef replacement in the Swift language@selector() in Swift?#pragma mark in Swift?Swift for loop: for index, element in array?dispatch_after - GCD in Swift?Swift Beta performance: sorting arraysSplit a String into an array in Swift?The use of Swift 3 @objc inference in Swift 4 mode is deprecated?How to optimize UITableViewCell, because my UITableView lags

                    Access current req object everywhere in Node.js ExpressWhy are global variables considered bad practice? (node.js)Using req & res across functionsHow do I get the path to the current script with Node.js?What is Node.js' Connect, Express and “middleware”?Node.js w/ express error handling in callbackHow to access the GET parameters after “?” in Express?Modify Node.js req object parametersAccess “app” variable inside of ExpressJS/ConnectJS middleware?Node.js Express app - request objectAngular Http Module considered middleware?Session variables in ExpressJSAdd properties to the req object in expressjs with Typescript