Skip to content

Commit db6d7c5

Browse files
committed
issue-16_using-subversion-page_new-troubleshooting-section
1 parent b48546a commit db6d7c5

File tree

1 file changed

+18
-0
lines changed
  • wordpress-org/how-to-use-subversion

1 file changed

+18
-0
lines changed

wordpress-org/how-to-use-subversion/index.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -239,6 +239,24 @@ When tagging a new version, **remember to update** the `Stable Tag` field in [`t
239239

240240
Congratulations! You've updated your code!
241241

242+
## Troubleshooting
243+
244+
In this section, you'll find descriptions of the issues you may encounter and ways to solve them.
245+
246+
### svn: E175012: Connection timed out
247+
248+
This issue occurs on the client's (your) side when the server (wordpress.org) takes a very long time to process the input.
249+
250+
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.
251+
252+
To solve this problem, you need to add a special timeout-increasing option to the commit command:
253+
254+
```
255+
svn ci -m "new version" --config-option=servers:global:http-timeout=900
256+
```
257+
258+
In this command, 900 is the number of seconds. Using this trick, you'll be able to bypass the timeout issue.
259+
242260
## Notes
243261

244262
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.

0 commit comments

Comments
 (0)