Skip to content

Magento module that finds redundant entries in mysql table core_config_data

Notifications You must be signed in to change notification settings

jhoelzl/JH_RemoveRedundantConfig

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

38 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Build Status

JH_RemoveRedundantConfig

Magento Module that finds redundant entries in mysql table core_config_data.

If you have different config settings for default, website or store scope in Magento backend, maybe after some time you will end up in having obsolete and redundant settings for website and store scope that have the same value as the default scope. This module finds the duplicate entries and adds the ability to remove them through a cronjob or a script.

This module could be useful to improve data quality in table core_config_data when you are monitoring your Magento instances (test, dev, prod) through an external tool.

Installation

  • Install the extension via GitHub, Composer, modman or a similar method. The extension is listed on packages.firegento.com.
  • Clear the cache, logout from the admin panel and then login again.
  • Enable/Disable automatic deletion of obsolete settings under System > Configuration > Developer > JH_RemoveRedundantConfig Settings.

Usage

  • First, test which entries are obsolete with the php script under shell directory in your magento directory:
 cd shell 
 php redundant_settings.php --action findSettings

The command lists all paths and config_ids which are redundant. If the output is correct, you can enable the cronjob (runs once per hour) under System -> Configuration > Developer > JH_RemoveRedundantConfig Settings or run the command:

 cd shell 
 php redundant_settings.php --action removeSettings

In the log file var/log/removed_obsolete_config_ids.log, you can find all config_id values that were removed by the module.

Improvements

Feel free to make a pull request when you have ideas for improving. Further improvement could be an extended log file were the whole entry that was removed is stored, not only the config_id.

Uninstallation

  • Fia FTP: Remove all extension files from your Magento installation
  • Via modman: modman remove JH_RemoveRedundantConfig
  • Via composer, remove the line of your composer.json related to jh_removeredundantconfig
  • Optional: Remove entry with path "dev/jh_removeredundantconfig/status" from table core_config_data

About

Magento module that finds redundant entries in mysql table core_config_data

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages