# Error after successful upgrade from 24.0.7 to 25.0.1, "pageMode is not a valid attribute"

**URL:** <https://help.nextcloud.com/t/error-after-successful-upgrade-from-24-0-7-to-25-0-1-pagemode-is-not-a-valid-attribute/150160>\
**Category:** ℹ️ Support\
**Tags:** nc25\
**Created:** [November 18, 2022, 4:46pm UTC](https://help.nextcloud.com/t/error-after-successful-upgrade-from-24-0-7-to-25-0-1-pagemode-is-not-a-valid-attribute/150160 "2022-11-18T16:46:32Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![max-nextcloud](https://help.nextcloud.com/user_avatar/help.nextcloud.com/max-nextcloud/32/76206_2.png) [@max-nextcloud](https://help.nextcloud.com/u/max-nextcloud)\
**Post date:** [November 18, 2022, 9:16pm UTC](https://help.nextcloud.com/t/error-after-successful-upgrade-from-24-0-7-to-25-0-1-pagemode-is-not-a-valid-attribute/150160/5 "2022-11-18T21:16:45Z")

</div>

Looks like this is an issue with the migration to 1.6 of collectives which may persist if updating to Nextcloud 25 and collectives 2.0.0 afterwards.  
This comment has a workaround for enabling collectives again:

> **[Latest Update crashes (#427) · Issues · collectivecloud / Collectives · GitLab](https://gitlab.com/collectivecloud/collectives/-/issues/427#note_1178299860)**
>
> I am on NC stable V24, I just tried to update to the latest collective via the app page in NC it dropped my NC into Mx mode......

Also 2.1.0 with a fix will be published asap.

---

_[View the full topic](https://help.nextcloud.com/t/error-after-successful-upgrade-from-24-0-7-to-25-0-1-pagemode-is-not-a-valid-attribute/150160)._