Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Prerequisites

All the bullet points below have to be respected if you want to use the new feature on your project

  • Portal & Engine version 2024.4 (or after)

  • New structures

    • portal

    • wkfpkgportal

    • wkfpkgportalaction

    • portaldownload

    • homewidgetelttype

  • Updates on existing structures :

    • asset & all your #damobject structures

    • vueapphomewidget

  • Creation or updates of/on instances for :

    • wkfpkgportal => CREATION

    • wkfpkgportalaction => CREATION

    • homewidgetelttype => CREATION

    • vueapphomewidgettype => UPDATE

    • pkgroletemplate => UPDATE

  • Plugins :

    • PACKAGED_Portals => activated

  • Portal’s configuration :

    • portals config domain added

    • named action actions added in common

    • features config has a new entry called portals, it should be set to true, if you want to use the creative workflow and it is by default activated

1/ Install on existing projects

Common steps

 Details
  1. Permissions

To have correct permissions on portals we also recommend to update or reset pkgroletemplate instances and all the other pkg* objects. If you reset your permissions from the nar, don’t forget to call the update (admin) endpoint given by PACKAGED_Security.
A touch on the users may also be needed to ensure that users, roles and roles templates are correctly synchronized.

If you can’t reset your permissions, you must modify them. You can do this by using wedia-config’s role template menu. For each role template, you will edit it’s “ Global permissions ” permissions.

  • For the “Administrator role type” the permissions should be set to :

    • Create portals => checked ✅

    • Administering portals => checked ✅

  • For the “Contributor role type” the permissions should be set to :

    • Create portals => checked ✅

    • Administering portals => not checked 🟩

  • For the “Userrole type” the permissions should be set to :

    • Create portals => not checked 🟩

    • Administering portals => not checked 🟩

Vassilen Add info about the public role & the added permission secugroup ?

  1. Front app

You will also need to upgrade your portal to retrieve all the new components and configs to benefit from the portals

  1. Asset Libraries

For all your library structures, which are containing assets that you want to use in portals, you will need to update them by adding portals to the structure the same way it’s present on asset structure (tags too).

Install on projects starting on 2024.4

Configuration possibilites

  • No labels