How to create a modern subsite in a classic team sitecollection?

We are using SharePoint Online in O365. We have a classic teamsite as intranet which is also our root SharePoint site from our tenant (http://myCompany.sharepoint.com). I would like to create a subsite but would like to make it modern. For example modern sitepages, document libraries and lists. How can I do this?

Ps. the classic team sitecollection needs to stay classic.

Calling Graphi API from Classic JavaScript through msal.js

I am trying to do silent login through msal.js and then trying to call graph api but always I get 403 error. When I decrypt my access token through jwt.ms I can see that audience is correct but scopes are showing wrong. Hope some can help me.

My code

let config = {     auth: {       clientId: _spPageContextInfo.spfx3rdPartyServicePrincipalId,       authority: `https://login.microsoftonline.com/$  {_spPageContextInfo.aadTenantId}`,       redirectUri: 'https://xxx.sharepoint.com/sites/xxx-Dev/Pages/myportal.aspx',       validateAuthority: false,       postLogoutRedirectUri: window.origin,     },     cache: {       cacheLocation: 'localStorage',       storeAuthStateInCookie: true     }   }    let myMSALObj = new Msal.UserAgentApplication(config)   let graphConfig = {     graphGroupEndpoint: "https://graph.microsoft.com/v1.0/groups"   }    let request = {     scopes: ["https://graph.microsoft.com/.default"]   }     myMSALObj.handleRedirectCallback(response => { console.log(response) });   //const idTokenScope = { scopes: [_spPageContextInfo.spfx3rdPartyServicePrincipalId] }    const handleError = (error) => {     if (error.errorCode === 'consent_required'       || error.errorCode === 'interaction_required'       || error.errorCode === 'login_required') {       //myMSALObj.loginRedirect(idTokenScope);       myMSALObj.loginRedirect(request);       return;     }     throw error;   };    const getToken = () => {     const date = new Date();     const user = myMSALObj.getAccount();     if (!user) {       //myMSALObj.loginRedirect(idTokenScope);       myMSALObj.loginRedirect(request);       return;     }     //myMSALObj.acquireTokenSilent(idTokenScope).then(response => {     myMSALObj.acquireTokenSilent(request).then(response => {       console.log(`$  {date.toLocaleTimeString()}`, response.accessToken);       callMSGraph(graphConfig.graphGroupEndpoint, response.accessToken, graphAPICallback)     }).catch(handleError);   }   getToken()    function callMSGraph(theUrl, accessToken, callback) {     var xmlHttp = new XMLHttpRequest()     xmlHttp.onreadystatechange = function () {       if (this.readyState == 4 && this.status == 200)         callback(JSON.parse(this.responseText))     }     xmlHttp.open("GET", theUrl, true)     xmlHttp.setRequestHeader('Authorization', 'Bearer ' + accessToken)     xmlHttp.send()   }   function graphAPICallback(data) {     document.write(JSON.stringify(data, null, 2))   } 

My decoded token enter image description here

My app permission enter image description here

About Commanding in UWP apps. What commanding approach is best? office like?, UWP? or classic win32?

I’m writing an app with platform UWP-Windows 10-1903(Universal Windows), for making electric circuits, designs and simulations. User makes a design on screen with resistors, generators, etc, and run simulations in time and frequency domain. It is intended for professional use, and non-free.

Target devices are Desktop (keyboard + mouse) and Tablet (finger touch). It could be nice to add Phone option, but it couldn’t be possible because Windows Phone died.

I did choose the develop with UWP platform because the Store helps much with the infraestructure for selling the app. Multi device paradigm is also attractive, user could work hard in the desktop, and then check a couple things in tablet mode when he or she is drinking a beer in the bar.

That said, i’m trying to design the commanding pattern.

App will have at least 50 commands, grouped in 10 menus. Remember, app is meant to be pro, and there are many tools and dialogs for helping the user to make his or her design. The app is charged with knowledge in electronics.

(for displaying the data, i don’t use page navigation, I use the SyncFusion Window docking manager, because there could be many windows with data, curves and circuits. To navigate back and forth all time could be annoying)

Possible approaches for commanding are:

  1. “Classic like win32” MenuBar, with icon+text for menuitems. That includes the file menu.
  2. UWP CommandBar at top, with icons, and menu flyouts. Seems nice and attractive.
  3. Ribbon menu bar, and Backstage view (for file commands menu). Like MS Office 2016, 2019.., etc

My question is, which approach should I choose? and why?, i’m like hesitant.

I saw many examples of different Windows and UWP apps. But there isn’t a consistency, and each app seems to follow its own preference.

Examples:

  • Paint 3D: has a top command bar, but with Backstage View for “file menu” commmands.
  • Win10-1903 Classic Paint: Has a Ribbon bar for Home and View Command groups, but with no Backstage View, just a classic file menu at top-left.
  • Office 2019: Full Ribbon menu, with Backstage View for “old file menu”. Settings command in backstage view
  • Microsoft Edge: Has a top command bar, but with the majority of commands grouped as secondary commands, that pops out like a flyout menu with the … button.
  • Win10-1903 3D viewer app: Has a UWP menu-bar (icon+text items), but the file commands are in a simple menu in classic format! (what happened with the backstage view??), another weird thing, the settings (gear icon) command is in the Help menu, not in the file menu.
  • (Store) DrawingBoard-Pro: Has top command bar, but file commands are in a bottom command bar.
  • Windows BuildCast UWP Sample: Navigation pattern with hamburger icon at top-left corner, almost no commanding. Settings command at the bottom of the nav pane.
  • Win10-1903 Video Editor: Has top command bar with a few primary and another few secondary commands. nice example.

All of those different and inconsistent examples gave me doubts about what to do. What approach should I use for my app? for instance, should I put a Backstage view?

Following, I add a side question, a thing that concerns me very much. Seems much of apps in the MS-Store are like toys or crappy.., and not oriented for serious work. I mean there are no serious big apps like a CorelDRAW, and AutoCAD, an Adobe Photoshop, and Autodesk Eagle or so. All of those little apps in the Microsoft Store, looks very nice in their UX, but are very limited in their capabilities (and cheap). And UWP apps that have desktop counterparts, are inferior to their dekstop versions.. (VLC player is an example), why all of this?

I mean, in the store, there are many apps like for viewing the human body atlas, apps for consulting the chemical periodic table, apps for checking the physics laws or calcuting resistors for a voltage divider, apps like social networks, apps for listening music, apps for checking weather, watch movies, play games, e-mail, calendar, etc. It’s like the usage pattern is open app –> use app –> close app.

But there are almost no app with the classic usage for design pattern, like: new or open file –> user edit his or her design –> save file –> share or send by e-mail, or print in paper. It seems like the apps are no more “file oriented”, is that “old fashioned”?

If I’m willing to develop a serious app for making electric/electronic designs, UWP and the MS Store is not best approach or option?, should I develop in WPF?

Thanks in advance, and sorry if I made this extremely long.

Go to classic results page link is wrong, where do I change it?

In the modern search at the bottom you get the “go to classic results page”.

In my case it says ...tenant.sharepoint.com/search/results.aspx while the correct address should be ...tenant.sharepoint.com/search/PAGES/results.aspx.

I went to many places to correct this (mostly the search site collection or the main root site collection in search settings) but it does not work, it is still redirecting wrong and giving a ‘page not found’ error.

SP 2010 Site Collection Migration to SP 2013 On-Prem to SP 2016 On-Prem to SP 2019 On-Prem | Moving from Classic to Modern Pages

I am new to an organization that is making the move from SP 2010 to SP 2013 to SP 2016 to SP 2019. These are all on-premise versions. The site collection has almost 3500 sites. There are lots of customizations – webparts that include more content editors that point to both jquery and html files.

For testing purposes, a team upgraded from SP 2010 to SP 2013. Nothing broke – yet. My concern is when they migrate to SP 2016, and the modern pages are turned on – content editor webpart does not exist in modern pages – SPFx rules. What happens on those pages where content editor webparts have been used for purposes of pointing to files? Is there a document for the best practices?

how to use media queries with javascript in my web parts – classic mode

I have a site that is using the pnp responsive and the webparts are responsive. But i’m using a jquery (easypaginate.js) in the webpart.

When i resize my webpart how can i dynamically change the step option to show only 3 li items when i resize the screen to let say 500px using (media queries) @media (max-width: 500px)

Below is the default setting options

$  ('ul#items').easyPaginate({         step:7,         nextprev:false,         numeric:true     });  } 

I want the step to be 3 when i go on a smaller screen. Thanks in Advance

Embedding Microsoft forms in SharePoint online to show (Questions and Responses) – Classic mode

I would like to use the Microsoft forms for a quick poll on an intranet (Classic mode) and was wondering if there is a way to redirect the user to the responses page/link after a survey or poll has been submitted? Or a way to have the questions and responses tabbed side by side?

Any resources or tips would be appreciated

Modern Team Site document library page in SP2019 does not show Exit classic experience option

I am working with SharePoint on prem 2019 and have a team site created in modern experience where several document libraries have been added. When site is accessed and document library link is clicked from quick launch, it opens up in modern UI. Once return to classic sharepoint is clicked, it takes to the classic experience. Once on the classic UI page, I do not see ‘Exit Classic experience’ link on the lower bottom left to go back to modern ui at all.

What could be the cause of this, can someone please assist, thanks in advance.

SharePoint Classic view via URL parameter

Is it possible to force SharePoint to use Classic experience with URL parameters?

(For example https://companyname.sharepoint.com/Lists/ListName/AllItems.aspx?ClassicExperience=True)

There is a Bookmark list that we uses on a daily basis, but some of our custom developed pages are not properly showing in the Modern experience, and our colleges have to click on “Change back to old SharePoint” link every single time.

There is a link that leads to the Classic SharePoint:

<a class="LeftNav-notificationLink" role="menuitem" data-bind="attr: { href: $  data.url, target: $  data.openInNewTab &amp;&amp; $  data.openInNewTab() ? '_blank' : null, tabindex: $  component.isLeftNavVisible() ? 0: -1, 'aria-label': $  data.altText }, visible: !$  data.show || $  data.show(), click: $  component.onClick.bind($  component), automation: $  data.automationId, automationType: 'Link'" href="#" tabindex="0" aria-label="Kattintson vagy nyomja le az enter billentyűt, ha vissza szeretne térni a klasszikus SharePointra" data-automationtype="Link"> <span class="LeftNav-linkText" data-bind="text: $  data.text">Vissza a klasszikus SharePointra</span> </a>