Hi,
AutoView is still a maintained plugin, we are actively using it on our own Moodle servers. I also have a Moodle 2.4 test
server and I can confirm that AutoView does work on this Moodle release (Using PHP 5.4,
Apache,
MySQL and Linux). Further releases will be forthcoming as time permits.
The Moodle 1.x _utf8 directories are present in the plugin because we are still supporting Moodle 1.x, the plugin has an abstraction layer which maps Moodle 2.x methods onto the Moodle 1.x APIs, thereby allowing the Moodle 2.x plugin to work unmodified on Moodle 1.x. This saves us a lot of effort since it means that we don't have to maintain two separate codebases for Moodle 1.x and 2.x. ?> is used because I think it should be there, though I appreciate I may be in a minority on that one. It has yet to cause a problem in any of the plugins I maintain.
Moving on to the actual problem:
The stack trace posted doesn't seem to reference any part of the AutoView code, so at first glance this doesn't seem to be an AutoView problem, I would expect at least one page from the plugin code to show up somewhere in the stack trace if it was. That doesn't discount an AutoView problem entirely however, since there are reasons why AutoView might not show up directly.
Can you confirm a few other things for me please:
1 - Which version of PHP are you running?
2 - Which database do you use?
3 - What OS are you running?
4 - Do you have the latest versions of the Course Files Area Repository and Repository File Manager installed and enabled as per the installation instructions (see the readme.txt file)? AutoView will not work without them.
5 - Does the module settings page for AutoView in Site Administration work? If there is a problem reading the language files then I would expect some kind of problem here as well.
6 - If you create a new AutoView instance from the course home page, does this work?
You say: "When i change the video and slide options in autoview database table and create folder in moodledata for video and slides it works fine."
Can you explain in more detail what you mean by this? Editing the autoview table in the database directly isn't recommended, putting in the wrong values could easily cause unexpected behaviour and crashes. Also, if you are accessing the moodledata directly with the OS file manager or an
FTP client to create the folders inside moodledata, please make sure that you have set the correct file permissions for read/write access by the webserver process, if you don't there will be problems. However, this is not the recommended way to manage files for AutoView, the only supported method is to use the Repository File Manager.
Editing the .avx file created for each presentation is unlikely to cause the problem you are seeing, but it's still not recommended unless you are skilled with
XML coding.