The idea is that this function will either +1 or -1 (actually, can be any number) a specific column of a specific item, instead of a full-blown save_pod_item request dealing with multiple queries and functionality.
Cuts right to the chase, one single query to update the table should do it.
I'm on it.
Awesome, but why'd you close it? Leave it open and let me close so I can commit to the 2.0 branch, I've gotta refresh 2.0 with 1.12 code and after that I can get any new stuff in there too. Maybe provide a gist of your solution?
Damn, because it's too early (west coast) and I clicked the wrong button I guess. sorry bout that.
Np, just a good time to figure out the process until 2.0 is workable again.
HAHA! I clicked it now, it's early for me still..
I clicked Comment & Close
I just removed the button with my AdBlock extension for Chrome, it targets it by the id/class and tag name. Now I'll never have that issue again!
I don't care what you call it, but at one time we had a function called pod_exists() didn't we ... which should have been Pod_API::pod_item_exists() ;-) ... anyway, couldn't we just add on a parameter to that function and change the name and create an option to return the value (instead of boolean) ?
Seems pretty simple to me.
They should really make that button smaller.
Pod_API::pod_exists checks to see if an actual Pod exists, but I don't recall a pod_item_exists(), what sort of use do you think that would give?