Community forums
Page Rendering Issue
Quote from Jermaine Snipe on December 3, 2019, 3:25 pmHello all:
We recently stood up a new site collection, and I moved all of the artifacts/widgets/files/pages from an existing site collection. Users that were recently added to the new site collection (none of these users have Full Control rights) cannot see any of the widgets on the home page. The widgets were rendered through the Akumina generator. The home page is checked in and published. I compared the configuration of the old and new site collection and I don't see any differences. Is there a setting I missed that would allow users with Design rights or lower to see the widgets on a page?
Hello all:
We recently stood up a new site collection, and I moved all of the artifacts/widgets/files/pages from an existing site collection. Users that were recently added to the new site collection (none of these users have Full Control rights) cannot see any of the widgets on the home page. The widgets were rendered through the Akumina generator. The home page is checked in and published. I compared the configuration of the old and new site collection and I don't see any differences. Is there a setting I missed that would allow users with Design rights or lower to see the widgets on a page?
Quote from Scott Kearney on December 4, 2019, 12:34 pmIs the site multi lingual? And when you deployed the widgets, did you use ml=true?
Is the site multi lingual? And when you deployed the widgets, did you use ml=true?
Quote from Jermaine Snipe on December 4, 2019, 1:08 pmNo sir, the site isn't multilingual. When I deployed the widgets, I had ml=false in the .env file.
No sir, the site isn't multilingual. When I deployed the widgets, I had ml=false in the .env file.
Quote from Scott Kearney on December 6, 2019, 9:09 amI would log a support ticket - most likely it is something small and easy to resolve.
Also - "moved all of the artifacts/widgets/files/pages from an existing site collection" - how was this done? if you look in the WidgetProperties_AK list in the site, locate the SiteId column. Does that match the destination site ID or the OLD one? If the old, change it to the new, redo the widget cache and retry.
I would log a support ticket - most likely it is something small and easy to resolve.
Also - "moved all of the artifacts/widgets/files/pages from an existing site collection" - how was this done? if you look in the WidgetProperties_AK list in the site, locate the SiteId column. Does that match the destination site ID or the OLD one? If the old, change it to the new, redo the widget cache and retry.
Quote from Jermaine Snipe on December 6, 2019, 10:42 amEverything was moved via Visual Studio merge operations to a new branch in Azure DevOps. It looks like the issue has been resolved; there was a permissions issue on our side. I'll update if we run into any more issues. Thanks.
Everything was moved via Visual Studio merge operations to a new branch in Azure DevOps. It looks like the issue has been resolved; there was a permissions issue on our side. I'll update if we run into any more issues. Thanks.
Quote from Scott Kearney on December 9, 2019, 8:57 amGot it - thanks for the update!
Got it - thanks for the update!