XLSM Mime Type Issue

Thanks for your report; I regret the trouble you are having with XLSM uploads.

I just ran some quick tests and I have no trouble uploading XLSM files with or without MLA enabled. I believe they are allowed by the default WordPress configuration.

If, however, you are in a multi-site environment they are not allowed. You can find more information in the “File Extension and MIME Type Processing” section of the Settings/Media Library Assistant Documentation tab, which includes:

The list is also used in /wp-includes/ms-functions.php, function check_upload_mimes(), which “is used to filter that list against the filetype whitelist provided by Multisite Super Admins at /wp-admin/network/settings.php.” Multisite installs must respect this restriction, so any list we produce will be passed thru that function if it exists.

If you are not in a multisite environment and are still having trouble, navigate to the Settings/Media Library Assistant Uploads tab, search for XLSM and make sure it is set to “active”. If that doesn’t help, let me know the steps you are using to upload the files and I will investigate further. Thanks for your understanding and your interest in the plugin.

Thanks for your update and the link to your screen shots; very helpful. It looks like you are doing everything right.

For a brute-force workaround you can try disabling WordPress’ type checking as described in this Codex article:

Roles and Capabilities, Special Cases (unfiltered_upload)

If you can access your site’s error log you can try activating MLA’s debug logging:

1. Navigate to the Settings/Media Library Assistant Debug tab.
2. Scroll down to the “MLA Reporting” text box and enter “129”. This will turn on MLA debug logging for MIME Type Processing.
3. Click the Save Changes button to record your new setting.
4. Optionally, scroll to the bottom of the screen and click “Reset” to clear the error log. You may not want to do this depending on how you manage your error log.

Once that’s done you can run one or more Upload tests. Then, go back to the Debug screen and:

1. Enter “0” in the MLA Reporting text box to turn debug logic off.
2. Click the Save Changes button to record your new setting.
3. Scroll to the bottom and click “Download” to get the log content in a text file.

There might be a lot of messages written to the log, so limit the amount of activity during the logging period. You should see messages in the log like these:

[22-Jan-2018 19:47:05 UTC] 591 MLACore::mla_plugins_loaded_action() MLA 2.70 (20180115) mla_debug_level 0x3

You can post the interesting messages in this topic. You can also email me the information if that’s better for you. You can contact me at my web site to continue the dialog.

Thanks for your patience.

Thanks for trying to activate the debug logging. The settings look good; I’m not sure why MLA can’t write its messages to the existing log.

You can try creating an MLA-specific log file by entering enter something like “/uploads/mla.log” in the “Debug File” text box (and saving your changes).

You can also try another experiment. Navigate to the Settings/Media Library Assistant Uploads tab and uncheck the box to the left of “Enable Upload MIME Type Support” to take MLA out of the loop. Run your upload test to see if WordPress will allow XLSM uploads without MLA’s involvement.

Let me know if that helps. Thanks!

I appreciate the additional information about your setup and plugin configurations.

If you can get the MLA logging to work I might be able to shed more light on the situation. I am happy to continue the dialog by email if that’s more convenient.

Regarding ALLOW_UNFILTERED_UPLOADS, you can add the define statement to your wp-config.php file. You can also try adding other statements such as define( 'WP_DEBUG', true ); to the file so more information is logged.

I hope the brute force workaround gives you some relief. Let me know how it goes.

Thanks for the good news that the ALLOW_UNFILTERED_UPLOADS setting works for you. Note that this is a global setting, so any logged in user will get that privilege.

I’m not surprised that there are no “errors” showing in the log; as you wrote, it’s not exactly an error situation. The MLA logging is more of a debug trace tool and should be writing messages showing the details of uploads whether or not they cause actual errors. It might give some clues on the trouble you’re having.

You wrote “Is there a way I can migrate to your plugin but retain the EML settings?” There is some information on adding support for the EML categories in this earlier topic:

Front-end filtering not working out

You could either replace the MLA Att. Categories taxonomy with the EML Media Categories taxonomy or you could map your items’ terms from one taxonomy to the other. The latter might be more complex if you have a hierarchy structure in your existing terms.

I am marking this topic resolved because MLA is working properly and you have found a solution for your immediate problem, but please update it or start another topic if you have problems or further questions regarding the above suggestions.