[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$frkJ2iNpr6HnYkYX5bc2_BGxHtU-eFGkbzekdzxzBQ5Q":3,"$fh_uFV8vHpAEjAoKHvCfaemAj_FQq4S3R-OBG0ReTySA":239,"$fJ7qxPcYlx5AD7iPOEq83xZzAjcbRP7pNyqslTFo5nAI":244},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"discovery_status":31,"vulnerabilities":32,"developer":33,"crawl_stats":29,"alternatives":40,"analysis":147,"fingerprints":191},"no-slug-conflicts-with-trash","No Slug Conflicts with Trash","1.2","Scott Reilly","https:\u002F\u002Fprofiles.wordpress.org\u002Fcoffee2code\u002F","\u003Cp>\u003Cstrong>NOTE: WordPress 4.5 incorporated the functionality of this plugin and thus it is no longer needed unless you’re still running an older version of WP.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin implements the belief that a trashed page or post should not in any way conflict with a new page or post when it comes to slugs. In essence, a new page or post should take precedence over anything in the trash. After all, the page\u002Fpost is in the trash for a reason.\u003C\u002Fp>\n\u003Cp>By default, WordPress takes into consideration posts and pages that have been trashed when deciding if the slug for a new post is already in use. Obviously, in general, WordPress should not allow duplicate slugs because that could interfere with permalinks. The thinking behind WordPress’s handling of the situation is that trashed posts\u002Fpages are still technically present, just inaccessible. It is possible that an author or admin would choose to restore a post from the trash, which WordPress feels should then occupy that same permalink as before it was trashed.\u003C\u002Fp>\n\u003Cp>If what WordPress does is unclear, here’s an example to help clarify things:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress ships with a page called “About” with the slug of “about”. The page’s URL would be http:\u002F\u002Fyoursite\u002Fabout\u002F\u003C\u002Fli>\n\u003Cli>Let’s say you trash that page and start a new page with the name “About”.\u003C\u002Fli>\n\u003Cli>Due to a trashed page having the slug that would normally have been assigned to the new page (“about”), the new page gets the slug of “about-2”, resulting in the page’s URL being http:\u002F\u002Fyoursite\u002Fabout-2\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With this plugin, for this example, the new “About” page would get the slug “about” as one would hope.\u003C\u002Fp>\n\u003Cp>That said, the plugin tries its best to restore untrashed posts to their original slug. The only time it fails to do so is if a new page or post has claimed the trashed post’s original slug, in which case the untrashed post is assigned a new slug.\u003C\u002Fp>\n\u003Cp>See other sections of the documentation for more insight into the plugin’s functionality. See WP core \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F11863\" rel=\"nofollow ugc\">ticket #11863\u003C\u002Fa> for discussion on the matter.\u003C\u002Fp>\n\u003Cp>Links: \u003Ca href=\"http:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fno-slug-conflicts-with-trash\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fno-slug-conflicts-with-trash\u002F\" rel=\"ugc\">Plugin Directory Page\u003C\u002Fa> | \u003Ca href=\"http:\u002F\u002Fcoffee2code.com\" rel=\"nofollow ugc\">Author Homepage\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>The Solution Explained\u003C\u002Fh3>\n\u003Cp>An overview of the approach employed by the plugin to resolve the issue of slugs potentially conflicting with posts in the trash.\u003C\u002Fp>\n\u003Ch4>What WordPress does\u003C\u002Fh4>\n\u003Cp>In order to understand the crux of the implemented solution, a quick refresher on unique slug handling by WP:\u003C\u002Fp>\n\u003Cp>Before published use, a desired slug is passed to \u003Ccode>wp_unique_post_slug()\u003C\u002Fcode> and a safe slug is returned. The safe slug may differ from the desired slug if any existing post (including a trashed post) has that slug (or, less likely, is invalid for permalink reasons such as feeds or date archives).\u003C\u002Fp>\n\u003Cp>In order to prevent a trashed post’s slug from conflicting with a new post, this plugin takes an approach that is comprised of two primary tasks:\u003C\u002Fp>\n\u003Ch4>1. Permit a post to use a slug that conflicts with a trashed post.\u003C\u002Fh4>\n\u003Cp>The plugin hooks the ‘wp_unique_post_slug’ filter. If the desired slug matches the safe slug, the desired slug is unique and nothing needs to be done.\u003C\u002Fp>\n\u003Cp>When the two slugs don’t match, it has to determine if the conflict is due to a trashed post or not, so it attempts to find a trashed post with the desired slug.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If no such trashed post is found, the conflict is with a live post (or was an otherwise unsuitable slug) so the safe slug must be used by the new post (so, again, nothing needs to be done).\u003C\u002Fli>\n\u003Cli>If such a trashed post is found, then the plugin simply inverses the traditional behavior of \u003Ccode>wp_unique_post_slug()\u003C\u002Fcode>: give the trashed post the safe slug and return the desired slug for use by the new post (rather than having the trashed post retain its slug and forcing the new post to use the safe slug). In order to be able to restore a trashed post to its original slug, the trashed post’s original slug is stored in postmeta.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2. Restore a trashed post to its original slug, if necessary and possible.\u003C\u002Fh4>\n\u003Cp>For a post transitioning away from the ‘trash’ post status, check to see if its slug was rewritten (denoted by the presence of the postmeta field only assigned if the original slug was changed due to a conflict while the post was in the trash).\u003C\u002Fp>\n\u003Cp>If there was no original slug, the slug was never changed and nothing more needs to happen.\u003C\u002Fp>\n\u003Cp>When there is an original slug, check to see if that slug is still in use by a non-trashed post.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If not, restore the post slug to the original value.\u003C\u002Fli>\n\u003Cli>If so, there is no recourse but to leave the post slug as-is (it is guaranteed to be unique already).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In either case, the postmeta field for the original slug value gets deleted since the now untrashed post is exposed in some fashion with its current slug and should abide by it going forward.\u003C\u002Fp>\n","NOTE: WordPress 4.5 incorporated the functionality of this plugin and thus it is no longer needed unless you're still running an older version of …",10,4151,100,2,"2016-06-26T17:01:00.000Z","4.4.34","3.5","",[20,21,22,23,24],"coffee2code","post","post_name","slug","trash","http:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fno-slug-conflicts-with-trash\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.2.zip",85,0,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":20,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},63,91830,88,374,71,"2026-05-20T00:34:58.937Z",[41,60,85,108,130],{"slug":42,"name":43,"version":44,"author":45,"author_profile":46,"description":47,"short_description":48,"active_installs":11,"downloaded":49,"rating":28,"num_ratings":28,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":57,"download_link":58,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":59},"random-post-name","Random Post Name","1.0","PRESSMAN","https:\u002F\u002Fprofiles.wordpress.org\u002Fpressmaninc\u002F","\u003Cp>Auto-generate a unique random string and set it to post_name.\u003C\u002Fp>\n\u003Ch4>Customization with hooks\u003C\u002Fh4>\n\u003Cp>Use of filter hooks is at your own risk.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>You can change post_type to be applied by an array. Deafult is ‘post’ only.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cpre>\nadd_filter( 'random_post_name_post_types', 'hoge' );\nfunction hoge(){\n    return ['post', 'page'];\n}\n\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>You can change the number of characters in the post_name. Deafult is 10.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cpre>\nadd_filter( 'random_post_name_digits', 'hoge' );\nfunction hoge(){\n    return 20;\n}\n\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>You can change the variation of characters. Deafult is ‘0123456789abcdefghijklmnopqrstuvwxyz’. Do not include multibyte chars.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cpre>\nadd_filter( 'random_post_name_choices', 'hoge' );\nfunction hoge(){\n    return '0123456789abcdefghijkmnpqrstuvwxyz_-';\n}\n\u003C\u002Fpre>\n\u003Ch3>Precautions\u003C\u002Fh3>\n\u003Cp>Too few characters and too few character variations can cause unexpected problems.\u003C\u002Fp>\n","Auto-generate a unique random string and set it to post_name. Customization with hooks Use of filter hooks is at your own risk.",965,"2020-06-12T11:13:00.000Z","5.4.19","5.4","7.1.24",[21,22,55,56,23],"pressman","ramdom","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Frandom-post-name\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frandom-post-name.zip","2026-04-16T10:56:18.058Z",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":13,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":80,"download_link":81,"security_score":82,"vuln_count":83,"unpatched_count":28,"last_vuln_date":84,"fetched_at":59},"remove-cpt-base","Remove CPT base","6.7","kubiq","https:\u002F\u002Fprofiles.wordpress.org\u002Fkubiq\u002F","\u003Cp>Remove custom post type base slug from url\u003C\u002Fp>\n\u003Cul>\n\u003Cli>possibility to select specific custom post type(s)\u003C\u002Fli>\n\u003Cli>auto redirect old slugs to no-base slugs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Yoast SEO specifics\u003C\u002Fh3>\n\u003Cp>If you’re using Yoast SEO plugin, after you change something in the Remove CPT base plugin, you should deactivate Yoast SEO and activate it back again to refresh its yoast_indexable database table, so it will generate correct og:url, canonical url and JSON-LD urls.\u003C\u002Fp>\n","Remove custom post type base slug from url",10000,97613,33,"2025-12-01T22:03:00.000Z","6.9.4","3.0","5.6",[76,77,78,79,23],"base","custom-post-type","permalink","remove","https:\u002F\u002Fwww.paypal.me\u002Fjakubnovaksl","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-cpt-base.6.7.zip",99,1,"2022-05-06 13:29:00",{"slug":86,"name":87,"version":88,"author":89,"author_profile":90,"description":91,"short_description":92,"active_installs":93,"downloaded":94,"rating":95,"num_ratings":96,"last_updated":97,"tested_up_to":72,"requires_at_least":98,"requires_php":99,"tags":100,"homepage":105,"download_link":106,"security_score":82,"vuln_count":83,"unpatched_count":28,"last_vuln_date":107,"fetched_at":59},"post-lockdown","Post Lockdown","4.0.5","andyexeter","https:\u002F\u002Fprofiles.wordpress.org\u002Fandyexeter\u002F","\u003Cp>Post Lockdown protects your site-critical pages and posts by disabling all non-admin users’ ability to trash or delete them.\u003Cbr \u002F>\nIt can also lock pages and posts, which will disable editing of the post as well as disabling trashing\u002Fdeleting.\u003C\u002Fp>\n\u003Cp>The plugin adds a new options page under the Settings menu in your WordPress admin panel which allows you to quickly search and\u003Cbr \u002F>\nselect for all pages and posts of any post type. When you find the item you want to select, simply click it to move it to the right\u003Cbr \u002F>\nbox and click Save Changes.\u003C\u002Fp>\n\u003Cp>See the screenshots for an example of what an Editor would see when they view a list of posts with some locked and protected.\u003C\u002Fp>\n","Allows admins to protect selected posts and pages so they cannot be trashed or deleted by non-admin users.",1000,22732,92,9,"2026-01-12T15:32:00.000Z","4.6","7.4",[101,102,103,104,24],"delete","lock","posts","protect","https:\u002F\u002Fgithub.com\u002Fandyexeter\u002Fpost-lockdown","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-lockdown.4.0.5.zip","2025-03-07 00:00:00",{"slug":109,"name":110,"version":111,"author":112,"author_profile":113,"description":114,"short_description":115,"active_installs":116,"downloaded":117,"rating":95,"num_ratings":118,"last_updated":119,"tested_up_to":120,"requires_at_least":121,"requires_php":18,"tags":122,"homepage":128,"download_link":129,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":59},"postname-permalink-auto-redirect","Postname Permalink Auto Redirect","1.1","fabioneves","https:\u002F\u002Fprofiles.wordpress.org\u002Ffabioneves\u002F","\u003Cp>Changed the permalink structure and don’t want to lose your SEO? You’re in the right place!\u003C\u002Fp>\n\u003Cp>This plugin will automatically redirect the old ‘%postname%’ permalink structure to the new one as long you keep the same slug in the posts. It works by searching posts by the slug name that comes in the request, so as long as you keep the post slug intact, it should be able to find the post and redirect to whatever new permalink it now is.\u003C\u002Fp>\n\u003Cp>Eg.:\u003Cbr \u002F>\nLet’s suppose you’re using ‘\u002F%postname%\u002F’ as your permalink structure, but after some time you find out it’s not a good structure (it’s not!) and you change it to ‘\u002F%category%\u002F%postname%\u002F’, the old links will now generate a 404 page, because there’s nothing there anymore.\u003C\u002Fp>\n\u003Cp>In this example your site is http:\u002F\u002Fmy-cool-domain.com and you have a post with the slug ‘my-cool-post’ under the category ‘news’. With the old ‘\u002F%postname%\u002F’ structure you would access this post with the URL:\u003Cbr \u002F>\nhttp:\u002F\u002Fmy-cool-domain.com\u002Fmy-cool-post\u002F\u003C\u002Fp>\n\u003Cp>With the new ‘\u002F%category%\u002F%postname%\u002F’ structure the URL will now be:\u003Cbr \u002F>\nhttp:\u002F\u002Fmy-cool-domain.com\u002Fnews\u002Fmy-cool-post\u002F\u003C\u002Fp>\n\u003Cp>But.. your old http:\u002F\u002Fmy-cool-domain.com\u002Fmy-cool-post\u002F is now generating a 404.\u003C\u002Fp>\n\u003Cp>Well, not anymore, “Postname Permalink Auto Redirect” to the rescue! The plugin will 301 redirect your http:\u002F\u002Fmy-cool-domain.com\u002Fmy-cool-post\u002F to http:\u002F\u002Fmy-cool-domain.com\u002Fnews\u002Fmy-cool-post\u002F automatically. You won’t lose your SEO and you’ll also tell the search engines that your page moved somewhere else.\u003C\u002Fp>\n\u003Cp>Notes:\u003Cbr \u002F>\n* You should keep the old postname slugs, or the plugin will not be able to find the posts based old links request.\u003Cbr \u002F>\n* This plugin supports WPML.\u003C\u002Fp>\n","This plugin will automatically 301 redirect your old 'postname' format permalinks so you don't lose your precious SEO.",700,16343,16,"2017-05-10T09:17:00.000Z","4.7.33","2.9.0",[123,124,125,126,127],"link","links","old-post-slugs","post-slug","post-slugs","https:\u002F\u002Fwww.frontkom.no\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpostname-permalink-auto-redirect.1.1.zip",{"slug":131,"name":132,"version":6,"author":133,"author_profile":134,"description":135,"short_description":136,"active_installs":116,"downloaded":137,"rating":95,"num_ratings":138,"last_updated":139,"tested_up_to":140,"requires_at_least":18,"requires_php":18,"tags":141,"homepage":145,"download_link":146,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":59},"wp-change-custom-post-slug","WP Change Custom Posts Slugs","ThemeHeap","https:\u002F\u002Fprofiles.wordpress.org\u002Fthemeheap\u002F","\u003Cp>The plugin allows to can easily change slug of custom post types from WordPress admin panel.\u003Cbr \u002F>\nEmail us: abuzer@greelogix.com\u003C\u002Fp>\n\u003Ch3>OUR SERVICES\u003C\u002Fh3>\n\u003Cp>Project                                     Duration                Cost\u003Cbr \u002F>\nWoocommerce custom shop                     1d                      $240\u003Cbr \u002F>\nResponsiveness for 8 pages website              2d                          $400\u003Cbr \u002F>\nWPML configuration for multi-lang website       4h                          $120\u003Cbr \u002F>\nFashion magazine website with Avada theme       5d                          $1000\u003Cbr \u002F>\nLawFirm website with Avada theme                5d                          $1000\u003C\u002Fp>\n","The plugin allows to can easily change slug of custom post types from WordPress admin panel.",9251,11,"2020-10-16T06:43:00.000Z","5.5.18",[142,143,144],"custom-post-types","custom-slugs","wp-change-custom-posts-slugs","http:\u002F\u002Fthemeheap.com\u002Fportfolio-item\u002Fwp-change-custom-posts-slugs\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-change-custom-post-slug.zip",{"attackSurface":148,"codeSignals":178,"taintFlows":186,"riskAssessment":187,"analyzedAt":190},{"hooks":149,"ajaxHandlers":174,"restRoutes":175,"shortcodes":176,"cronEvents":177,"entryPointCount":28,"unprotectedCount":28},[150,155,159,162,166,170],{"type":151,"name":152,"callback":152,"file":153,"line":154},"action","plugins_loaded","no-slug-conflicts-with-trash.php",115,{"type":151,"name":156,"callback":157,"file":153,"line":158},"admin_init","migrate_meta_keys",125,{"type":151,"name":156,"callback":160,"file":153,"line":161},"deactivate_plugin",126,{"type":151,"name":163,"callback":164,"file":153,"line":165},"admin_notices","deprecation_notice",127,{"type":167,"name":168,"callback":168,"priority":11,"file":153,"line":169},"filter","wp_unique_post_slug",130,{"type":151,"name":171,"callback":172,"priority":11,"file":153,"line":173},"transition_post_status","maybe_restore_changed_slug",131,[],[],[],[],{"dangerousFunctions":179,"sqlUsage":180,"outputEscaping":182,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":83,"bundledLibraries":185},[],{"prepared":11,"raw":28,"locations":181},[],{"escaped":183,"rawEcho":28,"locations":184},3,[],[],[],{"summary":188,"deductions":189},"The \"no-slug-conflicts-with-trash\" v1.2 plugin exhibits a strong security posture based on the provided static analysis.  The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface. Furthermore, the code signals indicate diligent security practices, with all SQL queries using prepared statements, all output being properly escaped, and the presence of at least one capability check. The lack of dangerous functions, file operations, external HTTP requests, and critical taint flows further bolsters its security. The plugin's vulnerability history is also clean, with no recorded CVEs, suggesting a commitment to maintaining a secure codebase.  Overall, this plugin appears to be well-secured, with no immediate exploitable vulnerabilities identified in the static analysis. Its strengths lie in its minimal attack surface and adherence to secure coding practices regarding data handling and output. However, the lack of nonce checks, while not explicitly flagged as an issue due to the absence of user-facing entry points, is a standard security measure that would typically be expected, though its absence here is mitigated by the plugin's limited functionality.",[],"2026-03-16T23:22:24.127Z",{"wat":192,"direct":201},{"assetPaths":193,"generatorPatterns":196,"scriptPaths":197,"versionParams":198},[194,195],"\u002Fwp-content\u002Fplugins\u002Fno-slug-conflicts-with-trash\u002Fcss\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Fno-slug-conflicts-with-trash\u002Fjs\u002Fadmin.js",[],[195],[199,200],"no-slug-conflicts-with-trash\u002Fcss\u002Fadmin.css?ver=","no-slug-conflicts-with-trash\u002Fjs\u002Fadmin.js?ver=",{"cssClasses":202,"htmlComments":203,"htmlAttributes":235,"restEndpoints":236,"jsGlobals":237,"shortcodeOutput":238},[],[204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234],"TODO: If post restored under different slug, put in an admin notice that indicates the post was","restored under a different permalink. Link to the post that has its original slug, and to the new","version.","Add message to trashed post on post edit page under slug field to indicate that if untrashed,","the post's slug would be in conflict with a published post and would get assigned a different slug","Probably not: Add message on post create page under slug field to indicate if the new post's slug (or","calculated slug) is currently in conflict with a trashed post. The message would just be to notify the","author that the trashed post cannot be untrashed with the same slug. If the previous TODO is","implemented, that seems sufficient with less noise for the author.","Save original slug under a separate meta key if the post gets untrashed to a non-original slug. (FYI,","once a post is untrashed, the existing meta key is removed regardless of whether the post could be","restored to that original slug or not. Thus this second meta key which the original slug value would","be copied to if the post wasn't restored to its original slug.) This would purely be an informative","meta key allowing a notice\u002Fmessage to be displayed to user indicating that the post was originally","published under this different slug. Maybe add a 'Forget original slug' link next to this message","in case user doesn't care about that.","=>> Read the accompanying readme.txt file for instructions and documentation.","=>> Also, visit the plugin's homepage for additional information and updates.","=>> Or visit: https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Fno-slug-conflicts-with-trash\u002F","Copyright (c) 2013-2016 by Scott Reilly (aka coffee2code)","This program is free software; you can redistribute it and\u002For","modify it under the terms of the GNU General Public License","as published by the Free Software Foundation; either version 2","of the License, or (at your option) any later version.","This 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.","You should have received a copy of the GNU General Public License","along with this program; if not, write to the Free Software","Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.",[],[],[],[],{"error":240,"url":241,"statusCode":242,"statusMessage":243,"message":243},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fno-slug-conflicts-with-trash\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":245,"versions":246},7,[247,253,259,266,273,280,287],{"version":6,"download_url":26,"svn_tag_url":248,"released_at":29,"has_diff":249,"diff_files_changed":250,"diff_lines":29,"trac_diff_url":251,"vulnerabilities":252,"is_current":240},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.1&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.2",[],{"version":111,"download_url":254,"svn_tag_url":255,"released_at":29,"has_diff":249,"diff_files_changed":256,"diff_lines":29,"trac_diff_url":257,"vulnerabilities":258,"is_current":249},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.4&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.1",[],{"version":260,"download_url":261,"svn_tag_url":262,"released_at":29,"has_diff":249,"diff_files_changed":263,"diff_lines":29,"trac_diff_url":264,"vulnerabilities":265,"is_current":249},"1.0.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.0.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.0.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.3&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.4",[],{"version":267,"download_url":268,"svn_tag_url":269,"released_at":29,"has_diff":249,"diff_files_changed":270,"diff_lines":29,"trac_diff_url":271,"vulnerabilities":272,"is_current":249},"1.0.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.0.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.0.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.2&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.3",[],{"version":274,"download_url":275,"svn_tag_url":276,"released_at":29,"has_diff":249,"diff_files_changed":277,"diff_lines":29,"trac_diff_url":278,"vulnerabilities":279,"is_current":249},"1.0.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.0.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.0.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.1&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.2",[],{"version":281,"download_url":282,"svn_tag_url":283,"released_at":29,"has_diff":249,"diff_files_changed":284,"diff_lines":29,"trac_diff_url":285,"vulnerabilities":286,"is_current":249},"1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.0.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0&new_path=%2Fno-slug-conflicts-with-trash%2Ftags%2F1.0.1",[],{"version":44,"download_url":288,"svn_tag_url":289,"released_at":29,"has_diff":249,"diff_files_changed":290,"diff_lines":29,"trac_diff_url":29,"vulnerabilities":291,"is_current":249},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-slug-conflicts-with-trash.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fno-slug-conflicts-with-trash\u002Ftags\u002F1.0\u002F",[],[]]