Last updated by Mmeal Comments (8)

The pages plugin allows all the users (you are included) to save and store hierarchically-organized pages of text, and restrict both reading and writing privileges to them. This means that they can collaboratively create a set of documents with a loose collection of people, participate in a writing process with a formal group, or simply use the functionality to write a document that only the creator can see, and only choose to share it once it's done.

The easy navigation menu allows the users to see the whole document structure from any page. They can create as many of these structures as they like; each individual page has its own access controls, so they can reveal portions of the structure while keeping others hidden. In keeping with all other elements in Elgg, they can add comments on a page, or search for pages by tag.

Obviously the admin has super-access to all the pages.


Pages really come into their own in two areas, firstly as a way for users to build up things such as a resume, reflective documentation and so on. The second thing is in the area of collaboration, especially when in the context of groups. With the powerful access controls on both read and write, this plugin is ideal for collaborative document creation.

  • Can you explain in a few not-too-technical words what are these two tipes of pages?

  • Top pages are the root page of a tree, it's a parent to subpages ('page').

    Soon there will just be one type of page though, it's in the works to unify them.


  • If this does not affect the visible user-side website but only the code, and since it's in the work to unify them, I think it is not so important to keep it in this guide section. We'll illustrate it in the developers section.

  • Is it correct: "Obviously the admin has super-access to all the pages."?

  • Can we have the ability to change a page's status.. like wheither it's a parent, or a sub-page under another one?


  • The pages plugin has somehow been deleted in my installation. Can I download it somewhere and reinstall?

  • Just copy this folder to your mod folder in your Elgg root installed directory.

    Hint: you can find this folder on your server in /your_elgg_path/vendor/elgg/elgg/mod/pages

    And don't forget about read+write permissions on this folder/files.

  • If you have installed your Elgg site with a zip archive from I would suggest to download the zip file of the same version you have currently installed again and copy the pages plugin from the extracted zip file to the mod folder in your install directory.

    The path suggested by RvR would be the path where the pages plugin would be when you installed Elgg using the composer method. But then there would also be a symbolic "pages" link from the mod folder in the install directory to the mod folder within the vendor subtree.

    If you have used the zip archive install method and the pages folder is only gone from the mod folder in the install directory you could also copy the pages folder from the vendor subfolder from the path given by RvR because the bundled plugins are available at both locations in the zip archive without symbolic links.