When publishing is activated on a web, a new "Navigation" link is displayed on the site settings page (which points to _layouts/AreaNavigationSettings.aspx).
I want to change the permission levels which dictate whether this link is visible on the page, however I can't find the CustomAction which installs this link.
Does anyone know which XML file in which feature this is defined in?
It is obvious that this is an out of the box feature, so you can't modify it without invalidating your support :/
What you could do is build your own feature and use a feature with CustomActions to remove and replace the links to the current page with links to the new page you're creating.
Related
Hi I'am trying to test a post purchase extension.
I tried the following steps:
registered my post purchase extension with the code provided
Served the extension using shopify extension serve
Installed the local app extension to firefox
Updated the firefox extension with the ngrok url
Tried to checkout from my development store
-No redirect occurs to the extension and nothing in logs, checkout goes directly to thank you page
if someone experienced could make a basic guide over this topic, that wold be awesome :)
I ran into a similar problem.
For dev stores, the store needs to have checkout extensions preview enabled. You can enable it during store setup in the partners panel. During set up you will be asked what extra features you need.
You need to enable checkout extensions in your main app settings in the partners panel
You need to enable preview mode in extension panel in partners panel. (if your extension is not on the list, remember to build and deploy it)
For checkout UI extension there is an extra step:
go to Online Store -> Themes -> Customize -> Find checkout page -> in customizer click link in the "Optimize your checkout with apps, fonts, colors, and more. Customize checkout" text (IMPORTANT: this will work only on new dev stores or the stores that have checkout UI feature enabled during setup; it's hard to tell exactly) -> scroll to the bottom and add your app.
I highly recommend going through Shopify documentation and tutorials slowly step by step :)
I wasted too much time on this detail.
I am using sitefinity 11 Trial version. I have come across a very strange issue.
I am trying to use Content -> Blogs section, when I click that option in menu, I am redirected to "Sitefinity/adminapp/content/blogs" page. Where it keeps loading, after a while it reloads the page not URL becomes "Sitefinity/adminapp/" then after some time URL becomes "/Sitefinity/adminapp/auth/oidc/sign-in#id_token=XXXXXsomevalue" then it keeps reloading there for always.
I have tried to "switch new interface" on/off but that didn't help either.
I also have created a Dynamic Module but same problem with that too.
I searched about this issue but no help. I also came across the link but this was about customising the Admin backend screens.
Please guide me the right path.
Thanks
Very strange, I opened the sitfinity admin section in Internet Explorer. there I got the message that this browser is not supported, please switch to Classic mode. I again set the "switch new interface" to off in IE.
And I am able to access the Manage screens.
Then I cleared the browsing history on Chrome, re login into sitefinity admin section unselected the "Remember me" checkbox. And I can use the screens in chrome also.
Another thing to check is what type of authentication mode you are using. (In Administration > Settings > Advanced > Security, the AuthenticationMode drop-down). Along with IE not being supported by the new Interface (which Edge, Chrome and Firefox are), the new interface also works best with Claims Authentication, which is Sitefinity's preferred authentication mode. We found that when we switched from Forms Authentication to Claims that we had some similar functionality back even while in the new interface. (Note that in Claims Authentication you'll use a different URL for logging in: https://sitename/Sitefinity instead of https:/sitename/Sitefinity/login with Forms Authentication).
It seems that Google updated their projects console, and when you go to enable an advanced service in Apps Script it no longer directs you to the auto-generated project for your apps script project.
The docs say that a project will be automatically created for apps script projects.
Click Cloud Platform Project link here:
Which takes you to https://console.developers.google.com/cloud-resource-manager where it asks you to create a project.
There is no longer a selection or area to add APIs to the Apps Script project. If I follow that link with an existing Apps Script project that already has working advanced services, it errors out on the project Id.
How can Advanced Services be enabled on new Apps Script projects?
From the page you ended up on, click the "hamburger" icon/navigation menu, and then in the sidebar at the bottom, click "Google Cloud Platform." Then click the same navigation icon, and from the sidebar menu, choose "APIs and Services" That gets you to the page that should open by default.
Your account is automatically loading some other page by default. I could only guess why. We may never know why. The browser and Apps Script probably need to coordinate somehow to know what URL to load, but with the new changes, it looks like something went wrong.
I have a webpart, and I insert that webpart into a site of Sharepoint 2010 (WSS).
I save a site as template by that site. After, I create a new site with that site template. I export this site, and after I import it. I see a error in import site:
"A Web Part with this ID has already been added to this page".
Please help me to fix it.
(It work well on MOSS 2010)
Is new site is on the same farm as the originating site?, I would also asume that this is a Team site with Publishing features or a publishing site al togethere right?, if so, basically is having a conflict of GUIDS for a particular web part within a page or layout. If you see most of the site comming up, then is easier, because you could open the page or layout using SPDesigner and change the guids of the added webparts on the page; if not, you might need to crack open the template file and do it there.
Changing the GUIDS might help you to bring the page up, however any change done of the front-end could reverse the changes, so the best option is to edit the page and re-add the web parts, so it takes a new GUID for good.
I am stuck on developing a mobile view for my SP2010 publishing portal. It is Internet-facing with custom pages / web parts (e.g. http://server/Pages/customPage.aspx with custom webparts on it). The site has a custom master page.
I am having the following issues with the built-in mobile functionality:
The welcome page. Navigating to
http://server/?Mobile=1 redirects me
to
http://server/_layouts/mobile/mbllists.aspx, which just shows a table of lists / document libraries available. For
my portal, I want to show a
dashboard, just like I currently do for the "normal" non-mobile view.
Navigating to one of my custom
pages (e.g.
http://server/Pages/customPage.aspx?Mobile=1)
also redirects to
http://server/_layouts/mobile/mbllists.aspx.
So in effect there is really no helpful built-in mobile support at all; just the ability to view lists with a mobile device.
So I have a number of issues and I'm hoping for some high-level help. My thought is that I should do the following tasks:
Create a separate master page for mobile
Figure out how to choose this master page based on "is client a mobile device?"
Figure out how to prevent the redirection to /_layouts/mobile/mbllists.aspx
Then I think the mobile site will operate similarly to the normal site.
Am I on the right track?
[Edit]
With what I have seen from links from #moontear and other research I've done, it sounds like my best option is to just disable built-in SharePoint mobile support, and just do my own conditional rendering based off of Request.Browser.IsMobileDevice.
Check out the extensive MSDN documentation about how to customize Mobile Views:
How to: Customize Mobile List View and Form Pages
when you check out that page you can see that you can already change the layouts of the list forms and maybe that is enough for you - but as you said you want a custom "Dashboard", you probably want to look into how the mobile redirection works:
Overview of Mobile Pages and the Redirection System
You can set which device is treated as mobile device by editing the compat.browse file as explained in this post: SP2010 Branding Tip #6 – Mobile Browsers, this way the device you set is shown your regular Sharepoint page (answering your questions 2/3).
Copy the "_layouts/mobile" folder to e.g. "_layouts/MyCompany/mobile", in webconfig add following appSetting key:
<add key="mobile_applicationrootdirectory" value="_layouts/MyCompany/mobile/"/>
After that you can add branding, css, etc. to your own mobile folder.
SharePoint is using this by calling SPMobileUtility.GetAppRootDirName()
http://msdn.microsoft.com/en-us/library/ee553908(v=office.14).aspx
using powershell
Disable-SPFeature -Identity MBrowserRedirect -Url http://url