I would like to have a WordPress plugin created. It would work directly with the pingbacks or trackbacks (whatever you want to call them) that the wordpress blog receives from other blogs on the web.
It would need to do the following:
I will break it down into three (03) parts.
PART ONE
1. Query the database and pull all the trackbacks currently in the system.
2. Allow the full export of all these URL’s, saved as a .txt file. (A history of trackbacks needs to be kept in the system, so you can always export the full list of trackbacks – not just the new ones. This would be best integrated into the WP DB being used by the site [more in item 7].)
3. Have email reporting integrated into the plugin, so you could have all the new trackbacks emailed directly to you, or to more than one email address. (this would be a weekly/monthly email of only the new trackback links for that week – not an email for each individual trackback, that would get annoying!)
4. The email reporting would have two choices for delivery, weekly, or monthly. If weekly then the email would be sent on Monday of every week, if monthly it would be sent the first day of each month.
5. It would only send the “NEW” trackbacks, not old ones that had already been reported. (look at line 2, we still want to be able store the full history of trackbacks and export them whenever we like)
6. Once reported it would also delete the trackbacks from WordPress, this way under comments there wouldn’t be hundreds of them building up over time. (There are often trackbacks stuck in the SPAM folder, so these would need to be moved out of the SPAM folder – accounted for, reported and then also deleted) This would not delete comments though, which are different from trackbacks. The comments should still be left in the system. (since we are manipulating the comments and the trackbacks there should be an option to “delete unnaproved comments” as well.)
7. The plugin would also need to create another table in the database to store the trackback history, so if we wanted to generate a report with all the trackbacks we could easily do that – even if they have already been deleted from the standard WordPress database location. (this should allow you to select specific dates for the trackback URL list export option)
8. Part of the reports would be to export trackbacks based on timeframes, i.e. last 7 days, last 14, last 30, last 90 then also be able to enter dates. These should be deliverable by email, as well as export as .txt file.
9. Plugin should be easy to update as newer versions of WordPress are released, full documentation within the code should also be present in the case that another developer or development team is ever contracted to expand on the functionality or create external software that interfaces directly with the plugin.
PART TWO
1. Take the pingback URL’s for the week and turn them into an RSS Feed – the RSS Feed would be hosted on the same domain that the wordpress blog is hosted on. A selection in the plugin setup should prompt for a folder location to store the feeds. This is a field that the user will enter, for example if the folder name was “dog-training-feeds” then it would be located at http://www.domain.com/dog-training-feeds/ or whatever the folder name is that the user sets.
This RSS Feed would need to be an XML Compliant RSS Feed and pass W3C Feed Validation. This URL can be used to test the validation of feeds: http://validator.w3.org/feed/
2. Once the RSS feed has been created, have the plugin automatically submit it to the following RSS Directories:
-blogpulse.com
-devasp.com
-feedgy.com
-feeds2read.net
-icerocket.com
-newsisfree.com
-ngoid.sourceforge.net
-overskrift.dk
-readablog.com
-rss-network.com
-rssmotron.com
-weblogalot.com
I would also like the ability to add more RSS feeds in the future – so the plugin would need to be able to accomodate this.
3. Once the newly created “weekly” RSS feed has been submitted to the RSS Directories, then an email report needs to be generated notifying the blog owner that it is done. Also, in the plugin it should also show the last date/time that the RSS submission occurred, as well as the link to the RSS feed in the specified feed folder location on the users domain. The number of URL’s in the feed should be predetermined by the user, from 1 to 20 as well as a random option that will randomly add URL’s to the feed from 1 to 20.
If there are 90 new URL’s for the week and the user selected 20 URL’s per feed then it would create 4 new RSS Feeds with 20 URL’s each for a total of 80 and then create another RSS Feed with the remaining 10 URL’s. Once complete the email report would contain the reporting information for this action as well as the links to all the RSS Feed URL’s created.
4. Along with the email reporting and the “last RSS submission” information, a history tab or link should be available that shows the previous RSS feed submissions, with the date/time they occured as well as the links to the RSS Feeds associated with the dates and times.
5. As well as storing all the pingback URL’s as stated in PART ONE, the RSS Feed URL’s also need to be stored in the database so they can be exported, by selecting specific dates to export from.
PART THREE:
This plugin also needs a registration system integrated for licensing purposes. It needs to accomplish the following:
1. Use both the users email address and “system generated key” to verify the license of the WP plugin.
3. Track and report the number of times it is activated and report the following:
– email address and key used to activate plugin
– domain name where the plugin has been activated
– number of active installs per license
4. The activation system needs to be automated, i.e. when someone activates their plugin, it is instantaneous and doesn’t require the helpdesk to manually activate the plugin.
CLOSING NOTES:
The plugin should be written to WordPress standards located here: http://codex.wordpress.org/Writing_a_Plugin
This page references some other sites with good tips on writing WordPress plugins.
The RSS Feeds also need to pass W3C Feed Validation. This URL can be used to test the validation of feeds: http://validator.w3.org/feed/
If you don’t understand something, or have a question about a feature please ask!
NOTICE:
* Plugin must work with the most current version of WordPress
* Plugin must not be encrypted. I need the full source
* Bids with a working DEMO are priority choices
* Payment when project is completed and tested working
*** You must be well-versed in the English language! I need to be able to communicate with you! ***
*** COMMUNICATION REQUIREMENTS: I require periodic updates on the project status, these can be delivered via email or skype or by phone and will be delivered on Monday, Wednesday and Friday American time. This is not a detailed report but a quick status update so I know the status of the project and can track the progress as well as ensure it finishes on time ***
