Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi, hcroeze.

    Do you have a URL I can look at? Are you able to get into your error logs?

    Thread Starter Haime Croeze

    (@hcroeze)

    Hi,

    I have a test with debugging set up at http://test3.croeze.net/events/training-wedstrijdsecretaris/

    the error with version 2.1 is a memory error:

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 71 bytes) in /customers/d/f/8/croeze.net/httpd.www/test3/wp-includes/formatting.php on line 209

    With version 2.0 I do not get this error.

    I tried also by raising memory in config.wp to 96M, that did not help

    then I tried by removing the following from wpconfig (wp eventmanager setting)

    define(‘EM_CONDITIONAL_RECURSIONS’,3);

    that did not help either.

    Here’s the error I get when visit the link:

    Notice: wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /customers/d/f/8/croeze.net/httpd.www/test3/wp-includes/functions.php on line 3370 
    
    Warning: Cannot modify header information - headers already sent by (output started at /customers/d/f/8/croeze.net/httpd.www/test3/wp-includes/functions.php:3370) in /customers/d/f/8/croeze.net/httpd.www/test3/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 60

    Could be a problem w/ your caching plugin?

    Thread Starter Haime Croeze

    (@hcroeze)

    Hi, I got rid now of wp-super-cache on the test site, debugging is on and I removed also the define(‘EM_CONDITIONAL_RECURSIONS’,3); from wp-config (uses extra memory).

    I still have the error on the page with content-protector v2.1

    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 2048 bytes) in /customers/d/f/8/croeze.net/httpd.www/test3/wp-includes/formatting.php on line 209

    http://test3.croeze.net/events/training-wedstrijdsecretaris/

    this does not happen with v2.0

    What happens when you disable WP Events Manager?

    Also, can you post the complete shortcode, including enclosed content, that you’re trying to use?

    Thread Starter Haime Croeze

    (@hcroeze)

    @kjvtough I can confirm it does not go with wp-events-manager. I removed the content-protector shortcode from the event and then it worked. Then I added this shortcode to a regular page and that works also.

    regular page with shortcode (v2.1) is http://test3.croeze.net/test/

    event without shortcode is: http://test3.croeze.net/events/training-wedstrijdsecretaris/

    shortcode is:

    [content_protector password=”waaghals” identifier=”test” ajax=”true”][contact-form-7 id=”856″ title=”contact form 2 voor event”][/content_protector]

    OK, I’ve just released 2.1.1 which should fix your problem. I suspect between Events Manager and Content Protector, there was some infinite recursion going on with respect to applying content filters. There’s now a custom filter, content_protector_content, that emulates apply_filter( 'the_content', ... ) for the form and CAPTCHA instructions without having to worry about whether another plugin trying to apply that filter.

    Thread Starter Haime Croeze

    (@hcroeze)

    @kjvtough

    this is awesome! Tested and it works! I can confirm that v.2.1.1 is compatible with wp-events-manager.

    Thanks,

    Haime

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Blank screen with version 2.1’ is closed to new replies.