Report any technical problems you discover and discuss solutions.

warnings on login page after update to v3.1

Meer
10 jaren 6 maanden geleden #3465 door ronm
Beantwoord door ronm in topic warnings on login page after update to v3.1
Karl
trying selecting the project in the workspace, holding down shift key and click the edit button to open it in the old Flash editor - does that allow you to edit the project?

If so it's easier to remove code that way than editing the xml directly.

HTH
Ron

Xerte developer & trainer
e-learning & m-learning consultant
mitchellmedia.co.uk | xerteacademy.com | learningapps.co.uk
Note: Support here is voluntary and meant for users to support each other.
Need direct commercial support with Xerte? mitchellmedia.co.uk/contact/

Graag Inloggen of een account aanmaken deelnemen aan het gesprek.

Meer
10 jaren 5 maanden geleden #3470 door tom
Beantwoord door tom in topic warnings on login page after update to v3.1
Could you send me a copy of an unaltered preview.xml

Graag Inloggen of een account aanmaken deelnemen aan het gesprek.

  • 0kee
  • Onderwerp Auteur
  • Offline
  • Senior lid
  • Senior lid
Meer
10 jaren 5 maanden geleden #3476 door 0kee
Beantwoord door 0kee in topic warnings on login page after update to v3.1
I've attached one of the LO that cannot be edited in V3.1. Thanks
Bijlagen:

Graag Inloggen of een account aanmaken deelnemen aan het gesprek.

  • 0kee
  • Onderwerp Auteur
  • Offline
  • Senior lid
  • Senior lid
Meer
10 jaren 5 maanden geleden #3485 door 0kee
Beantwoord door 0kee in topic warnings on login page after update to v3.1
Just a quick update on this, it may provide a clue to my issues. I was booted off the server where I have xerte hosted twice today for mod_security violations, specifically rule 340016 which Google tells me "This occurs when using the code editor to edit php code. If you try and save code changes (by pressing the edit button at the bottom of the code editor) and you do not receive a confirmation pop-up message, then this is the most likely cause."
What triggered it was just a bit of trial and error to try and figure out what was causing the problem. I was copying text from one of the V2 LO to a new V3,1 LO. When I came to something preventing it publish I would keep stripping it back to try identify the problem. I had stripped it back to a couple lines of plain text and that was still throwing up the error which led to my IP being blocked?

Graag Inloggen of een account aanmaken deelnemen aan het gesprek.

Moderators: ronmjultenJohnSmith
Tijd voor maken pagina: 0.142 seconden
Copyright © 2026 The Xerte Project.
Xerte logo Apereo logo OSI Logo