@osobo Moodle package has quite a complicated setup. The app has over 25 (!) plugin types and each plugin writing all over the source code. For this reason, source code is treated as data. /app/code is just the released tarball. The app runs off /app/data/moodle . The package seems to make some best effort update by copying latest /app/code into /app/data/moodle .

Yup, there is a mega change here - https://git.cloudron.io/packages/moodle-app/-/merge_requests/33

Hello, I finally managed to solve the issue as suggested above. I installed a second instance, which ended up working, then created a backup of version 3.1.3 (the one that wasn’t working) and imported that backup into the new instance. Thanks for your help!

Closed due to inactivity

@nebulon Thank you

@nebulon thank you

Thank you, i was uninstall and install it again, it works!

@gdeflaux I am not familiar with Moodle but I have seen Wordpress plugins strip certain tags to prevent potential XSS issues. It became necessary to restructure working content and the theme files to restore functionality that was broken. I would suggest making sure that you know how the CMS handles iframes before adjusting the CSP. LAMP stacks can adjust CSP via .htaccess, PHP header commands, and HTML <meta> directives. Good luck peeling back layers of the onion.

Go to preference [image: 1728070708966-584ccb2b-1ac5-4639-a201-a5f43d823058-image-resized.png] Change "editor preference" to "plain text area" [image: 1728070761442-9bbb4805-e0fd-4238-8ad5-eda9761eaa5b-image-resized.png] Turn on the "Edit Mode" and add an activity or resource, select page [image: 1728070926233-478cb6f2-c674-44d3-ab0a-9689bb5a7d2b-image-resized.png] Then, copy and paste the following code: <link href="https://unpkg.com/editor.md/css/editormd.min.css" rel="stylesheet" /> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.min.js"></script> <script src="https://unpkg.com/editor.md/editormd.min.js"></script> <div id="editor"> <textarea style="display: none;"></textarea> </div> <script type="text/javascript"> $(function () { var editor = editormd("editor", { width: "100%", height: "100%", path: "https://unpkg.com/editor.md/lib/" }); }); </script>

[image: 1724319210408-295f317a-fabe-4891-959f-bbb3bea9fa89-image-resized.png]

Not sure where moodle places the files but it must be somewhere in /app/data . You can always use the web terminal and the find command to locate it . Then , navigate to that folder via the file manager.

But no! What a careless mistake! I didn't even see it Thank you! All is ok now

@taowang yes, since we have cloudron backups (which are app level), we disable the backups inside the app.

OK, that's strange! Let us know if you figure out what changed.

It seems to be correct here in a test install: [image: 1707120164607-7f9aa340-458e-4313-a11c-83a680bbaab1-image.png] What is the package version you are running ? If you go the Cloudron Dashboard -> App -> Update . It will show the package version . Latest package is 2.4.0 which contains Moodle 4.3.0

Thanks for your quick reaction on this matter! With the new version update I am able to get those notifications! Best regards Gio

Great! Thank you so much, the new update solved the problem!

@andirahmat yes, block storage is the correct thing to use for app data directory. But even in block storage, some filesystems like CIFS are not suited (since they don't have permissions and symlink support either). Of course, other filesystems like FAT, NTFS etc are totally out of question.