• Resolved fractaleater

    (@fractaleater)


    Visual Composer is at 4.7.4.

    When MLA is enabled, “edit.php?post_type=page” shows a blank page with no PHP err\warn. php.ini has log_errors on, debug true in wp-config. Have around 120 pages and 2000+ media items.

    Only thing required to restore page posts is to deactivate MLA or VC.

    VC is not stock version.. version altered by Jupiter Theme from Artbees.

    https://www.ads-software.com/plugins/media-library-assistant/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author David Lingren

    (@dglingren)

    Thanks for your report and the details you provided.

    One common cause of “blank page” problems is memory limitations. Here is a recent topic with more information and suggestions for investigating/resolving memory problems:

    Can’t access mla-menu page

    I know of at least one other site that uses MLA and Visual Composer without issues:

    Trying to get property of non-object

    If you rule out memory issues and still have a conflict, let me know and I will investigate further. I will leave this topic unresolved until I hear back from you. Thanks for your interest in the plugin.

    Thread Starter fractaleater

    (@fractaleater)

    Have not ruled out memory issues, but troubleshooting shows that with VC and MLA active, and disable “W3 Total Cache” and “Wordfence Security”, and “edit.php?post_type=page” shows expected results. Enabling either one of those two plugins results in a blank page.

    I’ve followed the instructions for increasing PHP Memory in wp-config, but my hosting provider says I’m not bumping against my 1GB limit.

    I’ve moved on to identify any other combinations of disabled plugins that don’t result in a blank page.

    Thread Starter fractaleater

    (@fractaleater)

    Was a memory resource issue.

    Found this one line construct in my wp-config:

    /**#@-*//** Memory Limits. */define('WP_MEMORY_LIMIT', '96M');define('WP_MAX_MEMORY_LIMIT', '128M');

    Which is actually *not* a comment. Making it a comment and increasing values to 128 and 256 corrected the problem.

    Sorry for the distraction, and thanks for your effort on this plugin.

    Definitely donation worthy!

    Plugin Author David Lingren

    (@dglingren)

    Thanks for your updates and for taking the time to track down and solve your problem. I am very happy to hear the suggestions were helpful.

    As you’ve found, the memory issue is a “global” problem caused by the total requirements of your theme and all active plugins. Even so, I am working on MLA changes to reduce its memory requirements in a future version.

    Thanks again for the effort you put in to solving the issue and for your interest in the plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Visual Composer and MLA conflict’ is closed to new replies.