If anyone out there is a PHP developer and is familiar with developing WordPress plugins, the Numly Plugin would greatly appreciate your attention.
Originally created by Cal Evans and licensed under the GPL version 2.0. The plugin automatically submits posts created in WordPress to be fingerprinted, have their ESN generated an then place the information in the post.
This site as well as Mike Kavis’ blog on itToobox both use the plugin with great success.
The plugin is in need of some updates and it appears that Evans has moved on to other projects. I attempted to email him about this but have not received a reply. Among the requested improvements are the following:
- Creation of ESN after permalink has been created so that the permalink can be placed into the ESN information.
- Fixes to the display of the Numly graphic so that tracking will work in Numly
- More advanced options to give greater flexibility in how the plugin submits information.
If anyone is interested, feel free to contact Chris Matthieu and let him know. He can provide you with information about the Numly API (I couldn’t locate the documentation) and help you get started.
Any and all assistance here would be greatly appreciated.
My apologies to everyone for the limited posting this week. I am still very deep in my house (opening night is Saturday) and things will continue to be sparse here for a few more days. Thank you very much for your patience.
electrical
Good luck for your opening night:)
No need to be apologetic. We shall wait. Personal life is very important and you are on a particularly important aspect of it. All the best for successful completion.
Recliners & RS: Thanks for the well wishes, understanding and support! I’ll be sure to post video of photos of it as soon as practical. Should be a lot of fun!
[...] Numly plugin is looking for a new maintainer. This plugin automatically submits posts created in WordPress to be fingerprinted, have their ESN [...]
So how was opening night?
Recliners: See today's post for more info!
Recliners: See today’s post for more info!
Thanks for putting this up, Jonathan! I also use this plugin and love it. The changes you mention are the most pressing, but I think I can add a few for anyone who does take it over. I'll let Chris know.Hope your haunted house is scaring a few folks!-Will
Thanks for putting this up, Jonathan! I also use this plugin and love it. The changes you mention are the most pressing, but I think I can add a few for anyone who does take it over. I’ll let Chris know.
Hope your haunted house is scaring a few folks!
-Will
Another small fix to the plugin would be:All the user input fields of the plugin should remember your configurations when you deactivate and then activate the plugin. As it is now, all data is cleared and every time you reactivate the plugin, you need to re-enter the data. Right now it is only two fields, but with additional, more advanced, options as Jonathan suggests, this will be more problematic.-Will
Another small fix to the plugin would be:
All the user input fields of the plugin should remember your configurations when you deactivate and then activate the plugin. As it is now, all data is cleared and every time you reactivate the plugin, you need to re-enter the data. Right now it is only two fields, but with additional, more advanced, options as Jonathan suggests, this will be more problematic.
-Will
Will: Thanks for the heads up on that one, I haven't deactivated the plugin so I had no idea. I'll be sure to add that to the list. I'll be in touch with Chris tonight and see if anyone has contacted him.
Will: Thanks for the heads up on that one, I haven’t deactivated the plugin so I had no idea. I’ll be sure to add that to the list. I’ll be in touch with Chris tonight and see if anyone has contacted him.
So far, it seems like no takers on this. I did notice something else a few times since I upgraded to WP2.3.When I edit an existing post that already has a Numly number, I used to get issued a new number. This makes sense as if I change the original article, technically it becomes different. This is not happening since I upgraded to 2.3. Now I can edit a post and a new Numly number is not generated.Has anyone else noticed this. I wonder if it is the plugin acting differently with 2.3 or if it something on the site. I'll ask Chris about it.-Will
Will,I don't think there have been any takers. I haven't noticed that problem but, then again, I haven't updated any old posts. It could be an issue dealing with the WP hooks though.Definitely ask Chris about it. I'll direct him to this comment too.
So far, it seems like no takers on this. I did notice something else a few times since I upgraded to WP2.3.
When I edit an existing post that already has a Numly number, I used to get issued a new number. This makes sense as if I change the original article, technically it becomes different. This is not happening since I upgraded to 2.3. Now I can edit a post and a new Numly number is not generated.
Has anyone else noticed this. I wonder if it is the plugin acting differently with 2.3 or if it something on the site. I’ll ask Chris about it.
-Will
Will,
I don’t think there have been any takers. I haven’t noticed that problem but, then again, I haven’t updated any old posts. It could be an issue dealing with the WP hooks though.
Definitely ask Chris about it. I’ll direct him to this comment too.