Comments on: wp-plugins.org expired http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/ Thu, 20 Nov 2008 20:09:18 +0000 http://wordpress.org/?v=2.7-beta2-9638 hourly 1 By: Nuclear Moose Candy - Oops… http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/comment-page-1/#comment-19798 Nuclear Moose Candy - Oops… Wed, 09 Aug 2006 20:34:57 +0000 http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/#comment-19798 [...] Coincidentally, during this same time period, wp-plugins.org, a domain of mine, expired, causing some issues. You can read about it here, and do note my comments to that post. [...] [...] Coincidentally, during this same time period, wp-plugins.org, a domain of mine, expired, causing some issues. You can read about it here, and do note my comments to that post. [...]

]]> By: Glenn Slaven http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/comment-page-1/#comment-118233 Glenn Slaven Mon, 24 Jul 2006 04:18:32 +0000 http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/#comment-118233 Mate, I know the feeling, I has similar hassles trying to move a client's domain a year or so ago. As I updated above, thanks for all your work. <a href="http://wp-plugins.org">wp-plugins.org</a> is a great resource for all us plugin developers, we appreciate that you keep it running off your own back. Mate, I know the feeling, I has similar hassles trying to move a client’s domain a year or so ago. As I updated above, thanks for all your work. wp-plugins.org is a great resource for all us plugin developers, we appreciate that you keep it running off your own back.

]]> By: Glenn Slaven http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/comment-page-1/#comment-17580 Glenn Slaven Sun, 23 Jul 2006 13:18:32 +0000 http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/#comment-17580 Mate, I know the feeling, I has similar hassles trying to move a client's domain a year or so ago. As I updated above, thanks for all your work. wp-plugins.org is a great resource for all us plugin developers, we appreciate that you keep it running off your own back. Mate, I know the feeling, I has similar hassles trying to move a client’s domain a year or so ago. As I updated above, thanks for all your work. wp-plugins.org is a great resource for all us plugin developers, we appreciate that you keep it running off your own back.

]]> By: Craig Hartel http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/comment-page-1/#comment-118232 Craig Hartel Sun, 23 Jul 2006 09:32:12 +0000 http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/#comment-118232 Hi,<br>As is often the case, when things go bad, they go really bad. For some reason the <a href="http://wp-plugins.org">wp-plugins.org</a> domain was gone from my list of domains at my registrar. As it was not visible, I assumed that it was one of many domains I pushed over to Matt some time ago.<br><br>Turns out there was an issue with the registrar and when I suddenly got an email from Matt about it, I went to my domain management and saw that it was not there. I contacted the registrar support and they fixed the issue. I then moved the domain to a new registrar, not knowing that .ORG (and other) domains require an authorization code to be generated by the original registrar.<br><br>Sigh. You still with me?<br><br>Anyway, it took two days to get the authorization code, and as of 1100 hrs PST July 22, 2006 I finished the transfer process. Now it's just a matter of time for the transaction to complete and for the domain to become active again.<br><br>My sincere apologies to everyone for this major inconvenience!<br><br>BTW, this had nothing to do with my own domain being suspended...I simply forgot to renew the hosting package - it was simply coincidental with the <a href="http://wp-plugins.org">wp-plugins.org</a> issue. Hi,
As is often the case, when things go bad, they go really bad. For some reason the wp-plugins.org domain was gone from my list of domains at my registrar. As it was not visible, I assumed that it was one of many domains I pushed over to Matt some time ago.

Turns out there was an issue with the registrar and when I suddenly got an email from Matt about it, I went to my domain management and saw that it was not there. I contacted the registrar support and they fixed the issue. I then moved the domain to a new registrar, not knowing that .ORG (and other) domains require an authorization code to be generated by the original registrar.

Sigh. You still with me?

Anyway, it took two days to get the authorization code, and as of 1100 hrs PST July 22, 2006 I finished the transfer process. Now it’s just a matter of time for the transaction to complete and for the domain to become active again.

My sincere apologies to everyone for this major inconvenience!

BTW, this had nothing to do with my own domain being suspended…I simply forgot to renew the hosting package - it was simply coincidental with the wp-plugins.org issue.

]]> By: Craig Hartel http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/comment-page-1/#comment-17462 Craig Hartel Sat, 22 Jul 2006 18:32:12 +0000 http://blog.slaven.net.au/archives/2006/07/19/wp-pluginsorg-expired/#comment-17462 Hi, As is often the case, when things go bad, they go really bad. For some reason the wp-plugins.org domain was gone from my list of domains at my registrar. As it was not visible, I assumed that it was one of many domains I pushed over to Matt some time ago. Turns out there was an issue with the registrar and when I suddenly got an email from Matt about it, I went to my domain management and saw that it was not there. I contacted the registrar support and they fixed the issue. I then moved the domain to a new registrar, not knowing that .ORG (and other) domains require an authorization code to be generated by the original registrar. Sigh. You still with me? Anyway, it took two days to get the authorization code, and as of 1100 hrs PST July 22, 2006 I finished the transfer process. Now it's just a matter of time for the transaction to complete and for the domain to become active again. My sincere apologies to everyone for this major inconvenience! BTW, this had nothing to do with my own domain being suspended...I simply forgot to renew the hosting package - it was simply coincidental with the wp-plugins.org issue. Hi,
As is often the case, when things go bad, they go really bad. For some reason the wp-plugins.org domain was gone from my list of domains at my registrar. As it was not visible, I assumed that it was one of many domains I pushed over to Matt some time ago.

Turns out there was an issue with the registrar and when I suddenly got an email from Matt about it, I went to my domain management and saw that it was not there. I contacted the registrar support and they fixed the issue. I then moved the domain to a new registrar, not knowing that .ORG (and other) domains require an authorization code to be generated by the original registrar.

Sigh. You still with me?

Anyway, it took two days to get the authorization code, and as of 1100 hrs PST July 22, 2006 I finished the transfer process. Now it’s just a matter of time for the transaction to complete and for the domain to become active again.

My sincere apologies to everyone for this major inconvenience!

BTW, this had nothing to do with my own domain being suspended…I simply forgot to renew the hosting package - it was simply coincidental with the wp-plugins.org issue.

]]>