Renames internal option keys (dms_settings -> devds_settings); saved settings will reset to defaults once. Also adds a hard security denylist for custom file types.<\/p>","1.0.3":"
Resolves all WordPress Plugin Check errors\/warnings from 1.0.2. Recommended for anyone preparing to submit to WordPress.org.<\/p>","1.0.2":"
Important fix: previous versions could block normal JPG\/PNG\/GIF\/ZIP uploads. Update recommended for all sites.<\/p>","1.0.1":"
Fixes tab-redirect and duplicate-notice bugs from 1.0.0. Recommended update.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.3"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The File Types tab, showing searchable, groupable file type cards with toggle switches.","2":"The Upload Limits tab, with server limit detection and per-role permissions.","3":"The Tools tab, with preset profiles, import\/export, and the live upload tester."}},"plugin_section":[],"plugin_tags":[148482,84,7885,2904,85],"plugin_category":[50],"plugin_contributors":[269280],"plugin_business_model":[],"class_list":["post-345483","plugin","type-plugin","status-publish","hentry","plugin_tags-file-types","plugin_tags-media","plugin_tags-mime-types","plugin_tags-svg","plugin_tags-uploads","plugin_category-media","plugin_contributors-developersd","plugin_committers-developersd"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/developersd-manage-media-support.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Developersd Manage Media Support<\/strong> is an advanced media management plugin that gives administrators precise control over what can be uploaded to their WordPress site \u2014 far beyond the handful of file types WordPress supports out of the box.<\/p>\n\n Enable support for SVG, WebP, AVIF, HEIC, fonts, PDFs, Office documents, archives, developer files (JSON, YAML, SQL, Markdown), audio\/video, certificates, contact cards, and design files (Figma, Sketch, Adobe XD) \u2014 or register your own custom MIME types entirely.<\/p>\n\n Every uploaded file is checked against the extensions and MIME types you've explicitly enabled, validated against WordPress's own file-type detection, and optionally checked against known file signatures. SVG uploads are sanitized by default when enabled. Nothing here ever relies on trusting a browser-supplied filename or content type.<\/p>\n\n The plugin is built with a clean, fully namespaced, object-oriented architecture. Every class has a single responsibility, all settings live in a single option (no custom database tables), and a full set of filters and actions lets other plugins register additional MIME types or adjust behavior without editing core files.<\/p>\n\n\n No. The plugin enforces whichever is smaller: your configured maximum, or your server's actual PHP SVG support is disabled by default. When you enable it, the plugin sanitizes every uploaded SVG file \u2014 stripping scripts, event handler attributes, external references, and other known XSS vectors \u2014 using a dependency-free sanitizer built on PHP's DOMDocument. For maximum safety, we also recommend restricting SVG uploads to trusted roles using the Upload Limits tab.<\/p><\/dd>\n No. This plugin makes no external requests, collects no user data, and includes no analytics or tracking of any kind.<\/p><\/dd>\n Nothing \u2014 deactivating leaves all settings intact. Settings and the audit log are only removed on uninstall (deleting the plugin), and only if you've explicitly enabled \"Delete data on uninstall\" in the Advanced tab.<\/p><\/dd>\n Yes. Use the Key Features<\/h4>\n\n
\n
upload_max_filesize<\/code> \/ post_max_size<\/code> limits and a clear warning when your setting exceeds what the server allows.<\/li>\n.htaccess<\/code> and php.ini<\/code> snippets for hosts that support raising those limits.<\/li>\ndevds_mime_catalog<\/code>, devds_presets<\/code>, devds_default_settings<\/code>, and more).<\/li>\nSecurity First<\/h4>\n\n
Developer Friendly<\/h4>\n\n
\n
developersd-manage-media-support<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install directly through the WordPress Plugins screen.<\/li>\n\n
Will this let me exceed my host's upload size limit?<\/h3><\/dt>\n
upload_max_filesize<\/code> \/ post_max_size<\/code> values. It will clearly warn you if your configured value exceeds what the server allows, and provides optional .htaccess<\/code>\/php.ini<\/code> snippets you can try \u2014 but ultimately your hosting provider controls those hard limits.<\/p><\/dd>\nIs SVG upload safe?<\/h3><\/dt>\n
Does this plugin track anything or phone home?<\/h3><\/dt>\n
What happens to my settings if I deactivate the plugin?<\/h3><\/dt>\n
Can other plugins register their own file types?<\/h3><\/dt>\n
devds_mime_catalog<\/code> filter to add entire new groups or individual file types programmatically.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
Developersd\\MediaSupport<\/code>) as an unrecognized global prefix, and flagged template-partial local variables as if they were globals (they're always include()<\/code>d from within a class method, so they're not).<\/li>\n.phpcs.xml.dist<\/code> ruleset declaring this plugin's recognized prefixes, for anyone running PHPCS\/WPCS directly against the codebase.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
dms<\/code>-prefixed identifiers (constants, hooks\/filters, option names, the AJAX action, the nonce, and the enqueued script\/style handle) have been renamed to the devds<\/code>\/DEVDS<\/code> prefix, per WordPress.org Plugin Directory review feedback that the original prefix was too short. This includes the devds_settings<\/code> and devds_audit_log<\/code> options (previously dms_settings<\/code> \/ dms_audit_log<\/code>) \u2014 sites that saved settings under the old prefix will start fresh with defaults after updating.<\/li>\n<\/ul>\n\n1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n