How to recover from accidental deletion of the default feed - azure-artifacts

I have accidentally deleted (and then permanently deleted) the default feed which is created for a new organisation. I am now trying to create a new feed, which I realise will be project scoped, by going into the Artifacts section and clicking to add a new feed.
But, I can't get that far because as soon as I click on Artifacts, I get an error because of the deleted feed:
I'd really welcome a pointer on how to recover from this. Ideally, I'd like to recreate the original organization-scoped feed.
Thanks, Nick.

This issue occurred when I deleted the default feed. The issue is reported in visualstudio.com developer community. Below is the solution provide in the community
[Workaround]
The problem extends to the whole organization, if you delete a feed permanently from one of the projects, you will not be able to see the feeds in any other projects within the organization.
A quick workaround to fix the problem, go to User Settings > Preview Features > New Artifacts (Feeds) Experience turn it off
View your feeds with the classic version, if they appear, then you can turn that feature on again.
Click here for the solution link

Related

Jira: Adding a Link to in issue doesn't work for a project

I've been using Jira recently and I came across a problem that I don't know how to fix it.
I have to Jira instances. when I try to link an issue to one on the other instance it doesn't link. It used to work but now it won't.
every time I try to link it I will get this even though for other projects it wasn't needed :
and when press authenticate I get this page:
afterward, when I press the link nothing changes.
Please if you are familiar with this problem help me.
afterward, when I press the link nothing changes.
I tried to link the other way and it's working but I still can't identify where the problem is.
Please if you are familiar with this problem help me.
It's all about Application Links.
Some server changes (like reverse proxy, update in web.xml, etc.) or changes in the admin user account may break the links.
You need the check Application Links between two instances; if there is a problem, try to solve that first.
If not, remove the application link from both instances and add it again.
By the way, if the users in the two Jira instances are same, enable the "OAuth" in the application links (and also be sure that the admin account is same on these two instances.)
Sources:
Linking issues
Application Links

Cant create new team project in TFS 2010

I have an old setup with a tfs2010 and sql2008 and the current Collection is holding 3 team Projects. Now i want to create a new team project but for some reason i cant. it seems that it has something to do with the SQL Reporting that dosent excists. i get an error TF218027.
Ive been going through the setup and im wondering a bit
What exactly does the TFS use the reportServer for (MSDN dosent seem to want to tell me)
is there any way to create a Team project without the reporting
Will it damage my excisting data if i create and connect to a new sql reportServer
Hope someone will take the time to give an answer
thanks.
I have already tried the different approtaches discussed on different threads and im primarily looking for information on the 3 questions written above
Try the steps below:
In browser go to: http://application-tier/Reports/Pages/Folder.aspx
Press Folder settings button in the toolbar
Press New Role Assignment button in the toolbar
Specify user name in Group or user name field, check Content Manager role and press OK.
So for the people that actually read the question the answer is.
Keeps track of agile work progress
yes and its actually easy. go to the reporting service and stop it and then tell TFS not to report under reporting
Since it was never running the answer here is No

Google Fusion - Won't Allow Me to Publish a Feature Map

Here is the link to my public fusion table: https://www.google.com/fusiontables/DataSource?docid=1dp1DTZKzXWLE4TbI2Z9q-5jetC0iVt6ee_0eZdU8#map:id=3
I'm trying to publish the feature map and embed on a website, however 'Publish' is grayed out. Since I've set everything to public, I can't figure out what's preventing me from publishing and embedding.
I suggested a workaround when you asked this question on the product forum.
I don't understand why it's happening, but there's something stuck in a strange state for this table. Can you try downloading it to a CSV file and reimporting to a new table? You'll have to redo your map styles, but publishing should work on a new version,

Add Client Log in area to Kirby

I'm pretty new to Kirby, trying to build my first site with it, and the site is for a photographer who wants clients to be able to log in where they can view and download their photos. Is that something I could do with Kirby? I saw this - http://getkirby.com/blog/frontend-authentication - but it was a while ago, and I didn't see any plugins listed on their current plugin list that seemed to fit what I'm looking for.
Have a look at http://getkirby.com/docs/solutions/authentication.
You may update your Kirby root.

UmbracoExamine ExternalIndexer Cannot index queue items, the index is currently locked

We get this error a lot on our Umbraco site, also we've noticed that when we publish content, it doesn't actually publish it, then I check the log and I see this error message.
Is this because there maybe more than one admin user logged in at one time?
Pete
Having more than one admin user logged in at the same time is not a problem at all. There's plenty of running sites with many backoffice users logged in and editing at the same time. The only case where this could give an issue is the fact that if you have two users load up the same item in the backoffice and one makes changes and saves.. and the other one then saves without reloading first, the changes from user1 will be overwritten by whatever was loaded when user2 loaded up the page.
One thing that could lock up your indexes however is having multiple sites run off the same index files (which is NOT supported) - so make sure you're not doing this. I've seen some people forgetting having an old IIS test site configured in the same folder after going in production which could bring up this issue.
Another thing that I usually do is exclude the index folders from both anti-virus scanning and the windows indexing service, as I've seen both of these take temporary file locks which sometimes interfere with umbraco's access to the index files. The indexing can be turned off by right-clicking the specific folder in explorer, selecting properties > advanced > uncheck the 'allow files to be indexed'.

Resources