Extension talk:VisualEditor/2017/04
Add topic| This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
Please note that the Wikimedia Foundation does not provide support for installing VisualEditor on third-party wikis. However, if you have a question we may try to help.
parsoid upgrade broke visual editor
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
trying to use ve we get "(curl error: 7) Couldn't connect to server"
this started after an autoupgrade to parsoid . we use debian . from /var/log/apt/history.log
Start-Date: 2017-04-05 06:27:50 Commandline: /usr/bin/unattended-upgrade Upgrade: parsoid:amd64 (0.6.1all, 0.7.0all) now visual editor is broken. when edit is pressed this pops up: "(curl error: 7) Couldn't connect to server"
Has anyone else run into this? I'll do more searching for a solution. RobFantini (talk) 10:13, 6 April 2017 (UTC)
- just found possible solution here: Talk:Parsoid
- related to nodejs needing an upgrade. RobFantini (talk) 10:42, 6 April 2017 (UTC)
- we use debian jessie, the fix to the issue was to use backports
- aptitude -t jessie-backports install nodejs #
- aptitude dist-upgrade # upgraded parsoid
- Which resulted in these versions and visual editor fixed:
- nodejs Version: 4.7.2~dfsg-2~bpo8+1
- parsoid Version: 0.7.1all RobFantini (talk) 12:04, 6 April 2017 (UTC)
VisualEditor with Extension:Comments
[edit]I have a problem with extension:comments.
In edit mode, extension:comments seems working normally,
but when save the change, I can only see the tags. <comments></comments>
when I go source editing mode and back, extension:comments start working normally.
anything I can do? Please help me if anyone know the solution.
Thanks in advance Libattery1 (talk) 05:17, 12 April 2017 (UTC)
I'm trying to set up Parsoid/VisualEditor on a MediaWiki docker container behind a load balancer and...
[edit]It's not working.
Here's the skinny: I have a CentOS 7 machine with docker installed and running a container which includes Mediawiki and Parsoid. The load balancer routes traffic to the correct port based on the path requested: http://docker/wiki/ -> port 8080 (wiki container). The container also has port 8142 open for Parsoid which the load balancer allows traffic through. I can access the Parsoid endpoint http://docker:8142. I can successfully call the api directly: http://docker/wiki/api.php?action=visualeditor&format=json&paction=parse&page=Main_Page. I can also access the Parsoid server here: http://docker:8142/inside-docker.mathworks.com/v3/page/html/Main_Page. However, when I click 'Edit' on the wiki page Visual Editor ends up timing out and I get an alert stating "http" with no additional details or curl error. In the parsoid log I see:
{"name":"../src/lib/index.js","hostname":"468ec2230f38","pid":520,"level":40,"logType":"warn/api/esockettimedout","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.28.1","msg":"Failed API request, {\"error\":{\"code\":\"ESOCKETTIMEDOUT\",\"connect\":false},\"retries-remaining\":1}","longMsg":"Failed API request,\n{\"error\":{\"code\":\"ESOCKETTIMEDOUT\",\"connect\":false},\"retries-remaining\":1}","levelPath":"warn/api/esockettimedout","time":"2017-04-14T16:57:12.938Z","v":0}
Followed by:
{"name":"../src/lib/index.js","hostname":"468ec2230f38","pid":520,"level":40,"logType":"warn","wiki":"wiki$0","title":"Main_Page","oldId":null,"reqId":null,"userAgent":"VisualEditor-MediaWiki/1.28.1","msg":"non-200 response: 500 <!DOCTYPE html><html><head><title>Internal Server Error</title></head><body><h1>Internal Server Error</h1><p>Set $wgShowExceptionDetails = true; and $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information</p></body></html>\n","longMsg":"non-200 response:\n500\n<!DOCTYPE html><html><head><title>Internal Server Error</title></head><body><h1>Internal Server Error</h1><p>Set $wgShowExceptionDetails = true; and $wgShowDBErrorBacktrace = true; at the bottom of LocalSettings.php to show detailed debugging information</p></body></html>\n","levelPath":"warn","time":"2017-04-14T16:58:04.425Z","v":0}
Any ideas? Why would it work through the API directly and the Parsoid end point but not when called via AJAX from the Mediawiki interface.
Any help would be greatly appreciated. 144.212.3.4 (talk) 17:06, 14 April 2017 (UTC)
- This seems to be similar to this issue but I do not see a resolution: Talk:Parsoid/2015b#h-Failed_API_request-2015-07-20T11:58:00.000Z 144.212.3.4 (talk) 17:21, 14 April 2017 (UTC)
- I've determined this happens only with MediaWiki 1.28.1 and not 1.28.0. Has no one else updated and run into this? 144.212.3.4 (talk) 22:55, 14 April 2017 (UTC)
- If you set
$wgShowExceptionDetails = true; and$wgShowDBErrorBacktrace = true;, like the error message advises, do you get any detailed debugging information? Matma Rex (talk) 11:02, 15 April 2017 (UTC) - Those configuration options were already set and the logs did not give any further details to why the API call is failing. After running a diff against the 1.28 & 1.28.1 includes/api folder the only thing I can think of is the addition of the PARAM_SENSITIVE flag. Could it be that the token param is now marked sensitive and Parsoid is attempting to use it somehow but can't access it? 144.212.3.4 (talk) 14:36, 17 April 2017 (UTC)
- $wgCacheDirectory not being set was causing the issue.
- https://phabricator.wikimedia.org/T161453 144.212.3.4 (talk) 14:58, 20 April 2017 (UTC)
"http" message when trying to edit page using VisualEdit
[edit]I have upgraded my wiki to mediawiki 1.28.1 and installed the equivalent VisualEdit version. Running Ubuntu 16.04 and installed latest Parsoid.
When trying to Edit a page using VisualEditor a got a repated message saying "http". Nothing in the Parsoid log, nothing in mediawiki log or nothing in the apache2 logs.
Testing with "curl -L localhost:8142/wikiv3/page/html/Main_Page/" is working fine and I can also create a new page using VisualEditor.
My LocalSettings.php looks like:
wfLoadExtension( 'VisualEditor' );
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Optional: Set VisualEditor as the default for anonymous users
// otherwise they will have to switch to VE
// $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;
$wgVirtualRestConfig['modules']['parsoid'] = array(
// URL to the Parsoid instance
// Use port 8142 if you use the Debian package
'url' => 'http://localhost:8142',
// Parsoid "domain", see below (optional)
'domain' => 'wiki',
// Parsoid "prefix", see below (optional)
'prefix' => 'wiki'
);
$wgVisualEditorParsoidURL = 'http://localhost:8142';
config.yaml in /etc/mediawiki/parsoid looks like:
mwApis:
- # This is the only required parameter,
# the URL of you MediaWiki API endpoint.
uri: 'http:/localhost/api.php'
# The "domain" is used for communication with Visual Editor
# and RESTBase. It defaults to the hostname portion of
# the `uri` property below, but you can manually set it
# to an arbitrary string.
domain: 'wiki' # optional
prefix: 'wiki'
I have tested removing/adding the prefixes/domains but without success.
Any suggestions? 88.131.107.10 (talk) 14:35, 27 April 2017 (UTC)
- Found the solution: php7.0-curl was not installed... 88.131.107.10 (talk) 14:51, 27 April 2017 (UTC)
Background color changes in edit mode in MW1.27
[edit]I have two wiki's setup. One is MW1.27 and other is 1.28. Both use identical setup/settings as much as possible.
If I edit a page in MW1.28 site using visualeditor, background color remains same as it is in non-editing mode.
See the test case here: https://docs.kogence.com/docs/Test_Page?veaction=edit
But if I do exact same thing in MW1.27 site the background color switches to light grey color.
See the test case here: https://docs2.kogence.com/docs/Main_Page?veaction=edit
Any idea what is going on and how I can fix it? TitusiMW (talk) 23:03, 27 April 2017 (UTC)
- Folks any help with this? TitusiMW (talk) 16:36, 6 May 2017 (UTC)