Title: Active MLA plugin causes 500 error
Last modified: August 22, 2016
---
# Active MLA plugin causes 500 error
* Resolved [ceophoetography](https://wordpress.org/support/users/ceophoetography/)
* (@ceophoetography)
* [11 years, 4 months ago](https://wordpress.org/support/topic/active-mla-plugin-causes-500-error/)
* I like the features of the Media Library Assistant plugin, but ever since updating
to WP 4 or 4.1 and/or MLA 2 — I’m unsure on when the problem began — if I have
MLA active, my media attachment pages all get a 500 Internal Server Error.
* I want to take advantage of the tag cloud capabilities of the plugin, but I must
have my media attachment pages visible, as that’s how I link my photos to an
external store.
* [https://wordpress.org/plugins/media-library-assistant/](https://wordpress.org/plugins/media-library-assistant/)
Viewing 7 replies - 1 through 7 (of 7 total)
* Plugin Author [David Lingren](https://wordpress.org/support/users/dglingren/)
* (@dglingren)
* [11 years, 4 months ago](https://wordpress.org/support/topic/active-mla-plugin-causes-500-error/#post-5673244)
* Thanks for the good words and for reporting this issue; I regret the trouble
you’re having, which I have not seen before.
* Have you ruled out an interaction with some other plugin?
* Do your attachment pages use any of the MLA shortcodes, `[mla_gallery]` or `[
mla_tag_cloud]`? If they do, you can try updating to the Development Version,
which you can find on the “Developers” tab here in the Repository. The Development
Version fixes one bug in `[mla_gallery]` and it may affect you (although it is
unlikely to cause an HTTP 500 error).
* Failing that, do you have access to the error log(s) on your server? If so, is
there more detailed information in the log that might shed light on the issue?
* If all else fails, I would like to see your template file. You can post it here
or give me your contact information and I will respond with an address where
you can e-mail the template file to me. You can use the Contact Us page at our
web site:
* [Fair Trade Judaica/Contact Us](http://fairtradejudaica.org/our-story/contact-us/)
* Thanks for your patience and any more information you can provide.
* Thread Starter [ceophoetography](https://wordpress.org/support/users/ceophoetography/)
* (@ceophoetography)
* [11 years, 4 months ago](https://wordpress.org/support/topic/active-mla-plugin-causes-500-error/#post-5673467)
* David,
* Thank you for your reply and probing questions. When I first troubleshooted the
issue, I first disabled all plugins and activated them one by one, and the 500
error occurred (in my attachment pages) after activating the MLA plugin. I didn’t
think to then try working backward from there, pairing MLA with other plugins.
The debugging report from those initial tests said:
- [06-Jan-2015 04:35:17 UTC] PHP Notice: get_bloginfo was called with an argument
that is **deprecated** since version 2.2! The `siteurl` option is **deprecated**
for the family of `bloginfo()` functions. Use the `url` option instead. in[
redacted]/wordpress/wp-includes/functions.php on line 3495
- [06-Jan-2015 04:35:17 UTC] PHP Notice: get_bloginfo was called with an argument
that is **deprecated** since version 2.2! The `siteurl` option is **deprecated**
for the family of `bloginfo()` functions. Use the `url` option instead. in[
redacted]/wordpress/wp-includes/functions.php on line 3495
* That report would appear only with the MLA plugin activated.
* After some more digging around last night, according to your suggestion of checking
for a conflict between two plugins, it appears that the 500 error is caused by
a conflict between MLA and the W3 Total Cache plugin. The 500 error occurs only
when both of them are active.
* However, there’s still a problem with the MLA plugin even with W3 Total Cache
inactive. The media attachment pages are loading with MLA as the only active
plugin, but it has the strange side effect of wiping out most of the content
on my page (though leaving the photo and its caption intact — just the post,
basically), including my main sidebar and my footer. My experience has been that
having an improperly closed HTML tag in a post causes similar problems.
* Debugging also turned up, in addition to the data above, the following:
* [15-Jan-2015 05:01:48 UTC] PHP Fatal error: Allowed memory size of 41943040 bytes
exhausted (tried to allocate 35 bytes) in [redacted]/wordpress/wp-includes/taxonomy.
php on line 2662.
* Is there something in the MLA PHP templates that might be incompatible with the
upgraded core?
* Plugin Author [David Lingren](https://wordpress.org/support/users/dglingren/)
* (@dglingren)
* [11 years, 4 months ago](https://wordpress.org/support/topic/active-mla-plugin-causes-500-error/#post-5673468)
* Thank you for your update and especially for all of your thorough detective work!
* Regarding the PDP deprecated `bloginfo/siteurl` messages, I have done a text
search of the entire MLA code base and I can find no instance of a call with `
siteurl`. With the exception of the “twentytwelve-mla” child theme in the `/examples/`
directory, there are no `bloginfo` calls in the code. I do have several `get_bloginfo('
version' )` calls, but that’s it.
* I have never done any testing with “W3 Total Cache”, but I will install a copy
and see if I can replicate your issue. Thanks again for taking the time to test
out plugin combinations and track this down.
* The PHP Fatal error – memory exhausted message comes up when the total memory
required by WordPress and all plugins exceeds the limit; the immediate “35 bytes”
symptom doesn’t help much. Line 2662 is in the `wp_get_object_terms` function,
which MLA does use in many places. Can you tell me more about the context in
which this error occurs?
* Finally, the “media attachment pages” corruption. Can you post a link to an example
page and/or tell me if MLA is used directly on those pages? You could post the“
View Source” output of your browser if the page isn’t accessible. I would be
happy to see if I can find a problem. MLA doesn’t have any “PHP Templates” in
the WordPress sense, but it does, of course, generate HTML any time the `[mla_gallery]`
or `[mla_tag_cloud]` shortcodes are used. Those shortcodes are the only source
of MLA output in the “front end”.
* There are a few thousand sites using the current MLA version with WordPress 4.0
and 4.1, so I think/hope a basic incompatibility with WordPress core would be
more widely noticed and reported.
* Thanks for your good work and for any additional information you can provide.
* Thread Starter [ceophoetography](https://wordpress.org/support/users/ceophoetography/)
* (@ceophoetography)
* [11 years, 4 months ago](https://wordpress.org/support/topic/active-mla-plugin-causes-500-error/#post-5673476)
* I don’t know how this forum handles images, so I have uploaded some screenshots
and will link them here.
* This first screen capture shows how the media attachment page should look.
* [Image 1](http://ceophoetography.com/images/webpage_snap.png).
* The second screen capture shows how the media attachment page looks when MLA
plugin is active (but no W3 Total Cache plugin).
* [Image 2](http://ceophoetography.com/images/webpage_mla.png).
* Below is the source for the page as it should look (as in the first screenshot).
* ```
Cozy cove | The Museum of Spiritual Light — hosted by C.E.O. Phoetography
```
* Lastly, following is the source code of the media attachment page with the MLA
plugin active. A lot is missing.
* ```
Cozy cove | The Museum of Spiritual Light — hosted by C.E.O. Phoetography
