• Have wp network running w/ subdomains; after upgrading to 3.2.1, when I add new site, it seems ok in admin, but blank frontend?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Flush your cache and doublecheck your .htaccess 🙂

    blanks as in entire white screen? or blank as in text but no theme? two different problems. 😉 A link would be nice.

    also – did you delete the default theme?

    Thread Starter davecr

    (@davecr)

    Blank as in white screen – just did delete default theme,no change.
    Here’s the “new” site:
    http://testsite.berkshires.co/

    Here is the core site with links in footer to other subdomain sites:
    http://berkshires.co/

    Thanks Andrea,

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Exisiting ones work fine for me – http://coupons.berkshires.co/

    And Andrea wasn’t asking you To delete the theme, but if you HAD. Don’t 🙂 Put TwentyEleven back, please.

    Thread Starter davecr

    (@davecr)

    Thanks Ipstenu, htaccess is good and cache flushed – to no avail.

    Thread Starter davecr

    (@davecr)

    OK twentyeleven back – thanks. The problem is creating new sites – only since today after I upgraded to 3.2.1

    These errors appear on the dashboard of the new site, which does have page and post edit screens, etc.:

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /home/berkco/public_html/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php on line 540

    Warning: Cannot modify header information – headers already sent by (output started at /home/berkco/public_html/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php:540) in /home/berkco/public_html/wp-includes/functions.php on line 861

    Warning: Cannot modify header information – headers already sent by (output started at /home/berkco/public_html/wp-content/plugins/wordpress-seo/inc/class-sitemaps.php:540) in /home/berkco/public_html/wp-includes/functions.php on line 862

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    wordpress-seo is your problem. Delete it.

    Thread Starter davecr

    (@davecr)

    Hooray, wp-seo the culprit – but why? Any recommendations for replacing it? Thank you!

    I am having the same problem with a completely blank screen on my new blog I created on my new multisite setup I established on my WordPress site (for which I am the Super Admin.) I am set up with Sub Folders, and I have double checked my .htaccess file for correctness – all appears to be in order. Other than creating the new blog, I have done nothing to alter it – the existing post and comment are the sample ones that are set up automatically; the theme is still set to twentyten by default, and I have not installed any other themes. (Although the template and stylesheet both indicate twentyeleven as their theme under “settings.”)

    I’ve signed in and out repeatedly and flushed my cache, and I still get a completely blank, white page. Could there be a conflict with a plugin? I am running a bunch on the main site – they are: Admin Message Board; Blog in Blog; Broken Link Checker; Category Order; Current Date & Time Widget; Image Widget; Link Library; Maintenance Mode; My Link Order; My Page Order; Paid Business Listings; S2Member; Simple: Press; User Bio Widget; WordPress.com Stats; WP Google Fonts; and WP Show ID’s

    The link to the new blog’s homepage is http://abodelearning.com/southernexposure/.

    Thanks!
    Alisha

    Ahh, nevermind! I selected a different theme, placed some widgets in the sidebars and lo and behold – there is my page! Thanks anyway! 🙂

    @davecr – try Yoast’s seo plugin in the repo

    @alishayouch – it’s always a good idea to start a new thread for your particular issue. A blank white screen is a general php error and not the same in every case. glad you fixed it though.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    @davecr – Why? Because the plugin probably isn’t fully compatible with (a) your theme (b) your server (c) WordPress 3.2.1

    It happens :/

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘no frontend on new sites’ is closed to new replies.