[NEW] ESBN

@vkarly,

Hmmmm…this smells familiar. Right before I released, the last bug I fixed was one that was cropping up on ESBN’s test blog. I had to edit the value I received from the system to store correctly.

But honestly, if he’s getting an E040 then the syste isn’t giving us a valid ESNB number because it thinks the username is missing. The number we need to display isn’t in in the meta field yet.

When you say you changed the value, what was it originally and what did you change it to.

=C=

p.s. why does anyone use anything but bigint(20) for PKs? Ya gotta wonder.

[Anything I might have to say to your ps would probably get me in trouble…. take it as read….]

Well, I changed it to an ESBN for a post on the (working) 2.0.1 install, just to see what it was expecting to get. The value originally showed E40 – Missing author, just as rafleet posted. So I changed it first to my author name on ESBN. That got rid of the error of course, but just wanted to load my author login page at ESBN when clicked on – hardly ideal. So I stuffed the other number in there just to see if it would be happy with that (because being installed on a different wp version, you just never know….)

So then I took the number for the other post out, which means nothing shows at all right now (because logically you don’t want a second post showing the same ESBN number as another one….)

[Edit: later…. you can generate an ESBN number by inputting through the interface after you sign in. Gives you a usable number, but you can’t click it and get anything but ESBN’s “not found” page. I don’t know if it takes longer to update that way or not…. Anyway, 1.5.2 use seems to be problematic.]

@vkaryl,

Oh go ahead, get in trouble. What are they going to do fire you? (or did you mean with me?)

Ok, yes, if you are editing the metadata directly you can get rid of the error. But that just changes the display, not the underlying problem.

I have good news and bad news.

The good news is this only seems to affect 1.x installs, all the 2.x installs I’ve tested on (you, mine and ESBN’s test blog) seem to work just fine.

The bad news. I’m prepping a release for this weekend that fixes a couple of problems and also re-does how the options are saved. This version (1.2) will be a WP 2.0+ only version. I am using a function that I know was introduced in 2.0.

Sorry, I hate to lock anyone out but it’s the only wan I can find to accomplish what I want to accomplish.

=C=

Well, that’s okay, long as I know. With a couple of exceptions the 1.5.2 blogs I have don’t need this sort of thing anyway (well, I could be wrong, but most of them are just personal playgrounds….) and the couple that could benefit/might need an ESBN number I will simply upgrade.

Truthfully…. I like 1.5.2 better. The added-in stuff in 2.0+ is just silly stuff for kids (personal opinion here – I do have one, and I WILL express it….), doesn’t add a darn thing to the usability much less the value of the blog – or lack thereof. But I suppose eventually 1.5.2 WILL become a liability of some sort, and WILL be unpatched etc. so I’ll have to move them all.

Kicking and screaming…. *sigh* In any case, at least if we know up front that a plugin only works with a particular version, we’ll be less likely to show up here with problems. Maybe.

[Nope, not with you, after all we hardly know each other. But sometimes it’s just not sensible or productive to go off into a diatribe….]

What is the advantage of having an ESBN number for an article? Are articles better picked up by other organisations? What are the benefits?

@vkaryl,

I THINK the function I’m using is 2.0, I’m not sure. I’ll ask for testers later this week and we’ll see.

@herold,
Personally, no real advantage. I jsut saw an opportunity to write another plugin and took it. If you take your blogging seriously and want to register your comments, this is an easy way to do it. I’ll leave it up to the ESBN folks (nice guys) to convince you as to why, I’m just a code monkey. ??

=C=

Cal, if you want to let me know when you need testers, you can grab me email – vkaryl *AT* bytehaven *DOT* com. Posts flash by here like *snicker* Ruby on Rails….

Cal, Vkaryl,
Thanks for a flurry of work here, in trying to troubleshoot the problem. I’m running about 20 blogs right now on my site for various CMS projects, and the one I’m trying this ESBN thingie on is my main semi-daily posting install.

I hate to upgrade this one to 2.0.1, because I’ve got tons of code hacks, plugins, and more all working right at this point(same feelings as you, V, I suppose) …but…I see a need for ESBN for this blog more than any other I edit and use on my host.

Regarding the loop…only changes I’ve made to it are posted in the code above for POST.PHP. Mainly just WORDCNT and CHARCNT code…not much more.

I think it would be worthwhile to eventually try to get a 1.5.2 version working for the community. Be glad to help in any way I can.

Getting fairly handy with php, but not a WP geek yet…just an old fart, old school, geek…since 1982. (OFOSG)

Cal, again…thanks for this project, and your other ones..I played with several last nite…good stuff.

Rich

Ok, new version is ready, I’ll start testing it tomorrow. If all goes well, I’ll have a release on Sat or Sun. BTW, they’ve changed their name to Numly, https://numly.com/. I’ll eventually change the plugin name too.

=C=

“NUMLY”? Numb-nuts, anyone? Okay, whatever, let’s head lawsuits off at the pass, I guess, huh? *laughing*

Thanks for the update, Cal!

LOL!

Rumor I heard was they got a C&D from ISBN but that’s a RUMOR!

=C=

I didn’t hear it from YOU, bro! Oy….

I’m posting here because it looks like I’m the only WordPress blogger who hasn’t yet. ??

@vkaryl,

Ok, I’ve combed over the code and for the life of me I can’t find anything that requires bettern than 1.5. $_POST[‘post_author’] was introduced in 1.2. get_userdata() may be the problem. I’ve seen a couple of posts on google about problems with it being AWOL. Since we don’t get any output in the post action, if it were blowin’ chow, we wouldn’t know it.

Anyhow, if you are using WP-ESNB, you may want to grab the latest version. This is a beta announcement. If nobody complains, I’ll release it fully and announce officially. (so we can start a new thred!) ??

=C=

p.s. welcom to the conversation WarAxe!
=C=

Got it, installed, working fine…. The older version still doesn’t work on 1.5.2, and trying this version on a 1.5.2 blog causes a totally blank page etc. *shrug* No biggie, I’m probably going to migrate to latest wp version anyway….

About the icon…. any objection to me changing it?