ATutor

Learning Management Tools







Pages:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15


Content creation creates multiple copies


  • 2005-02-09 09:22:05

    Content creation creates multiple copies

    Hi folks,

    Please excuse duplicate post but I didn't want this Q to get lost at the bottom of another post.

    I have a problem with a vanilla install of ATutor. Most features work except for content creation. Moment I press the 'Save Changes' button it creates 27 (always 27) copies of it in the DB. I have also installed Acollab and that seems to work correctly.

    Another thing that might be important, when I installed it it incorrectly assumed that I was using https and so didn't work and the only way I could fix it was to edit the include/vitals.inc.php file.

    Strange thing is I have a 'test' server that is almost identical and I don't get the problem on that one.

    1st Machine (no problems) Win 2K, IIS 5, PHP 4.3.3, MySQL 4.0.20, Atutor 1.4.2, Browser IE and Firefox both work.

    2nd Machine (problems) Win2K, IIS 5, PHP 4.3.3, MySQL 4.0.23, Atutor 1.4.2 & 1.4.3, Browser IE & Firefox.

    On the second machine the site seems to be fully working other than this problem. If I edit exisiting content it works fine it is only when creating new content I get a problem. IE comes back with a Document can't be displayed error and Firefox throws up a document contains no data error.

    I hope someone can make a suggestion on how to fix this as I really like this system. Of course the machine it works correctly on is only a test box and I can't use it for the live Intranet as it is on a different subnet.

    Cheers folks

    Neil :(

  • 2005-02-09 12:37:36

    Trial and error

    A similar problem has been reported in the past, but we have not been able to reproduce it ourselves, and there does not seem to be anything in the content editor code that might be causing the problem. It does seem to happen on a few IIS installation only.

    Given the only apparent difference in the systems is the version of MySQL, are you able to upgrade your test environment with MySQL 4.0.23 and see if you can reproduce the problem there.

    Or, try upgrading your production environment to MySQL 4.1*