Support » Plugin: WP Defer Loading » Plugin could not be activated because it triggered a fatal error.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author bassjobsen


    @mattday thanks for posting your issue. Could you confirm you are using version 1.0.1 of the plugin?

    wp-defer-loading.php of version 1.0.1 don’t have a line 252. I found some white space on the end of the file this will gives you troubles maybe.

    Sorry for the lack of info. I confirm version is 1.0.1.

    The cause of the problem turned out to be the inconsistent opening tag ‘<?’ on line 236. Changing it to ‘<?php’, as used everywhere else in the file fixes this issue. (Note: this occurred on a server running nginx – I did not observe it on a different server running apache).

    The plugin actives after that fix, but it still does not work. It spews out what should be Javascript as visible text at the top of each page. Looking at the page source, there are superfluous script tags, but I haven’t had a chance to look at it any further.

    <script type="text/javascript">
    			 // Add a script element as a child of the body
    			 function downloadJSAtOnload() {
    			 <script type='text/javascript'>try{jQuery.noConflict();}catch(e){};</script>
    var element = document.createElement("script");
    element.appendChild( document.createTextNode(...
    Plugin Author bassjobsen


    @mattday thank you very much!!!!!!
    I changed this and upload as version 1.0.2

    Please let me know if you find any other issue.

    Plugin Author bassjobsen


    @mattday Note is marked the above as resolved. This is not correct since you still got the output errors. I post this errors here:

    I will try to fix them a.s.a.p.
    I you got any further information like the theme or plugin(s) used, please let me know.

    Thanks, I will post anything further on github, but not sure when I will get a chance to look at it again. The theme was just a very slightly modified version of Twenty Twelve.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.