The fucking ‘Edit Function’ is bust, fix it!
—Unedited and Bitching Mad
This article appears in May 7-13, 2009.
Hey Coast Edit Bitch!
Leave a comment
Subscribe to our newsletter
Be the first to know about breaking news, articles, and updates.
Please…it was working as recently as 48 hours ago (Safari 4). Thank you.
Agreed, the edit button works… it’s when you’re not logged in and you post that edit can be tricky. Login first to avoid the “gotchya”.
Yes Three, it did work 48 hours ago, it was working great, but it ‘s busted now I tell ya, it’s just not working anymore.
Nope kay, that doesn’t work. Tried it.
Doesn’t matter if your logged in or not.
It needs a good tweaking!
Agreed, Smee, it’s been non-functional all day.
Wroks fnie for em
Rack up another ‘agreed’ on the OP’s side.
Not working for me… I’m running Firefox. I’ve cleared the cache, too.
It screwed up for me too (…WHILE I was logged in, kay).
personally, I don’t like the edit feature as it’s no better than reading through from the initial “post your comments” under the bitch you’re reading.
pisses me off to no end on my cell too….
I’d suggest not fixing it… but doing away with it.
but that’s just me.
I had this problem when this site went Beta early. I tried to edit a bitch, but somehow it got nuked. Do yourselves a favor, and proof read it and then spell check it before you submit said bitch, ergo not having to deal with the edit feature.
I never had the edit work. ya i would go to edit, fix my post, go to post it and it would be the unedited version. so now i don’t bother.
Judging by all the typos here, I assumed no one used it anyway. Waste of time, take it out.
seconded.
It’s useful, from a technical POV, to let Andy know what browser and version you’re using. Certain bugs are very specific to browser type (IE is notable for always having exceptions and not being W3C compliant). Edit always worked in Safari 3 & 4 until just a couple days ago.
To those whose edit buttons do not work: tell me your browsers, plz
Safari 3
Works fine in Safari 4.
Thanks to all for your help on this. We believe the issue is now resolved.