Last modified: 2014-10-30 13:11:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T74760, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 72760 - VisualEditor does not display Files, and can not access the local files
VisualEditor does not display Files, and can not access the local files
Status: UNCONFIRMED
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-30 12:07 UTC by Lhug
Modified: 2014-10-30 13:11 UTC (History)
4 users (show)

See Also:
Web browser: Google Chrome
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Parsoid Log w. debug (15.02 KB, application/octet-stream)
2014-10-30 13:11 UTC, Lhug
Details

Description Lhug 2014-10-30 12:07:32 UTC
Intention:
Trying to edit a page with linked files on a private wiki. Mainly to test if the Visual Editor functions are usable.

Steps to Reproduce:
1. Open page with a linked file
2. click "edit"
3. wait and see

Actual Results:  
The linked file simply disappears and is not visible to the editor. after saving, it is accessible again. Trying to insert media showed no local media.

Expected Results:  
Picture is editable of course, and at least a list of media to add.

Reproducible: Always

Using vector as skin. Changing skin did not resolve the issue. Wiki is running on a CentOS with self certified SSL. 
Accessing files that are on the commons is possible, and these are viewable by the editor. Copying the Link properties to other media links does not help, they are still invisible to the editor. Normal Text is editable and media are accessible there. Tried Workarounds found on several pages:

Changing permissions to all-read-true and/or all-read-edit-true did not resolve the issue. (in fact, if I do that, many pictures are not viewable - they are still there and linked, but show broken image)
Granting the ImageSearch read permissions did not help.
granting localhost, 127.0.0.1, our url and our IP read permissions did not help.
2 API-Queries returned expected results (https://dpaste.de/0Adz for ?action=query&prop=imageinfo&iiprop=url|size&iiurlwidth=220&titles=File:Logo.jpg&format=json and ?action=query&prop=imageinfo&iiprop=url|size&titles=File:Logo.jpg&format=json

Locally (on a Ubuntu machine) the pictures are being shown, yet the local media repo is empty to the VE.

We are running parsoid as a service run by root, the log file reports API request failed when trying to edit a page with pictures in it.

The used versions are MediaWiki 1.23.5, VE Snapshot 1.23, nodejs 0.10.30, Parsoid snapshot 1.23
Comment 1 Lhug 2014-10-30 12:43:26 UTC
A direct call of the api query the VE starts shows definite parsing errors.
https://dpaste.de/8AhK is the result of the API-Query on the live system.

https://dpaste.de/DKwm is the result of the same page on the local system.

Notice the imagelinks in the first link are still in [[]].
Comment 2 Lhug 2014-10-30 13:11:44 UTC
Created attachment 16956 [details]
Parsoid Log w. debug

This is the Parsoid log with debugging info when opening a page with a picture in it. Since I have no idea what exactly is happening in that parsoid service, or when it happens, maybe someone else can tell me what to do with this.

The fails API-request is easily notable

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links