WordPress.org

1. Ajd777
   Member
   Posted 2 years ago #

   I just had an account created for one of my plugins on http://svn.wp-plugins.org, and I have followed the Linux directions exactly, but every time I try to commit a file SVN returns a 403 forbidden error.

   Specifically (this is a fresh attempt [some stuff trimmed]):

   $ svn co http://svn.wp-plugins.org/inline-ajax-page/

   A inline-ajax-page/trunk
   A inline-ajax-page/branches
   A inline-ajax-page/tags
   Checked out revision 8794.

   $ cd inline-ajax-page

   $ svn add trunk/*

   A trunk/inap.php
   [trimmed file list]

   $ svn ci trunk/*

   Adding trunk/inap.php
   Authentication realm: <http://svn.wp-plugins.org:80> WordPress Trac - Login with forum username

   Username: ajd777
   Password for 'ajd777': ********

   svn: Commit failed (details follow):
   svn: CHECKOUT of '/!svn/ver/8769/inline-ajax-page/trunk': 403 Forbidden (http://svn.wp-plugins.org)

   I've done everything I can (including forwarding all ports, scouring Google, using a client rather than the terminal and starting from scratch several times) to make sure it isn't a problem on my end, but it still won't work. I assume other plugin authors here use it. Does anyone have an idea how to fix this?

2. ElasticDog
   Member
   Posted 2 years ago #

   I get the exact same message as well...not sure how to get around it.

3. JeroenOnstenk
   Member
   Posted 2 years ago #

   Well at least you found already more info about it then I did.

   I'm not experiencing this all as "user friendly".

4. ElasticDog
   Member
   Posted 2 years ago #

   Figured it out...make sure that the username you use to submit to the svn repository is case-matched to your forum account. I kept using 'elasticdog' and it failed...using the proper 'ElasticDog' fixed it right up. That should either be changed or documented somewhere IMHO.

5. GamerZ
   Member
   Posted 2 years ago #

   I got this error message as well when I want to commit my latest plugin (wp-pluginsused).

   BUT I am able to commit older plugins without any problem.

   Wonder the mods got any idea about it?

6. PaulButler
   Member
   Posted 2 years ago #

   I am having the same problem. I can access my old plugin's SVN repository fine, but when I connect to the new one I get the 403 permission denied error.

7. GamerZ
   Member
   Posted 2 years ago #

   I have post it onto wp-hackers list. Waiting for reply.

   http://comox.textdrive.com/pipermail/wp-hackers/2007-August/013861.html

8. Pistos
   Member
   Posted 2 years ago #

   Same for me.

9. mdawaffe
   Member
   Posted 2 years ago #

   I'm working on this right now.

10. GamerZ
    Member
    Posted 2 years ago #

    Thank you Michael =D

11. mdawaffe
    Member
    Posted 2 years ago #

    I think it's fixed now. Please let me know if you encounter more errors.

12. GamerZ
    Member
    Posted 2 years ago #

    yeap fixed =) THANK YOU michael

13. Pistos
    Member
    Posted 2 years ago #

    Fixed for me. http://comox.textdrive.com/pipermail/wp-hackers/2007-August/013869.html Thanks. :)

14. GamerZ
    Member
    Posted 2 years ago #

    @Pistos: are you able to get your plugin to display at http://wordpress.org/extend/plugins/ after commiting?

    I committed 6 hours ago and till now it has not appear there even though the FAQ put 15 minutes

15. mdawaffe
    Member
    Posted 2 years ago #

    GamerZ, you seem to get hit by all the bugs :)

    http://wordpress.org/extend/plugins/wp-pluginsused/

    Should be working now.

16. GamerZ
    Member
    Posted 2 years ago #

    yea, sigh, and you always take the time to fix it. Thank you so much. =)

17. snapshots
    Member
    Posted 2 years ago #

    Here's another 403 error on first-time svn commit to trunk:

    $ svn --username snapshots --password **** ci -m "Initial version"
    Adding trunk/admin.inc.php
    svn: Commit failed (details follow):
    svn: CHECKOUT of '/!svn/ver/18251/snap-shots-for-wordpressorg/trunk': 403 Forbidden (http://svn.wp-plugins.org)

    I'd appreciate it if someone could help me out.

18. snapshots
    Member
    Posted 2 years ago #

    I've created a new post to track my occurrence of the similar issue.

19. DaoByDesign
    Member
    Posted 2 years ago #

    ElasticDog, you're a champ! Cheers, I was having the same problem, kept typing in "daobydesign" and it needed to be "DaoByDesign" - thanks so much.

Topic Closed

This topic has been closed to new replies.