Closed perler closed 10 years ago
Hi, thanks for reporting your problem. I tested the installed on my local machine with "." as target installation path. On my machine the wysiwyg controller works. I got no error. Only to clearify what the install command does:
Problem could also be in Nginx configuration. Status code 499 means "client has closed connection". Can you provide your Nginx Configuration?
sure: https://gist.github.com/perler/8254617
I just realized, that another installation on the same server has the same problems (the wysywig editor was disabled there, so it was not appearent in the first place). this installation was also installed with n98 but I tend to think it is an nginx problem. this is an installation on a virtualmin server (my own), in the end is there the problem somewhere..
@perler I cannot really reproduce the behavior. For some time i published a project in github which creates a complete virtualbox with vagrant and puppet. The Magento installation inside the box is done by n98-magerun. If i start the machine i have no problems to save any CMS page in Magento Admin.
You can test this on your machine.
https://github.com/cmuench/Magento-Vagrant-Puppet-Nginx
The Nginx Config can be found here:
I'm not quite sure, if it is even n98 related, but I suspect it.
do this:
in this case, i get a spinning wheel, nothing happens and my nginx writes a return code 499 (?!) into the logs for requests which point to the wyswig editor. as it is actually enough when you try to leave the page, this seems to occur when loading the page, not when saving it.
when you disable the wysiwyg editor, everything works when you install anywhere else than in the root, everything works
could this be a problem of n98 when setting values while installing? I never had something like this in an installation from the magento source and we know, that magento can be picky when it comes to paths, trailing slashes and whathaveyou..