JavaScript Custom Actions issueshttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues2019-08-26T14:26:42Zhttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues/2Google Analytics2019-08-26T14:26:42ZLaurent SittlerGoogle AnalyticsCreate a custom action that allow to add a google analytics script with IDCreate a custom action that allow to add a google analytics script with IDhttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues/19PnP Responsive : Oslo Master Page2018-12-06T20:01:00ZLaurent SittlerPnP Responsive : Oslo Master Page## Which Custom Action should you use to report the issue?
[x] SharePoint.UI.Responsive
[ ] SharePoint.UI.StickyFooter
[ ] SharePoint.GA
## Environment
[x] Office 365 / SharePoint Online
[x] SharePoint 2016
[x] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
## Expected or Desired Behavior
When the Master Page was chnaged to Oslo, the Responsive UI has to work like Seattle.
## Observed Behavior
No Responsive Design when the master page is Oslo.
Error to get element **DeltaTopNavigation** and CloneNode (undefined node)
## Steps to Reproduce
1. Create or use a Team Site
2. Enable Pnp Responsive Design by Provisionnig Framework or directly from the PnP-Tools PowerShell Script
3. Check the PnP Responsive works with the Seattle as Master Page
4. Go to Site Settings
5. Click on Change the Look
6. Click on the current theme
7. Select Oslo Master Page
8. Click on Try it out
9. Click on Keep it
10. Resize the window screen... No responsive design available## Which Custom Action should you use to report the issue?
[x] SharePoint.UI.Responsive
[ ] SharePoint.UI.StickyFooter
[ ] SharePoint.GA
## Environment
[x] Office 365 / SharePoint Online
[x] SharePoint 2016
[x] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
## Expected or Desired Behavior
When the Master Page was chnaged to Oslo, the Responsive UI has to work like Seattle.
## Observed Behavior
No Responsive Design when the master page is Oslo.
Error to get element **DeltaTopNavigation** and CloneNode (undefined node)
## Steps to Reproduce
1. Create or use a Team Site
2. Enable Pnp Responsive Design by Provisionnig Framework or directly from the PnP-Tools PowerShell Script
3. Check the PnP Responsive works with the Seattle as Master Page
4. Go to Site Settings
5. Click on Change the Look
6. Click on the current theme
7. Select Oslo Master Page
8. Click on Try it out
9. Click on Keep it
10. Resize the window screen... No responsive design availableSharePoint UI Responsive v2.0.0Laurent SittlerLaurent Sittlerhttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues/24Optimization of the solution for production environment2018-12-06T20:00:58ZLaurent SittlerOptimization of the solution for production environment## Which Custom Action should you use to report the issue?
[x] SharePoint.UI.Responsive
[ ] SharePoint.UI.StickyFooter
[ ] SharePoint.GA
## Environment
<details>
<summary>Expand for output related to your SharePoint Environment</summary>
[x] Office 365 / SharePoint Online
[x] SharePoint 2016
[x] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
<pre>
If SharePoint on-premises, what's exact CU version:
</pre>
</details>
## Summary
Currently the solution could be deployed in production and development environment but for production environment the code should be minified.
Provide minified files and add a parameter into the PowerShell that allow to choose between production environment (minified files) and dev environment (normal files)## Which Custom Action should you use to report the issue?
[x] SharePoint.UI.Responsive
[ ] SharePoint.UI.StickyFooter
[ ] SharePoint.GA
## Environment
<details>
<summary>Expand for output related to your SharePoint Environment</summary>
[x] Office 365 / SharePoint Online
[x] SharePoint 2016
[x] SharePoint 2013
If SharePoint on-premises, what's exact CU version:
<pre>
If SharePoint on-premises, what's exact CU version:
</pre>
</details>
## Summary
Currently the solution could be deployed in production and development environment but for production environment the code should be minified.
Provide minified files and add a parameter into the PowerShell that allow to choose between production environment (minified files) and dev environment (normal files)SharePoint UI Responsive v2.0.0Laurent SittlerLaurent Sittlerhttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues/3StickyFooter : Remote Provisioning2017-03-27T18:50:08ZLaurent SittlerStickyFooter : Remote Provisioning* Create XML Schemas for :
* Infrastructure : support the target that provide Sticky Footer source files)
* Custom Action : an other schema that provide the Sticky Footer as a SharePoint Custom Action
* Create PowerShell Script to provision the Sticky Footer to SharePoint Site
* Create user/installation documentation* Create XML Schemas for :
* Infrastructure : support the target that provide Sticky Footer source files)
* Custom Action : an other schema that provide the Sticky Footer as a SharePoint Custom Action
* Create PowerShell Script to provision the Sticky Footer to SharePoint Site
* Create user/installation documentationLaurent SittlerLaurent Sittlerhttps://gitlab.lsonline.fr/SharePoint/javascript-customactions/-/issues/1StickyFooter : Add init options2017-03-27T18:50:08ZLaurent SittlerStickyFooter : Add init optionsAdd some options with default values if not set as :
- Link List TitleAdd some options with default values if not set as :
- Link List TitleLaurent SittlerLaurent Sittler