MediaWiki Visual Editor Parsoid 404 Error: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
OK, that reminds me, there's a third item I noticed too, which was that a lot of the documentation I was reading had configuration references that were for older versions. I was working with WikiMedia 1.3 and the Parsoid version available on 1.14.2018. A lot of the documentation I read referred to the localsettings.js file (Parsoid service configuration) which appears to have been deprecated at some point in favor of the config.yaml file. | OK, that reminds me, there's a third item I noticed too, which was that a lot of the documentation I was reading had configuration references that were for older versions. I was working with WikiMedia 1.3 and the Parsoid version available on 1.14.2018. A lot of the documentation I read referred to the localsettings.js file (Parsoid service configuration) which appears to have been deprecated at some point in favor of the config.yaml file. | ||
Anyway, I got the Parsoid service installed and working (tested it in all the methods recommended), but it just would not 'talk' with the MediaWiki site. It kept coming up with a 404 (not found) error. | Anyway, I got the Parsoid service installed and working (tested it in all the methods recommended), but it just would not 'talk' with the MediaWiki site. It kept coming up with a 404 (not found) error. Nothing I did made a dent in the issue. Plus there were different suggestions from different sites that had radically different configurations settings that on the surface would seem to suggest there was no way one of these methods ever actually worked. But I tried them anyway to no success. After I got everything working (spoiler alert), I chalked this part of the adventure up to different versions of the Visual Editor, Parsoid, and different 'flavors' of linux. | ||
== The Research == | == The Research == | ||
| Line 20: | Line 20: | ||
Have you checked your apache / HTTPD configuration? | Have you checked your apache / HTTPD configuration? | ||
</div> I hadn't. And it turns out that was the issue. Specifically I had a simple typo in my httpd.conf file (I'm using CentOS 7.4, so the location and name of your Apache / HTTPD configuration file may vary. It may even be in multiple files.) that allowed me to view any page on the site, but didn't allow for editing with the Visual Editor. | |||
== The Solution (continued) == | |||
</div> I hadn't. And it turns out that was the issue. Specifically I had a simple typo in my httpd.conf file (I'm using CentOS 7.4, so the location and name of your Apache / HTTPD configuration file may vary. It may even be in multiple files.) that allowed me to view any page on the site, but didn't allow for editing with the Visual Editor. As near as I could figure out it has something to do with absolute and relative paths. But for the life of me I couldn't figure out how anything had worked at all with that typo, so I gave up on that and just fixed it. | |||
== The Conclusion == | |||
And then everything worked. | |||
Sorry if you were looking for some really detailed instructions or a summary on all the stuff I learned, but my intent was to just share my story and solution. Hopefully it helps someone. | |||
== Final Thoughts == | |||
One other item I ran into was logging for the Parsoid service. At the stage where I was trying to get that service working I figured I'd just check the log files. A large number of sites referred to the log file location at /var/log/parsoid/parsoid.log, but that didn't exist for me. Long story short, I went down the logging rabbit hole for about an hour and ended up giving up as I could never get the service to actually log anything. So if anyone has a 'how to' on that, specifically for CentOS, please write something on that subject. Thanks in advance. | |||
</div> | </div> | ||