It probably doesn't help that the latest version of that plugin was for Moodle 2.0. So it's not surprising it doesn't work in 2.8
https://moodle.org/plugins/pluginversions.php?plugin=mod_ejsapp
It probably doesn't help that the latest version of that plugin was for Moodle 2.0. So it's not surprising it doesn't work in 2.8
https://moodle.org/plugins/pluginversions.php?plugin=mod_ejsapp
Matteo, my phpinfo page is in the root Moodle directory, it has the following code:
------------------------------------------------------
<?php
// Show all information, defaults to INFO_ALL
phpinfo();
?>
---------------------------------------
In the Moodle's own phpinfo, admin/phpinfo.php, it has the following line:
phpinfo(INFO_GENERAL + INFO_CONFIGURATION + INFO_MODULES);
Which i changed to:
phpinfo(INFO_ALL);
And now Moodle's phpinfo page shows everything, Apache's Enviroment inclusive. The results are the same as my own phpinfo page:
REQUEST_URI | /admin/phpinfo.php/filename_UTF8_encoded_%E3%81%9D%E3%82%8C%E3%81%8C%E5%8B%95%E4%BD%9C%E3%81%99%E3%82%8B%E3%81%AF%E3%81%9A |
SCRIPT_NAME | /admin/phpinfo.php |
PATH_INFO | /filename_UTF8_encoded_それが動作するはず |
PATH_TRANSLATED | /var/www/html/moodle/filename_UTF8_encoded_それが動作するはず |
ORIG_PATH_INFO | /admin/phpinfo.php/filename_UTF8_encoded_それが動作するはず |
Using slasharguments on, the profile picure on the top right corner is: /theme/image.php/more/core/1432265791/u/f2
If i disable slasharguments, the picture's URL is: /theme/image.php?theme=more&component=core&rev=1432265791&image=u%2Ff2
Still no picture on both tests. But the CSS styles and the allaroud site's visual is the same on both modes. This odd because in the other day if i disabled slasharguments, the page's visuals were not showing ok ... But then, meanwhile, i moved/deleted /moodledata/cache/cachestore_file/default_application/ hmmmm :/
Small notice: In the admin page, for example: My Home Page > Site Administration > Server> PHP Info, The words Site Administration > Server, aren't clickable. Just saying. Nothig serious to me.
P.S.- This forum could have a Preview Post function.
Thanks for you attention so far!
Hi Paul,
that's strange, http://demo.moodle.net/admin/phpinfo.php/filename with a whitespace returns:
QUERY_STRING | no value |
REQUEST_URI | /admin/phpinfo.php/filename%20with%20a%20whitespace |
SCRIPT_NAME | /admin/phpinfo.php |
PATH_INFO | /filename with a whitespace |
as expexted.
This check is important because here in the Community there were posts reporting issues w/ blank spaces in the filename, depending on the fact that those blank spaces were not there in the PATH_INFO as expected. This missing could affect your instance if someone will upload file w/ spaces in the filename.
Apologies for not telling you about the constant missing in the PHPinfo page: FYI, MDL-50415.
Thanks for improving the docs, including XSendfile which makes the difference when serving the files!
HTH,
Matteo
Hi San,
first apologies for not having underlined the missing constant: FYI, MDL-50415.
Your URL is correct in both the configurations: have you already tried using the clean theme?
If you think that Moodle cache is the problem please purge the caches directly from Moodle: deleting them from the file system is a last resort approach ;).
It could be also a permission issue in accessing part of the Moodle file system. Have you already tried to:
?
HTH,
Matteo
P.S.: you've 30 minutes to edit your message and that's the way I manage the "preview", to fix bot typos and formatting issues .
Hi Markus,
that's is a running configuration in a Linux box (an example: https://moopi.mrverrall.co.uk/course/view.php?id=4).
You should find in the log message - http://nginx.org/en/docs/debugging_log.html - the reason why the server starts no more, probably a typo or too many "similar"sections. You should post here the relevant logs, hoping that someone using nginx in Windows will have ideas about your error.
HTH,
Matteo
in https://moodle.org/plugins/pluginversions.php?plugin=mod_ejsapp they say it has been tested with moodle 2.7 2.8 2.9.
It would nice if the powers that be, would include the Atto: Toggle Preview button into Moodle. Comes in really handy and cuts down on clicks. Also, no longer have to worry about the 30 minute edit time running out.
Ok... I would start by making sure you have the latest code from https://github.com/UNEDLabs/moodle-mod_ejsapp.
I feel yery happy for your interest.
I contacted the manteiner, De la Torre, he has provided to remove some misprint and to release a newer version of the plugin that installs succesfully.
Many thanks
Yes, i actually tested with both themes. Same results.
I did what you said. And the only thing suspicious to me, was a "grey" GET when all the rest was green. On this file: /theme/image.php/clean/core/1433019843/f/jpeg-80
After i uploaded a image, there was only a blank image showing the files archive "table". It didn't fetch that image and therefore showed a blank.
But after that, it fetched a preview file (blank) with 200 GET: /draftfile.php/5/user/draft/830028852/porto.jpg?preview=thumb&oid=1433020330
BTW, If i upload that same image to the description area, it works. The image shows when i reload the page.
Am i missing anything, when testing this?
Hi San,
for sure we miss something, we just need to find what .
What do you mean with only a blank image showing the files archive "table"? If the response body contains an HTML error page printed by Moodle (w/ debugging enabled), please post it here.
I could guess that there is an issue with scaling the profile image being uploaded: a permission issue or an environment issue about the GD setup.
You should follow all the network responses, starting from the upload of a new profile image and then viewing it. If you don't feel confident with the browser DevTools, please use WireShark or Fiddler to look at the HTTP responses.
HTH,
Matteo
Thanks Matteo,
Turns out this was just user error, all examples and handled correctly
I tried upgrading moodle version 2.3 to version 2.7, but the database tables are not getting upgraded. I tried it many times, but each time it landed on the same problem.
Please, help me on this regard.
What *exactly* went wrong? What error messages are you seeing?
Hi,
I am trying to create a local environment for a moodle 2.0 based project on wamp server 2.2
but after installation of moodle on wamp , the system throws " 500: Internal error ".
On further search it was found that in Apache error log , the error is :
" .htaccess : All override not allowed here "
I tried fixing this error by checking "rewrite module " in the Apache directives but the system always creates
broken .htaccess file in www directory of moodle .
Please help me in understanding the cause of the same. Thank you in Advance .
Please reply ... it is very urgent !
What are you doing installing a very obsolete/unsupported version of Moodle?
Other than that, show us the contents of your .htaccess file. You've got something in there you shouldn't have.
I got these messages with full debugging turned on. Do any of these provide a clue?
setting controller status to 700
saving controller to db
calculating controller checksum ecbeb7411f1d7519a816f6ca74c249d2
loading controller from db
setting controller status to 800
setting controller status to 1000
saving controller to db
And here are the messages produced during the restoration process...
+1 to what Howard said concerning version ... but to answer your question about apache ...
.htaccess takes it's 'permissions' (so to speak) from the main configuration file for apache ... in the case of a Wonder box I don't know where that is but it's name is either httpd.conf (.cnf) or apache2.conf (.cnf).
In that file there will be definitions for document root and contained in the settings for document root there is a setting for what to allow for overrides. If you allow Override ALL then other overrides can be placed in .htaccess. Override ALL for document root is not normally recommended but if on a Wonder machine Wndows 7 am assuming is NOT for production so, think it might be ok IF apache/mysql and thus Moodle access is not turned on as a service to be launched upon boot up automagically (what one doesn't know is running can hurt!).
Changing the config of apache does require restart of apache for the changes to take affect.
http://httpd.apache.org/docs/2.2/mod/core.html
http://httpd.apache.org/docs/2.2/mod/core.html#allowoverride
'spirit of sharing', Ken