Supply users with color pickers for both background and text.
And also fix the header fonts to be in line with OOTB webparts, using styles from Heading3 and make it compatible with section background colors.

• Question
  I have implement this extension of "setting a group logo" it works in an environment but it's not working in another environment.
  Can you help me how to debug such extension?

I am experiencing some issues where the "Save As" function will create a file with the filetype docx, but if i download the file it opens up fine as an pdf.

This results in not being able to open the file without downloading it first.

Possibility to add search query to NavigationHeader. Title and Path from the result are used to create the navigation links for the header.

Can for instance be used to dynamically link to all pages within a library with a certain tag.

@tarjeieo We need to make som updates to the button, and are using it in several projects now. Shall I or will you?

Question:
I noted that html files in document library can utilise this renderStreamAsList function to generate a PDF. It doesnt seem to work with images though.

Are you aware of anything which can enable this for me?

tks

We have versioning on in our document library, so I just wanted to check if it was possible to overwrite (create new version) of existing pdfs

Create a webpart that dynamically will render links to all anchor texts on current page

• Initial support for languages 1033 English and 1044 Norwegian (Norwegian is a requirement)
• Configurable properties:
  • Webpart title
  • Header styles to include (Header 1, header 2, Header 3)
• Render:
  • Use current SharePoint theme
  • Style similar/close to modern quick links
  • Indent based on style used

If time/budget permits:

• scroll to anchor (maybe a toogle in property pane to enable)
• expand/collapse
• choose background color (from theme)

See https://github.com/pnp/sp-dev-fx-webparts/tree/main/samples/react-page-navigator for inspiration :)

Features

• Outline/transparent fill or fill
• Icon (fluent)
• Text
• Fill/outline color
• Text and icon color
• Url of choice, not limit to https (support: javascript, custom protocols, etc)
• Tooltip

Next

• Multiple buttons in webpart
• Support flex++

when embedding a document library on another page using the 'document web part/app' the button is shown as 'PdfExportCommandSet', with no icon, and clicking doesn't do anything

In some rare instances, the organisation might want to force the announcement popup for all users once they load a page with the menu/announcements enabled.

We need a field to control this behaviour. The field description needs to explain what happens. "Vis som popup"

Once the field is enabled, all users that load a page with the extension enabled, should get the announcement popup automatically opened.

When closing the notification, the notification will still open next time you navigate the page. If you close the announcement bar, the message will be removed and the popup will not be displayed for the current user for the current browser session.

Pzl.Ext.HighlightHome is good example how to connect Field Customizer with built-in field! But when solution is uninstalled from site, field still remains connected with nonexistent renderer and doesn't render correctly. Is it possible to correctly uninstall this solution ?

By the way. Is it possible to fallback to default renderer if field value is not processed (is not "Home" page doc icon)? Because for example we can easy add default icon for non-Home pages but, it's hard to find required doc icon for file item in Document List.

Hi - nice solution! The previous issue mentions html conversion, but this is not included on the list of acceptable file types. Is there a reason why this is excluded? Thanks

Links on headers in megamenu dosen't work when accessing the menu from Site Content. It works from other pages just not from Site Content.

Any headings created in the CustomTextEditor should create anchor links the same as the OOTB text editor web part. It would also be useful to be able to link to the Title in the Accordion.

I am having an issue where the endPointInfo object is being returned with an empty array immediately following the creation of the MS Teams. This is causing the quick-launch link creation to be bypassed due to the if-statement.

@wobba have you encountered this? async/await logic is already in place on the MSGraph.Get/Put so I'm not sure what else can be done except polling/re-trying.

public static async CreateTeam(graphHttpClient: GraphHttpClient, groupId: string, siteUrl: string) { console.log("Creating team"); await MSGraph.Put(graphHttpClient, beta/groups/${groupId}/team`, "{}");

    let endPointInfo = await MSGraph.Get(graphHttpClient, `beta/groups/${groupId}/endpoints`);
    console.log(endPointInfo);

    if (endPointInfo && endPointInfo.value) {
        let info = endPointInfo.value.find(element => { return element.providerName === 'Microsoft Teams'; });
        let currentWeb = new Web(siteUrl);
        await currentWeb.navigation.quicklaunch.add("Teams", info.uri);
        console.log("Adding teams link");
    }
}`

@wobba thanks again for sharing this – it's a great pattern to follow for run-once spfx extensions to compliment a provisioning solution.

Users cannot remove their added links.
Press the minus button on the added link. It is removed from view in the web part, but not from the Favourite Links list.
When you refresh the SharePoint page, the link is still there.

Latest version installed, node v12, tried in several browsers.

Followed instructions as per the readme.
BTW I am happy to update the project via the O365Cli if this what is required.

npm i npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\colors-d6dc8d0d\lib\system\supports-colors.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\node-sass-31e93abb\test\fixtures\invalid\index.scss' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\blockScopeAwareRuleWalker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\blockScopeAwareRuleWalker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\index.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\index.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\programAwareRuleWalker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\programAwareRuleWalker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\ruleWalker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\ruleWalker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\scopeAwareRuleWalker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\scopeAwareRuleWalker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\syntaxWalker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\syntaxWalker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\walkContext.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\walkContext.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\walker.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\language\walker\walker.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\blockExclusion.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\blockExclusion.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\classExclusion.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\classExclusion.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusion.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusion.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusionDescriptors.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusionDescriptors.js' npm WARN tar ENOENT: no such file or directory, lstat 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics \node_modules\.staging\node-sass-31e93abb\test\fixtures\sass-path\orange' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusionFactory.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\exclusionFactory.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\tagExclusion.d.ts' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\tslint-8b0f78fc\lib\rules\completed-docs\tagExclusion.js' npm WARN tar ENOENT: no such file or directory, open 'D:\Dev\Pnp\Puzzlepart\spfx-solutions\Pzl.Ext.GoogleAnalytics\ node_modules\.staging\office-ui-fabric-react-57ce0cd7\lib\components\Coachmark\Coachmark.js' npm ERR! code E404
Upgrade-report Save as MD.txt

Vi setter ikke header som searchableContent. Tipper det er ganske enkelt, kalle "setRteContentProp" med header informasjonen on update, og sørge for at den funksjonen bevarer content og header i forskjellige "containers" som ikke rører hverandre!

I want to embed a newform in a webpart, but I want to avoid rendering any of the chrome.
the querystring ?env=embedded works great for OOB SharePoint-chrome, but the megamenu is still visible.

I propose not rendering the megamenu when the querystring env=embedded is present.
This is also in line with how SharePoint renders (or doesn't render) its chrome.

const hideMenu = document.location.search.toLowerCase().indexOf('env=embedded')>-1

Hi,

I have an issue where under some folders on SharePoint online, the save as PDF function gets stuck on "processing". If I move the same file (.Docx) to a different folder the save as PDF function works fine.

The download as PDF function always works regardless of the files location. This leads me to believe it might be a permissions issue? I would just like to know if you have experienced a similar issue before.

I have tried to re-deploy the application as well.