Creating child theme in 1.8 causes loss of column widths

  • Anonymous


    Yes, the @import was missing from the child theme.


    Saying his site has experienced load times issues with the upgrade to 1.8.. It did take a little while to load (when 1.8 was activated)… but I didn’t have time to determine if it’s theme related or something else.



    Immediately after the upgrade to 1.8 I began experiencing slow page loads and “500” errors. Dashboard and normal pages would timeout and when they did load it would be 7 to 10 seconds before the first byte loaded. Memory usage jumped about 15MB and server load was high – even after a reboot. The site is running on a VPS so this was quite out of the ordinary. It is actually the reason I attempted to add the child theme – so I could cut down on the load times a bit.

    Including the @import fixed the formatting, but didn’t help load times. Immediately after reverting to 1.7.3 page loads returned to normal.

    I’m thinking of trying the update again, but I’m a little cautious as the site needs to be functional on Saturday morning.


    Syahir Hakim




    That seems to work much better! Memory is as it should be and no CPU increase.

    Now I’m off to check my child theme! Update: Child theme works as expected.

    So, what was the change?


    Syahir Hakim


    There were multiple changes based on the feedback received so far, but one change in particular relates to memory. This is explained here:



    Excellent. That definitely explains the 15-20MB increase and load. Thank you Syahir for your work on Graphene and Josh for his help yesterday.

    jonas klein


    Hello syahir congratulations for the speed the update package for min solved the problem of error on line 28 among other errors with this my blog is back to normal.

    Thank you for your attention

Viewing 7 posts - 11 through 17 (of 17 total)

  • 1
  • 2
  • You must be logged in to reply to this topic.
Do NOT follow this link or you will be banned from the site!