say I am trying to publish an article to a tenant from my main orchard site. how would i go about creating a module where i can select the content i want to publish and then publish it to the tenant I want. would I use xmlrpc to post to it or is there another method.
It is already done.
See http://www.youtube.com/watch?v=2VpIOjSJwFo&feature=share&list=PL49EB89430968C7D4 for a demo, and http://orchard.codeplex.com/discussions/402151 for the discussion of the feature. This is most likely going to be in 1.7.
Related
I have tried to save the SharePoint communication site as a template that contains apps. I have faced the below error.
Sorry, this site can't be saved as a template. It contains apps that don't work in templates.
Please check social.technet.microsoft.com link for the same issue.
The above link suggests removing apps and saving the template of the site. But I will need a site template with apps. Can anyone suggest how to save SharePoint communication site as a template with apps?
Refer to this official article:
https://learn.microsoft.com/en-US/sharepoint/troubleshoot/sites/fails-saving-site-as-template
If the site contains apps that can't be saved as part of the template, it's necessary to remove any affected apps that are listed in the error message, and then save the site as a template.
If you want to use the app after you save the site as a template, you'll have to add it to the site again.
If you want to use the app in a new site based on template, you need to manually add it in the new site.
I have newly started exploring capabilities of Azure DevOps Wiki. I have multiple projects in Azure DevOps. I want to create one separate project to store Business & Technical documentation for all my projects in a centralize place. How can I add multiple Wiki pages to keep this organize.
Second question is I have a predefined structure for the documentation. For eg. Purpose Of Application, Local Build Steps, Deployment Steps, Third Party Control used, etc. How can I create & store this as a template so that whenever a new project documentation is to be created this document can be used as a placeholder to be followed by everyone.
How can I add multiple Wiki pages to keep this organize.
In Azure Devops, Wiki is similar to another kind of Repo. You could Clone Wiki to the target project and Publish the code as wiki.
Here are the steps:
Use the Clone wiki option to get the URL from other projects.
2.Navigate to the target project -> Repos. Use the import repositoryoption to import the wiki to the Repo.
Use the Publish Code as wiki option to publish the repo as wiki page.
Here is a doc about clone wiki.
How can I create & store this as a template?
Azure Devops doesn't support creating wiki templates now.
Here is a suggestion ticket about this feature. You could vote and add comments in this ticket.
Hope this helps.
My company currently uses Jira and Confluence. In this setup, it is very easy to link a Jira ticket to a Confluence page, via a simple search inside the create link dialog.
We're now looking at moving to VSTS Work Items and Sharepoint. I'm wondering whether VSTS Work Items and Sharepoint are strongly integrated as well. Is it easy to insert a link in a VSTS Work Item to the latest version of a Sharepoint document?
The VSTS isn’t integrated with on-premise SharePoint, but you can add the link to the work item (Hyperlink type). So, they aren’t strongly integrated.
as workaround in Azure DevOps you can add a link to work item's description (enter to Description field, use icon "Create link" and paste this link to window which appears).
I've recently create a site template on our SharePoint online environment which did originally have site publishing features enabled. This was done by setting the appropriate flag to enable saving as a template and then using the url /_layouts/15/savetmpl.aspx to save it.
When creating a site from this template i get intermittent errors indicating something went wrong but with no further detail other than a correlation ID. It's not every time and it happens occasionally when using the site.
A couple of questions on this.
a) What with the publishing infrastructure is not supported within Site Templates.
b) What is the best approach to create a custom site template where i can have a custom front page containing web parts and content, based on the publishing page layouts. I've searched through a significant number of posts online and cannot find a definitive answer to this.
Any help is much appreciate. Thanks in advance.
Grant
Please follow the below steps to create Site using custom template :
1.Firstly create site using custom template and select "upload site template later" or "upload solution later".
2.Then go to your created site and firstly enable publishing feature before uploading your site template to the solution gallery.
3.After that just go to the "Solutions" under "Web Designer Galleries" and upload your "Site template".
4.Now go to Site settings and select "Sites and workspaces" under "Site Administration".
5.And you can create your Custom site. you can see your uploaded Site template in Custom tab
Feel free to ask question if you have any doubt.
I'm creating a PerformancePoint (henceforth PP) Dashboard that contains a web report to be deployed to the a SharePoint web application that I had created. I followed the instruction in the link below.
Deploy a PerformancePoint dashboard to a SharePoint site
In summary, following the instructions in the link, I published the Dashboard to the PP site. Then, I added my account in PP as Creator in the Application level, Editor in both the Dashboard and the Web Report. In the SharePoint site, I added my account under Contributor. I even added the PerformancePointDefault.master just to be sure.
Now, when I deploy my Dashboard to a Report Library, I was able deploy the folder for the Dashboard, but not the Dashboard Page file.
I googled for this, but I could not find any article helpful.
UPDATE 2009-09-30:
I was able to resolve the issue by creating another site collection. Maybe the first site collection is messed up.
I had the EXACT same problem. I was about to take the best advice I could find and delete my site collection and create a new one from scratch, but by the grace of God, I had one final thought.
In our case, the site created was originally http://ServerName but we later added a host header (i.e. http://BiSite). I had been deploying the dashboard using the host header the entire time, so I decided to try using the original name of the site using the server name and viola, the dashboard finally deployed correctly, pages and all.
When you publish a dashboard in MOSS, you have to make sure that you select Publish a Major Version in the dashboard page's drop-down in the report library.
Why is this a community wiki? Seems like there should be a right answer to this question...