clarklab

Any ideas on where I’d start to fix this? I did a little poking around and see that you save the ‘next url’ in wp_options, but couldn’t figure out how to change that to my advantage.

I’m just bummed because it somehow missed a few shots from Valentine’s day and now I’ve got no way to double back and pick them up.

To test things further, I went ahead and set up Twitter auth, and it didn’t work either. Same error message.

So to use this with 3.5, I need to copy/paste what I see above? Or is there a new fix coming out?

Thanks in advance!

btw, there is an equivalent function for updating the data, set_theme_mod: https://codex.www.ads-software.com/Function_Reference/set_theme_mod so I thought it might be something you guys could implement without having to move mountains.

Plus I assume others might want it as the Theme Customizer gets more popular. It’s a great way to avoid an options page.

If needed, I could output some extra classes. I’m not certain how Front End Editor actually works (a client installed it). Does it hook as the PHP renders or in the front-end based on class names, etc?

And thanks for the quick response.

Sure! Here is a quick example, allowing the user to input a line of text into the footer:

https://gist.github.com/3902885

My timing is always impeccable.

But, but… the backgrounds upload just fine. I’ve also made my own settings section with an image upload contained. Will I need to avoid the ‘core’ header feature and write my own? The only difference is the admin screen will disappear, which I wanted to hide anyway.

I guess I’m just confused why image uploads work everywhere but the header. Is it the cropping?

Any reason this isn’t more clearly spelled out in the docs for the plugin? To be fair, it’s not particularly front-and-center on the Stripe page either, I just felt a bit silly getting so far along in the implementation (actually processing payments) before I realized I needed SSL.

Doubtless there are others making the same mistake?

Here are the quick mockups. Basically it’s just another post status, with an extra options screen for controlling how often authors can call dibs.

https://clarklab.com/wp-content/uploads/2012/02/edit-flow-pool.png

https://clarklab.com/wp-content/uploads/2012/02/edit-flow-pool-setting.png

I think this flow would be really useful for us, as our editors and admins are usually the best at creating a good headline, inserting an appropriate post image, etc. I think if the admins could line up a bunch of posts with some post details already perfected we’d see an explosion of targeted content out of our authors (something that currently takes a lot of planning and emails).

We’re in the middle of a shift in content strategy and having some sort of pool would make the process much smoother.

For now, I’ll probably just give it a shot with a shell user called ‘Unassigned’, like you guys suggested.

Hey textenhance, I just saw these links on my website and I’m *positive* I didn’t enable them myself. Everything I read online says that the publisher has to enable them, which I did not.

Are you sure there isn’t some other way these links find their way onto sites? Perhaps something more nefarious? Or is it a browser thing?

Yeah that was the solution I thought of at first, but I just know that at some point we’d screw up and send a post out authored by ‘Unassigned’. That would be easily fixed by just checking for that name should it ever make it in my templates and replacing with ‘Staff’, but I think in the long run I’d much rather have a more robust system.

I’d loooove to draw up some wireframes that shows what I’m after. I’ve got a few other ideas I’d like to see in Edit Flow, care if I toss them in? Or should I make new threads?

Some background on me: I run https://androidandme.com. We’ve got about 8 authors, 2 story editors, and 1 copy editor. We post about 8 times per day.

I’ve got the same problem. We’d just been dealing with it for months until I finally realized that this was the only plugin I was running that touched the media uploader popup.

right now the only way I can think to do it is to save the pageview data as meta data on each post and then orderby the meta value. but that seems like jumping through a hoop, I’d rather not have to cache the number.

I shouldn’t really admit this but I’ve been relying on is_iphone for the main mobile detection in my mobile theme for over a year now. I kept meaning to go back and replace it with something more intelligent but it always seemed to get the job done.

Until recently, when I’ve started noticing odd holes. The new Firefox build on Android returns false. Sometimes browing in incognito mode on desktop returns true. Tablets technically function as desired but I think I need to start taking resolution in account a little more heavily.

What do the rest of you guys use for mobile detection?