The MS documentation for the supported version of Handlebars says v4.6.7 (Runtime) and v4.7.7 (Compiler) are supported.
https://learn.microsoft.com/en-us/azure/active-directory-b2c/page-layout
I have a custom B2C policy using the latest version of the selfasserted page layout
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.10</DataUri>.
This page is returning v4.6.7 of Handlebars. Our testing has identified an issue with this version and we need to use v4.7.7.
I can't find B2C documentation on how to implement the compiled version for v4.7.7' using a custom page layout.
Do I need to download handlebars v4.7.7 and reference it in my custom templet page or is there a parameter in the custom policy to enforce the compiler version (v4.7.7)
Any pointers would be greatly appreciated.
Thanks
We control what is rendered here by the page layout version you select, there is nothing else to configure. Make sure the content definition you are putting the page layout in, is referenced by the self asserted technical profile that’s displaying the page you’re inspecting.
Related
I use facebook_audience_network plugin to implement native ad in my app. The problem is the layout the plugin provide doesnt go well with my UI as you can see in the picture.
I also tried modifying xml file in plugin's 'layout' folder but it doesn't change the Native ad Layout.
How can I modify the plugin so that the native ad match the other contents?
A snippet of code would be highly appreciated.
My app UI
It's described as a non-required field, but it's an enum (without any other listed options) and the description is vague: Used by the Application Insights system to determine what kind of flow this component was created by. This is to be set to 'Bluefield' when creating/updating a component via the REST API. - Bluefield.
My rule of thumb is don't include anything extra (KISS) that doesn't break my application, but if there's some benefit I can get out of it, I'd like to know. Thanks!
Reference: https://learn.microsoft.com/en-us/azure/templates/Microsoft.insights/components?toc=%2Fen-us%2Fazure%2Fazure-resource-manager%2Ftoc.json&bc=%2Fen-us%2Fazure%2Fbread%2Ftoc.json
Flow_Type and Request_Source Do not have any effect in the current version, and they might be deprecated in future versions of App Insights API
The Application Insights extensions in Visual Studio and Azure appear to inject the javascript snippet for page view tracking automatically, even though the docs say you enable this with an Application Setting key "APPINSIGHTS_JAVASCRIPT_ENABLED" = true.
Other docs show how to add the same javascript in my layout view, which I did. As a result I'm now seeing the AI javascript twice, once from my view, once from the AI magic. I'd prefer to control this myself -- how can I prevent the tooling from modifying the pages to inject the script? Setting APPINSIGHTS_JAVASCRIPT_ENABLED to false doesn't seem to work.
I'm working in an ASP.NET Core 2.0 web application.
Try upgrading to the lastest version of Microsoft.ApplicationInsights.AspNetCore. They released a new version (2.2.0) today, which resolved the problem for me! The javascript part is not added automatically anymore!
Stormpath's login view https://docs.stormpath.com/nodejs/express/latest/product.html#disable-the-built-in-views doesn't match the styling of the rest of my app. Can I customise the look, either by providing my own styling or replacing the view completely?
I've tried to find documentation on this but all I've been able to find out is that StormPath allows disabling the built in views.
I literally just found the official docs on Customising the Built-in Views 30 seconds after writing that question.
I want to hide a Sharepoint web that has been deprecated (via custom means) due to the release of a newer version, whether it would be making it invisible in the sites and workspaces, or via some special archiving function provided by Sharepoint. Basically I do not wish the users to be able to see the deprecated site.
I was wondering what are the options for doing so, both programmatically or via Sharepoint utils/interfaces?
Thanks.
UPDATE:
The scenario where I want to hide the web from the users (e.g. Webv1.0 when Web2.0 is available) is a bit like, okay, I have version 2.0 of Software X downloaded and installed, and it has converted all of my data into version 2.0 format so it will be compatible with new features. As a user, I would not want to use Software X version 1.0 anymore since it is now old. Of course I would want a backup copy of my data from version 1.0, but I probably don't want to be confused by having a link here which can get me to version 1.0 of the software (and from a developer's point of view, it'll be extra unnecessary work to make version 1.0 being viewable/editable in version 2.0).
I thought of the idea of using security to only allow admins to see everything, but I want to explore other options first e.g. whether it is possible to make the link to the old site disappear programmatically.
Thanks.
Could you just remove all access to that site (by breaking security inheritance) and just allow admins only access to it?
Colin's answer sounds like the way to go. Alternatively you can inject a little bit of JavaScript that automatically redirects the user to the new version of the site.
You can add JavaScript using a content Editor Web Part (one page at a time) or by using the free SharePoint Infuser (all pages in one go).