[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$feZaeeOiT_-4OmLvADRJKv7ZusmceCMXUS5x20yVh_qU":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":8,"trust_score":10,"computed_at":11,"plugins":12},"greencp","Bjoern","https:\u002F\u002Fprofiles.wordpress.org\u002Fgreencp\u002F",2,30,85,84,"2026-04-04T23:08:31.204Z",[13,35],{"slug":14,"name":15,"version":16,"author":5,"author_profile":6,"description":17,"short_description":18,"active_installs":19,"downloaded":20,"rating":21,"num_ratings":7,"last_updated":22,"tested_up_to":23,"requires_at_least":24,"requires_php":25,"tags":26,"homepage":30,"download_link":31,"security_score":9,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"dynamic-links","Dynamic Links","0.2","\u003Cp>When inserting an image into a posts WordPress uses absolute urls (i.e. including domain name) for the src and href attributes of the image and associated link. This leads to problems if you change your domain (e.g. when moving from test to production environment) or if you change the base path of your upload directory. Also usage of relative URLs (i.e. absolute path to file without domain part) can reduce file size, but may not be used in feeds.\u003C\u002Fp>\n\u003Cp>Dynamic Links replaces all links to files in the upload directory with a placeholder which is replaced again with the base path to the upload dir when the content is viewed. This way image links are dynamically adapted to changes in domain name or upload base path.\u003C\u002Fp>\n\u003Cp>As additional option relative links can be used when content is display on your site to reduce page size (Though there are better options to do this. It’s just included because it’s possible). Images and links in feeds will always get the full path.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This program is free software; you can redistribute it and\u002For modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation.\u003Cbr \u002F>\nThis program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.\u003C\u002Fp>\n","Makes links to files in upload directory of wordpress in posts (e.g. images) \"dynamic\". Allows use of relative image URLs in Posts and makes …",20,3912,100,"2014-01-24T17:27:00.000Z","3.7.41","3.2","",[27,28,29],"dynamic-image-links","images","relative-urls","http:\u002F\u002Fwww.bjoernahrens.de","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdynamic-links.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":41,"downloaded":42,"rating":32,"num_ratings":32,"last_updated":43,"tested_up_to":44,"requires_at_least":45,"requires_php":25,"tags":46,"homepage":52,"download_link":53,"security_score":9,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"fast-translate","Fast Translate","1.4","\u003Cp>Changing the WordPress site language to any other than English slows down page generation times. A lot. This is caused by the slow and inefficient way of text domain loading. PO and MO files are designed to be used with PHP Gettext-extension. But since it’s an extension, it’s not installed by defalt on very hosting platform. To overcome this barrier, WordPress has re-implemented the whole MO file parsing in PHP, but WordPress’ implementation is quite slow and memory intense.\u003C\u002Fp>\n\u003Cp>This plugin replaces the default MO-Reader with another implementation of MO parsing, which is faster than the default one. Only used text domains are loaded (since version 4.6 this is also WordPress’ default behaviour) and from these only used translations are loaded. It also makes use of hash tables included in mo files, which are ignored completely by WordPress’ default implementation. To boost the performance even more, the plugin also caches translations to the object cache, if one is installed. For optimal performance you need a fast object cache backend like Redis, Memcached or APC(u).\u003C\u002Fp>\n\u003Cp>Fast Translate is a minimalistic fork of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-performance-pack\" rel=\"ugc\">WP Performance Packs\u003C\u002Fa> localization improvements. \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-performance-pack\" rel=\"ugc\">WP Performance Pack\u003C\u002Fa> offers additional control and more optimizations for WordPress performance, e.g. use of PHPs native gettext extension, improved image handling and CDN support.\u003C\u002Fp>\n","Faster WordPress localization with cache support.",10,3827,"2019-12-12T10:14:00.000Z","5.3.21","4.0",[47,48,49,50,51],"l10n","localization","performance","speed","translation","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffast-translate","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffast-translate.zip"]