Customizr Version 3.15 broken?

atrumm
(@atrumm)

10 years, 4 months ago

Hi all!

Customizr has been rockin and sockin until today…updated to version 3.15 (also updated wordpress to 3.8 just before that)…

and wam – broken site…specifically this:

Warning: Invalid argument supplied for foreach() in /home/beegood/www/www/wp-content/themes/customizr/inc/class-fire-widgets.php on line 51

anybody else have this come up?

— Aaron

Viewing 11 replies - 1 through 11 (of 11 total)

WebMaster
(@marketing-master)

10 years, 4 months ago

My page is also broken after update. Sometimes home page is blank, some times showing only half page in Chrome. In Explorer and Firefox home page is always blank. Other pages are not blank but they are broken. I’m working on this last 3 hours but I didn’t found a solution 🙁

Home page
Sub page

This happened after I updated WP and Customizr like @atrumm.

WebMaster
(@marketing-master)

10 years, 4 months ago

I disable all plugins and then activate one by one. There is big issue with NextGEN Gallery by Photocrati AND W3 Total Cache. If I disable both everything is OK, if I disable only one page is broken.
@atrumm do you use any of those two plugins?

chappie
(@chappie)

10 years, 4 months ago

The author is working on a fix – see his blog comments.

Thread Starter atrumm
(@atrumm)

10 years, 4 months ago

@marketing Master – I don’t have either of those plugins, no. I only have a couple of plugins I guess I’ll try disabling them and see what happens.

@chappie – I see talk on his blog about the NextGEN Gallery problem but I don’t see much about my particular problem…is there more I’m missing?

Thanks for your replies guys. I wonder if I should post a comment to the author’s blog.

— A

Thread Starter atrumm
(@atrumm)

10 years, 4 months ago

@marketing Master – did you happen to fix your problem?

I haven’t 🙁 – disabled my plugins and the only thing that happened is now even my dashboard doesn’t load – same error as front page. Odd.

And/or anybody else? I might have to post a new topic 🙂

sillinguist
(@sillinguist)

10 years, 4 months ago

@atrumm did you try clearing your browser cashe?

Thread Starter atrumm
(@atrumm)

10 years, 4 months ago

@hugh – heh – always a valid question – along with “Is your computer’s power turned on, sir?”

Unfortunately yes I’ve cleared the cache and cross browser checked.

I’m very surprised no one else is running into this problem, as it’s pretty fundamental. Hmm.

WebMaster
(@marketing-master)

10 years, 4 months ago

@atrumm I fix it temporary with turning off NextGEN and W3 Total Cache and I’m waiting for theme upgrade. Unfortunately I didn’t found any other solution for me.
And yes I clear browser cache in three different browsers and clear cache in W3 many times ;).

ElectricFeet
(@electricfeet)

10 years, 4 months ago

@atrumm OK, so you’ve disabled all your plugins and the problem persists. Can you now disable you child theme and run with pure Customizr? Does the problem persist? If it does, what happens if you switch to twentytwelve?

Thread Starter atrumm
(@atrumm)

10 years, 4 months ago

@electricfeet – hello! thanks for responding!

Well – I can’t even get to the dashboard as even that is giving a fatal error so I haven’t tried switching themes…

I guess I’ll have to manually make a switch by digging into the DB and file structure…

Do you happen to know which table sets which theme WP is using? 🙂 (not that I won’t find it by looking)

— A

ElectricFeet
(@electricfeet)

10 years, 4 months ago

I think that if you delete a theme, it defaults to twentytwelve (?). So deleting the theme folder with FTP would be safer than delving in the db. It will also tell you if the theme is the problem or not.