Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #16: Enhancing the "Using Subversion" Page: Adding a 'Troubleshooting' Section #17

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Issue #16: Enhancing the "Using Subversion" Page: Adding a 'Troubleshooting' Section #17

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
db6d7c5
issue-16_using-subversion-page_new-troubleshooting-section
WPLake Aug 5, 2024
eabc45a
Update wordpress-org/how-to-use-subversion/index.md
frantorres Jan 3, 2025
846d54b
Update wordpress-org/how-to-use-subversion/index.md
frantorres Jan 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions wordpress-org/how-to-use-subversion/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,24 @@ When tagging a new version, **remember to update** the `Stable Tag` field in [`t

Congratulations! You've updated your code!

## Troubleshooting

In this section, you'll find descriptions of the issues you may encounter and ways to solve them.

### svn: E175012: Connection timed out

This issue occurs on the client's (your) side when the server (wordpress.org) takes a very long time to process the input.

Usually, it happens only with large plugins that contain hundreds of files. For example, contributors to the Gutenberg plugin (which is a part of WordPress but is also available as a plugin) [have faced](https://github.com/WordPress/gutenberg/issues/55295) this issue.

To solve this problem, you need to add a special timeout-increasing option to the commit command:
frantorres marked this conversation as resolved.
Show resolved Hide resolved

```
svn ci -m "new version" --config-option=servers:global:http-timeout=900
```

In this command, 900 is the number of seconds. Using this trick, you'll be able to bypass the timeout issue.

frantorres marked this conversation as resolved.
Show resolved Hide resolved
## Notes

Don't put anything in SVN that you're not willing and prepared to have deployed to everyone who uses your plugin. This _includes_ vendor files, `.gitignore` and everything else.
Expand Down