Topic on Extension talk:VisualEditor

The website vojnaenciklopedija.com extension does not work as I have already stated in the title. Successfully installed, however, it stopped half load and reports that it can not connect to the server. Maybe I'm wrong and something I do not know. Here's the code to check:

//  VisualEditor  -   (19.01.2017)  -

wfLoadExtension( 'VisualEditor' );

require_once "$IP/extensions/VisualEditor/VisualEditor.php";

// 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' => 'localhost',

// Parsoid "prefix", see below (optional)

'prefix' => 'localhost'

);

// This feature requires a non-locking session store. The default session store will not work and

// will cause deadlocks (connection timeouts from Parsoid) when trying to use this feature.

$wgSessionsInObjectCache = true;

// Forward users' Cookie: headers to Parsoid. Required for private wikis (login required to read).

// If the wiki is not private (i.e. $wgGroupPermissions['*']['read'] is true) this configuration

// variable will be ignored.

//

// WARNING: ONLY enable this on private wikis and ONLY IF you understand the SECURITY IMPLICATIONS

// of sending Cookie headers to Parsoid over HTTP. For security reasons, it is strongly recommended

// that $wgVisualRestConfig['modules']['parsoid']['url'] be pointed to localhost if this setting is enabled.

$wgVirtualRestConfig['modules']['parsoid']['forwardCookies'] = true;

$wgNetworkAuthUsers[] = array(

'iprange'               => array('127.0.0.1/32'),

'user'                  => 'parsoid');

$wgVisualEditorParsoidForwardCookies = true;

And we temporarily remove the extension until you provide us an answer, because it blocks access to the user settings.

Any?

It's really hard to try and figure out what's wrong without knowing what actually fails.

Can you post the error message that you're getting in the console and/or in the PHP/server logs?

I posted error message way up.

Is Parsoid running? Had a similar Problem with it..

No. Do I need to be adjusted according to this guide? Parsoid/Setup

No try this one Parsoid/Developer Setup.

Option 2 worked fine for me.

Thank you. I will try using the instructions on this page.

Did it work ?

Parsoid is successfully configured, but the visual editor still does not work.

I'm working on the server about it. I'll tell you when I finish that was resolved.

Parsoid is successfully configured, but the visual editor still does not work.

@Zoranzoki21 can you post the errors you're getting now? We can't help without knowing what fails.

https://drive.google.com/file/d/0B5s5frq73YCdT0JWQlUyQjluZ1E/view?usp=drivesdk

Please do not post text as images, as search engines cannot index text which is "hidden" in images. Thanks!

OK

Do not create Phabricator tasks for support requests. Thanks for your understanding.

OK.

Since it is not for the phabricator, as a rule raised here, will someone answer?

As with any other place (mailing list, chat channel, a piece of paper on a tree in the park around your corner) that is run by volunteers, the answer to the question "Will someone answer?" was, is, and will always be: Maybe.

Ok.

So you get a popup saying "(curl error: 7) Couldn't connect to server". What have you tried so far to fix this? :) Searching for that specific error message plus the term "VisualEditor", there are some threads with hints such as Topic:Su2mdhksx4rz6wi6 or Topic:Tjzkjkhe1voerymw (which does not mean that their solutions also work for you). The first link shows where you could investigate.

Thanks for your reply! I will act in accordance with the above, and I'll report the result, whether it succeeded or not.

I did above, but still managed to tip the one mistake that can not connect to the server. See screenshot: https://snag.gy/0bpScH.jpg

Now I get a curl error: 6

See screenshot: https://snag.gy/IWwXRr.jpg

What exactly have you tried so far to solve "Curl error (6): Couldn't resolve host name"?

I have done according to those guidelines only, and after that displays this error when I want to be the visual editor.

So you are saying that you have tried nothing so far to solve that error. (To clarify.) Okay.

I was just trying on the basis of instructions in topics you gave me.

Can you post server error logs? And are you getting any console errors?

Tomorrow during the day I call the provider where my server that I drew log.

@Malyacko @MSchottlender-WMF Here is log file for Februar: https://drive.google.com/open?id=0B5s5frq73YCdbUNfNS0xbF9zOVpUdUV0ODUwcmNPd24wdzVz

However, I just entered the visual editor. I now like to edit, and store changes not. https://snag.gy/UBGvd7.jpg

Nothing I then adjusted the exception of those visual instructions of those topics.

@Zoranzoki21 Look, I really appreciate that you want to use VisualEditor, and that you're trying to install it, but this seems to be getting a little too difficult to help you properly.

VisualEditor is not being supported for 3rd party wikis, partly because it right now requires some access and knowledge into the connection between Parsoid and VE, configuration and log files that most users either don't have, or don't know how to use. It's not a judgment statement at all, but it does make the statement about the fact that issues can arise and that there is no promise that VisualEditor team and contributors will be able to help with those issues.

I don't have time to read a 10mb log file, and while the screenshots you provide are appreciated - they aren't really helpful for me (or anyone else) to properly help you, since they lack the context. We need to know the state of your system, the configuration you've used, whether Parsoid works, what log errors you've received, when the error happens and what you've tried and failed to do.

We can try and see if you can get the relevant data in an organized manner, or you might want to consider not using VisualEditor on your wiki until VE is supporting 3rd party installations.

OK. @MSchottlender-WMF Would you be able to like this? I send to you by e-mail access parameters for cpanel and VHM (which are reluctant to give, because if there is something screws up, fell down to the other domains that are on the server). I would not give this public access parameters, not someone came in and broke down.

In my opinion, private emails do not scale and do not help others. You are free to post information in public after removing/obfuscating crucial information like passwords.

Just tell me how to send a code number that is not public.

There should be no need to post private information or send me or others any passwords. We are not going to log into your wiki and do the debugging for you.

Is not it easier for you to give you the password via private that you see where the error is possibly correct, but to write to each other like this for months. I'm not the only one who complains about something. There are other users. And that they should respond, not only to me.

And if need access to cPanel or complete server?

Again: Noone will log into your wiki and debug for you. Time for everyone who tries to help others is limited, unfortunately, especially as you are not the only one who has questions. Thanks for your understanding.