WatchCount.com

When you say “my repository” do you mean a local repository? And what’s the use case here – using SVN for plugin development, or for your WP installation itself?

I don’t have time to look through the checklist, but maybe this free-or-paid SVN client has some kind of polling synchronization feature?

-WCC

That’s a page for a specific WordPress plugin called “WordPress.com Stats” – it seems to be made by the WordPress people, but technically it’s showing stats for itself as a plugin, just like any other WP plugin.

I’d venture to guess that the spikes are when they release updates to the plugin, and users get notified within their plugin admin screen to auto-upgrade at the click of a link. Maybe other promos happen too, to alert users to the new release (a website landing page, email notifications, etc.).

I wonder about the “spike pairs”. Maybe the 2nd spike in a pair is on the weekend when people get around to maintaining their blogs???

-WCC

Just wondering if anyone knows of an easy way to take this 1 step further: the full URL of the page that is currently being displayed.

Thanks!

-WCC

Yes, there definitely is. When I first needed to (learn to) do the same thing, I was a little worried I would need to brush up on mysql commmands. Then I found that there was a layer of abstration that WordPress introduced to make it easier to write to the DB – something like the $wpdb class (in PHP) that gave easy access to the DB.

Then I discovered that they made it even easier for reading/writing/saving plugin preferences to the WPDB without even needing to use objects/classes/etc. Just a simple function, get_option(), retrieves options from the WP DB that you wrote with update_option(). The format is pretty much a simple name-value pair.

As you learn about and play with these functions, here are 3 tips for good implementation:

1) update_option() is great for both adding a new option, and updating one – usually no need to bother with the add_option() function at all.

2) Instead of writing many options to the DB for all of your plugin’s settings, store all of your settings in 1 array, then store that 1 array as 1 simple option in the WP DB.

3) When your plugin is uninstalled/deleted, run delete_option() to remove the option(s) from the WP DB.

-WCC

Which version are you using? For example, Google has a translation website, a translation portion of their toolbar, and the new translator toolbar itself.

-WCC

Jonas:

Actually, I just submitted my first plugin request yesterday, so it’s only been 1 day for me. I’m sure the WP approvers must be a number of volunteers kindly donating their time to review submissions, and given the holidays (here in the US), maybe things might take a little longer than usual.

Sounds like you may be at the same step that I’m at: submitted a request, but haven’t been granted access to svn yet. Correct? In which case, the readme.txt file hasn’t been uploaded/submitted yet, so I guess that’s not even an issue at this point.

1 thing, too: I was under the impression that the Plugin URL we supply during the application process is a link to a home/landing page on our site with information about the plugin — not a .zip file itself. But, I could be wrong about that.

adamt07: Thanks for your input on this process! I’m sorta wondering where along the way you had that “little trouble” — sounds like it was with using svn, no? If that’s the case, then it would seem to be after the approval stage that Jonas and I are currently at.

As for actually using Subversion (svn), I’ve got these URLs in my notes to review, once I have about an hour or 2 to sit down and really absorb it all — and of course have been granted svn access.

http://codex.wordpress.org/Using_Subversion
http://wordpress.org/extend/plugins/about/svn/
http://wordpress.org/extend/plugins/about/faq/
http://subversion.tigris.org/
http://subversion.tigris.org/faq.html

-WCC

Jonas,

I’m not completely sure what the problem is here, but I was under the impression that WP reviews your request before, not after, you are granted access to a svn repository. Frankly though, I’m just relaying this idea from this page.

Judging from the looks of your WP Plugin Dir entry, it doesn’t look like you have included a readme.txt file with the various subsections and so forth. I haven’t used svn myself (yet), but I wonder if you should double-check your check-in procedure and make sure your source files are situated properly. I got the sense that once a developer placed all of their files into svn properly, within 15 minutes the plugin would automatically – and fully – appear in the WP Plugin Dir without further WP approval. But I could certainly be wrong.

-WCC

You might be in the same situation as in this thread. I shared some ideas there. The fact that you registered the domain names with different registrars shouldn’t make any difference.

Good luck,

-WCC