@jsabater Thanks for reporting! I'll have a look, but it seems an error introduced by backporting.

@jsabater Can you please check the traceback to see where has_page_permission is called?

For the moment, you might want to patch has_page_permission:

from cms.utils import permissions
from cms.utils.page_permissions import has_generic_permission

permissions.has_page_permission = (
    lambda user, page, action, use_cache=True: 
        has_generic_permission(page, user, action, site=None, check_global=False, use_cache=use_cache)
)

(sorry, untested)

If has_page_permissionis called from project code, you also might replace the call by a call to has_generic_permission.

Hi, @fsbraun ! The method has_page_permission is called, in my case, from djangocms_page_sitemap/cms_toolbars.py in populate at line 29.

Anyhow, I see that you already proposed a fix, which was merged. Will you be re-releasing 3.11.7 or will you releasing 3.11.8 with the fix?

Thank you for the info!

A re-release is technically not possible. So the fix will go into 3.11.8. Have you tried patching?

No worries, 3.11.8 is fine by me. I am not in a hurry. I have set django-cms==3.11.6 in the requirements.txt file and that works fine. I'll monitor releases and wait patiently :-)

@jsabater 3.11.7 has been retracted and 3.11.8 is coming any minute now