Topic on Extension talk:VisualEditor

Joshua.yathin.yu (talkcontribs)

Functionally, my VisualEditor has been successfully installed on my Wiki on a Windows WAMP Server. The Wiki is located in port 81 and the Parsoid on 8000. I tried using this to edit small pages and it works completely fine (although really have to wait a bit).

The thing is, the communication between the Wiki and the Parsoid workers is seriously slow. A short page requires more than half a minute to finish parsing. The cmd always say the API being not accessible (because the whole port 81 is being consumed by the port 8000 when a parsing instruction is received. It makes it impossible to use the extension. Am I configuring it incorrectly?

Specifics:

  • Windows 7
  • WAMP Server 64-bit 2.5 (Apache 2.4.9), listen on port 81
  • 64-bit nodejs
  • Parsoid listen on port 8000 (paranted by Windows Command Processor cmd.exe)
  • Parsoid configured to communicate with Wiki through localhost, vice versa
  • Users access Wiki by direct IP / hostname (with Apache lockdown; localhost is allowed unconditional access)
Joshua.yathin.yu (talkcontribs)

Actually, it takes around 120140 ms (2 minutes) to finish parsing a single page and hence timing it out. Also, I would want to point out that when parsoid starts parsing, the whole Apache (port 81) becomes inaccessible.

Jazeckel (talkcontribs)

I am having the same problem. Please help! I created a new page with just a single line of text saying "this is a visual editor test." The create worked fine with the visual editor, and it saved fine. Then I tried to edit the page, and it timed out. The output from the parsoid service says "Failed API request, 8 retries remaining." After it gets down to 7 retries remaining, it times out. I then get a message saying "completed parsing in xxxx ms" but I am guessing that's just because I hit cancel on the retry prompt for the timeout.

I am using a private wiki on a Windows 2012 R2 server. I had some issues with the contextify install but I managed to install it manually instead (direct compile with node-gyp instead of via npm) to the directory of the parsoid package and parsoid passed all its unit tests.

89.247.250.82 (talkcontribs)

It's 2021-06-11 today and I have a similar problem: Can create a page using the visual editor but can't edit pages with the visual editor.


Error message on edit is:


"Error contacting the Parsoid/RESTBase server: (curl error: 28) Timeout was reached"

Reply to "Always timeout"