[Support request] Testing GP 2.0

Home Forums Support [Support request] Testing GP 2.0

Home Forums Support Testing GP 2.0

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #440658
    Greg

    GP 2.0
    When using the generate press child theme along with GP 2.0 I get the following errors one one particulr development site:
    Warning: array_merge(): Argument #5 is not an array in /home/gregl027/public_html/coffee-beenz.com/wp-includes/widgets.php on line 1159

    Warning: array_diff(): Argument #2 is not an array in /home/gregl027/public_html/coffee-beenz.com/wp-includes/widgets.php on line 1160

    Warning: Invalid argument supplied for foreach() in /home/gregl027/public_html/coffee-beenz.com/wp-includes/widgets.php on line 1162

    Warning: array_merge(): Argument #1 is not an array in /home/gregl027/public_html/coffee-beenz.com/wp-includes/widgets.php on line 1170

    When I disable the child them all is good.

    Child theme contents
    /*
    Theme Name: GeneratePress Child
    Theme URI: http://generatepress.com
    Description: Default GeneratePress child theme
    Author: Thomas Usborne
    Author URI: http://edge22.com
    Template: generatepress
    Version: 0.1
    Tags: two-columns, three-columns, one-column, right-sidebar, left-sidebar, fluid-layout, responsive-layout, custom-header, custom-background, custom-menu, custom-colors, sticky-post, threaded-comments, translation-ready, featured-images, theme-options, light, white, dark, black, blue, brown, gray, green, orange, pink, purple, red, silver, tan, yellow
    */

    #440683
    Greg

    Actually the errors disappear after reloading the site, but return after switching between gp2.0 and gp child

    Cheers
    Greg

    #440687
    Tom
    Lead Developer
    Lead Developer

    Hi there,

    This was a WP 4.9 bug – have you updated to 4.9.1?

    #440765
    Greg

    Yes Indeed

    #440872
    Tom
    Lead Developer
    Lead Developer

    Hmm, strange indeed. If you search this string, you’ll see it happening with a lot of themes: wp-includes/widgets.php on line 1159

    It’s caused by something they did in 4.9 which tries to maintain widgets and widget position when switching themes.

    Are all of your widgets in the same areas after doing the switches?

    Does the same thing happen when switching between GP 1.4 and your child theme?

    #440894
    Greg

    Hello Tom,
    all the widgets are in the same place and i just tested with GP1.4 and everything works as one would expect.

    Cheers
    Greg

    #440897
    Tom
    Lead Developer
    Lead Developer

    So the error doesn’t display now if you activate the child and parent? Now if you update to 2.0, it displays again?

    #440913
    Greg

    That is correct. I can switch between GP 1.4 and the GP Child theme without any errors. Soon as I update to 2.0 i get the errors.

    Cheers
    Greg

    #440915
    Tom
    Lead Developer
    Lead Developer

    Ah, looks like they didn’t ship it in 4.9.1: https://core.trac.wordpress.org/ticket/42603

    #440916
    Tom
    Lead Developer
    Lead Developer

    How are you switching to 2.0? Using the Easy Theme and Plugin Upgrades plugin?

    #440917
    Greg

    yes, exactly per the instructions you sent out.

    #440921
    Tom
    Lead Developer
    Lead Developer

    Can you send me temporary admin login details possibly?: https://generatepress.com/contact/

    #441594
    Greg

    Hello Tom,
    Other than the pre-sale form I was not too clear on where to enter the credentials for you to access the site.

    Here are the creds.
    I will change them when you are done:

    let me know when you are done please

    Cheers
    Greg

    #441666
    Leo
    Staff
    Customer Support

    Hi Greg,

    I’ve removed the admin info for safety and added as a note to Tom.

    For future reference, you can send it through Account Issue here: https://generatepress.com/contact/

    #441681
    Tom
    Lead Developer
    Lead Developer

    This is indeed a bug in WP 4.9: https://core.trac.wordpress.org/ticket/42603#comment:11

    Looks like it’s been fixed in the next WP version.

Viewing 15 posts - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.