2 added 5 characters in body
source | link

Best practice: Just revert the commit of the security update in your version control (e.g. git). If you say "we don't use version control" you should should fix that issue first :)

I would prefer to keep the security patch in your system and you should try to determine why your extensions aren't working anymore. In the most cases you have missed some important things which haven't been that important before the update.

Summary:

  • Use version control
  • Apply all patches to your installation
  • NeverNo need to remove a security patch (since there is no reason)
  • Don't be lazy and fix your extensions to work with the current (and most secure) environment
  • Never change the core...

Best practice: Just revert the commit of the security update in your version control (e.g. git). If you say "we don't use version control" you should should fix that issue first :)

I would prefer to keep the security patch in your system and you should try to determine why your extensions aren't working anymore. In the most cases you have missed some important things which haven't been that important before the update.

Summary:

  • Use version control
  • Apply all patches to your installation
  • Never remove a security patch (since there is no reason)
  • Don't be lazy and fix your extensions to work with the current (and most secure) environment
  • Never change the core...

Best practice: Just revert the commit of the security update in your version control (e.g. git). If you say "we don't use version control" you should should fix that issue first :)

I would prefer to keep the security patch in your system and you should try to determine why your extensions aren't working anymore. In the most cases you have missed some important things which haven't been that important before the update.

Summary:

  • Use version control
  • Apply all patches to your installation
  • No need to remove a security patch (since there is no reason)
  • Don't be lazy and fix your extensions to work with the current (and most secure) environment
  • Never change the core...
1
source | link

Best practice: Just revert the commit of the security update in your version control (e.g. git). If you say "we don't use version control" you should should fix that issue first :)

I would prefer to keep the security patch in your system and you should try to determine why your extensions aren't working anymore. In the most cases you have missed some important things which haven't been that important before the update.

Summary:

  • Use version control
  • Apply all patches to your installation
  • Never remove a security patch (since there is no reason)
  • Don't be lazy and fix your extensions to work with the current (and most secure) environment
  • Never change the core...