Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[2759,2275,9151,3866,2552],"plugin_category":[43],"plugin_contributors":[283696],"plugin_business_model":[],"class_list":["post-375997","plugin","type-plugin","status-publish","hentry","plugin_tags-customization","plugin_tags-developer","plugin_tags-diff","plugin_tags-merge","plugin_tags-update","plugin_category-customization","plugin_contributors-maximebakernsn","plugin_committers-maximebakernsn"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/naroum-update-merge.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Editing a third-party plugin is sometimes the only way to get what a client needs. The problem comes with the next update: installing it overwrites your changes, and skipping it leaves security fixes behind.<\/p>\n\n
Naroum Update Merge solves this with a three-way merge, the same approach version control tools use. It compares:<\/p>\n\n
Because it knows the original, it can tell what you changed from what the update changed:<\/p>\n\n
For each conflict you choose which code to keep: my version, the new version, both (in either order), or the original version. The tool only combines code that already exists in these versions; it does not let you type code. To adjust the result by hand, download the merged ZIP, edit it, and install it with Plugins > Add New > Upload Plugin.<\/p>\n\n
Agencies and developers who maintain client sites with customized plugins and want a reviewable, reversible update process instead of redoing their changes by hand.<\/p>\n\n
The tool is available under Plugins > Update Merge, to users who can install and update plugins. It is unavailable when This plugin connects to WordPress.org only when you choose a WordPress.org source in the analysis form. Nothing is sent automatically or in the background.<\/p>\n\n No personal data is sent. Only the plugin slug and version number are part of the requests. WordPress.org Terms of Service<\/a> and Privacy Policy<\/a>.<\/p>\n\n\n In Direct installation is disabled in that case. Download the merged ZIP and install it from Plugins > Add New > Upload Plugin.<\/p><\/dd>\n Download it from the Backups section of the tool, then upload it from Plugins > Add New > Upload Plugin and choose to replace the current version.<\/p><\/dd>\n No. Only plugins installed in their own folder are supported.<\/p><\/dd>\n Disable automatic updates for customized plugins on the Plugins screen. After each installation, the tool reminds you to check this setting.<\/p><\/dd>\n Yes, with the DISALLOW_FILE_MODS<\/code> is set. On multisite, it is in the network admin.<\/p>\n\nExternal services<\/h3>\n\n
\n
api.wordpress.org<\/code> (Plugins API) is queried with the plugin slug to find the download link of the latest release.<\/li>\ndownloads.wordpress.org<\/code> is used to download the latest release, or the original release matching the installed version number.<\/li>\n<\/ul>\n\n\n
naroum-update-merge<\/code> folder to \/wp-content\/plugins\/<\/code>. On multisite, network activate it.<\/li>\n\n
Where are the working files stored?<\/h3><\/dt>\n
wp-content\/uploads\/naroum-update-merge\/<\/code>: ongoing analyses (deleted after 3 days), backups and saved references. The folder is protected with an .htaccess<\/code> file and random folder names. On Nginx, add a rule denying access to this path. Everything is removed when you delete the plugin.<\/p><\/dd>\nWhat if my host requires FTP credentials to install plugins?<\/h3><\/dt>\n
How do I restore a backup?<\/h3><\/dt>\n
Does it handle single-file plugins?<\/h3><\/dt>\n
My changes were overwritten by an automatic update.<\/h3><\/dt>\n
Can I limit the archive size?<\/h3><\/dt>\n
naroum_um_max_unzipped_bytes<\/code> filter (500 MB by default).<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n