Ggthjy

How did Arya survive the stabbing?

Why doesn't a table tennis ball float on the surface? How do we calculate buoyancy here?

Why Were Madagascar and New Zealand Discovered So Late?

What deity do celestials/aasimars worship?

Is there a good way to store credentials outside of a password manager?

How does buying out courses with grant money work?

Customer Requests (Sometimes) Drive Me Bonkers!

What grammatical function is や performing here?

Implement the Thanos sorting algorithm

Do sorcerers' Subtle Spells require a skill check to be unseen?

How to minimizeplan ahead the effect of running sp_delete_backuphistory? Measure the gains too!

Why use "finir par" instead of "finir de" before an infinitive?

How should I support this large drywall patch?

Fastest way to shutdown Ubuntu Mate 18.10

All SQL Server aliases linked to default instance instead of instance I assigned

'Given that' in a matrix

What does 算不上 mean in 算不上太美好的日子?

Trouble understanding the speech of overseas colleagues

What does "Its cash flow is deeply negative" mean?

Is a stroke of luck acceptable after a series of unfavorable events?

Lay out the Carpet

Increase performance creating Mandelbrot set in python

Would a high gravity rocky planet be guaranteed to have an atmosphere?

Grabbing quick drinks

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

1

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

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

1

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

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

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

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited 52 mins ago

fuxia♦

93k13185366

edited 52 mins ago

fuxia♦

93k13185366

asked 1 hour ago

hardikhardik

62

New contributor

hardik is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 1 hour ago

hardikhardik

62

2 Answers
2

active

oldest

votes

2

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

answered 1 hour ago

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

17.9k73246

add a comment | 

1

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

answered 34 mins ago

butlerblogbutlerblog

1,81121125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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ż
  27 mins ago
  

  
  
  
  

add a comment | 

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/3.0/"u003ecc by-sa 3.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
});


}
});

hardik is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

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

Name

Email

Required, but never shown

2

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

answered 1 hour ago

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

17.9k73246

add a comment | 

2

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

answered 1 hour ago

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

17.9k73246

add a comment | 

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

answered 1 hour ago

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

17.9k73246

share|improve this answer

answered 1 hour ago

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

17.9k73246

answered 1 hour ago

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

17.9k73246

answered 1 hour ago

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

17.9k73246

1

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

answered 34 mins ago

butlerblogbutlerblog

1,81121125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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ż
  27 mins ago
  

  
  
  
  

add a comment | 

1

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

answered 34 mins ago

butlerblogbutlerblog

1,81121125

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  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ż
  27 mins ago
  

  
  
  
  

add a comment | 

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

answered 34 mins ago

butlerblogbutlerblog

1,81121125

add_filter( 'site_transient_update_themes', 'remove_update_themes' );

function remove_update_themes( $value ) {

    return null;

}

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

answered 34 mins ago

butlerblogbutlerblog

1,81121125

answered 34 mins ago

butlerblogbutlerblog

1,81121125

answered 34 mins ago

butlerblogbutlerblog

1,81121125