• Resolved ajd777

    (@ajd777)


    I just had an account created for one of my plugins on https://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 https://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: <https://svn.wp-plugins.org:80&gt; 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 (https://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?

Viewing 3 replies - 16 through 18 (of 18 total)
  • 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 (https://svn.wp-plugins.org)

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

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

    Ryan

    (@daobydesign)

    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.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘403 errors when committing to svn.wp-plugins.org’ is closed to new replies.