Seeing weird error in logs – mla-default-mime-types.tpl

Thank you for your report, which is very exciting. Yours in the third occurrence of this problem (in four years) and the first since I added the debug message you list.

As you suspected, the problem is in the mla-default-mime-types.tpl file, which contains definitions of all the MIME types and file extensions I know of. It looks like an empty line has crept into your copy of this file, somewhere in the first 162 lines. The empty line is ignored and should be harmless.

Do you see one message in the log or many for each page load?

I would very much like to see your copy of the file to verify that and compare it to my copy. I can also send you a clean copy of the file that would eliminate the problem. If you send me your contact information I can reply with an email address you can use to send the file. Use the Contact Us page at the FTJ web site:

Fair Trade Judaica/Contact Us

Do not post your e-mail address in the forum; personal details in a public forum violates WordPress guidelines. If you have trouble accessing the FTJ site, post a note here with your country of origin and I can temporarily unblock it.

In the past, simply reinstalling the current MLA version or updating to the current Development Version resolved the problem. You can do either one by following the instructions in this earlier topic:

Shortcode not working in (special) widget

I will leave this topic unresolved until I hear back from you. Thanks again for reporting it and for any help you can give me in my further investigation.

I have released MLA v2.24. Updating to the new version may resolve the problem you reported.

As I posted earlier, it would be great to see a copy of the file that gave you the log messages, but if the new version solves your problem that’s good, too. Let me know what your experience is; thanks.

Hi David, sorry for the late reply, I didn’t see any notification come in. I actually just googled the error message again and by luck found my own post ??

I did some debugging a few weeks ago when I reported the issue and there was no empty line in the file. I even downloaded the plugin again to check if there were any differences, but there were none.

In the mean time I did already update to the 2.24 version, but the issue still persists. I did notice now that there was an empty line at the end of the file, which I removed now, but still the same issue persists.

Added this now:

$i = 0;
foreach ( $mla_mime_types as $mla_type ) {
    $array = explode(',', $mla_type );
    $i += 1;
    // Bypass damaged entries
    if ( 5 > count( $array ) ) {
        error_log( __LINE__ . ' - ' . $i . ' _get_upload_mime_templates mla-default-mime-types.tpl $array = ' . var_export( $array, true ), 0 );

Resulting in 162

Is there any point in logging this btw? I have now removed the line as unless something is actually broken, I don’t want to clog up the log files ??

I’m having the same error message.
[03-Mar-2016 15:01:39 UTC] 1756 _get_upload_mime_templates mla-default-mime-types.tpl $array = array (
0 => ”,
)

Any help? I don’t see any empty lines. I can provide my file if you wish.

@billyudi – Thanks for your report and your offer to provide the file. If you can send me your contact information using the “Contact Us” form (see my first post in this topic) I will reply with an address you can send the file to.

I haven’t been able to reproduce this issue on my test system. What is the operating system, etc., on the server with the problem? Maybe there’s some subtle file system issue I haven’t considered.

I have uploaded an MLA Development Version dated 20160302 that incorporates Richard K’s “line counting” improvement and makes the error logging optional. By default, logging is now disabled. To enable logging, add something like this to your wp-config.php file:

/**
 * Media Library Assistant debug options
 */
define( 'MLA_DEBUG_LEVEL', 1 );

/* That's all, stop editing! Happy blogging. */

That will add a “Debug” tab to the Settings/Media Library Assistant submenu that gives you convenient access to the error log, and will turn on the logging for damaged TPL files. You can enter “0” (zero) in the MLA Reporting text box (scroll to the bottom and click Save Changes) to disable TPL logging but keep the Debug tab available for other uses.

If you install this Development Version, activate the logging and still have the problem, let me know what the log says. If you send your current copy of the file I can try it out.

Be sure to preserve your current TPL file before installing the Development Version! If you can test the Development Version with the current file, so much the better.

Thanks for your patience and for your help.

I have released MLA version 2.25, which contains some improvements in the error logging for problems encountered in the parsing of default MIME type definitions.

I am marking this topic resolved, but please update it if you have any problems or further questions regarding the topic. Thanks for your help with this issue.