Dirty Bill

@ivnus – I can see you have an implementation of this on your site. Did you create a plugin out of it, or did you just integrate it? I’m working to do the same thing you are, but I’m not having success implementing what I’ve gleaned from the various threads on this topic.

Can we get this fixed in FWP?

same problem here. Desktop eventually shows mobile. Mobile usually shows mobile on home page, switches to desktop on other pages.

Be good if we could hook it into here: https://openweathermap.org/wiki/API/JSON_API

That’s fine that it’s a debug feature, but I’d like to know how to satisfy the condition so I stop tripping the error.

Disabled, then re-enabled mod-rewrite on Apache server – fixed the issue. Not sure why this would work over a restart but mine is solved.

Same problem. Only non-stock plugin installed is Buddypress and it is disabled. Tried with 2010 and 2011 themes, front page comes up, any link clicked gives a 404 error.

I run many WP sites including WPMU, first time I’ve ever had this happen.

The problem doesn’t persist if I deactivate Edit Flow. Here is an image from one of our editors: https://www.facebook.com/photo.php?fbid=10151029373697779&set=o.238106879581642&type=1&theater

I’ve been using Edit Flow for a couple of years, our plugin structure has remained static for over a year, it broke with the last edit flow update.

Note: No users are able to publish to live, they can only submit for approval then our managing editor will do final edits before pushing it live.

Before diving into that being the out – this workflow has been working fine for a long time and ONLY broke with the Edit Flow update.

Same problem here. The Save button shows up in full screen edit, but NOT in standard edit mode. Happened with the update.

Same issue.

shutdown all plugins and site runs, activated bbpress only and same memory allocation error, really odd.

Same issue, memory size, etc.

Got a link to that solution Ron?

Thanks Peter, I will try this out and report back.

I’ve played with it, no difference in the issue. It looks like anything that makes a memory_limit call (in wordpress) as in admin.php triggers the php error.