I noticed there are two ways to see this problem,
one is wait a time (1 hour more or less) and two with the option "Republish entire site".
I tried deleting content node, doc type and template; and recreating again.
Also there is no error displayed with ?umbDebugShowTrace=true, the page has no parent it's directly under Content.
Any help will be great.
Thanks.
Umbraco version is 4.11.5
The most obvious reason why a page would be blank would be if you have not set a valid template - or have subsequently deleted the template. Check the properties tab towards the top to see if there is a template for the node.
The second most obvious would be if you were adding a doctype that wasn't an allowed child type of the parent - you could do this by adding it as an allowable child, and then later removing this right from the second tab of the doctype setup.
Not much to go on really.
Related
In the page below, it specifies that you can register your device in the left hand column of the page, under advanced options:
https://developers.google.com/assistant/sdk/guides/library/python/embed/register-device
This is no longer the case, the option is not there. Instead there is a backend option.
Is there any kind of web page to do this action at all?
Would prefer a graphical option to a command line one.
Ok. sorted this out.
My thanks to those who looked over this question. Basically I deleted the current projects and started again. the device model registration is right down (scroll right down to) the bottom of the page on the first screen after you have first created the project. Apparently you need to not skip this step, or navigate away from this page before you do the device creation.
after that everything went well and is up and running. Thanks again
We use Visual Studio Online.
We've been experiencing this issue over the past two days, when adding a new Product Backlog Item into the backlog view.
When we add an item from the quick add form in the backlog, TFS displays error TF400486. The item is saved and given an ID number, however, the spinner displays continuously. If further items are added from this screen, they will not save. A screen shot of the error is below.
The full error text is:
TF400486: Unable to complete the operation because you or another user has modified, removed, or re-parented items, or you are trying to reorder an item outside of its immediate parent.
Adding an item via the Work>Queries>New>Product Backlog Item does work correctly.
Any ideas what might be going wrong in the backlog view?
We had this same error and found a workaround. We removed the link to a parent Workitem and then could do Drag & Drop again. This was true even after we relinked the user story with their former parent elements again.
I hope this helps.
We never found the root of this error.
It sounds like a caching issue for that page. Try using private mode (InPrivate) or clearing the cache for that browser.
Make sure you don't have another iteration path with the same name. If so, it prevents items from being reordered.
In my case i added sufix (2022) on my the old iteration path T01-JAN-01
I am using jQuery UI sortable to update the order of an array stored in a container document. When the sort fires the "stop" method, it rebuilds the array and orders it based on the new DOM layout. It all works fine and the updated document reflects the proper order. HOWEVER, the dom reloads and the order is back to what it was.
When I physically refresh the page it actually shows the proper order. It's just that on-the-fly changing of the array won't just re-render itself properly.
Interestingly enough, this problem has only cropped up in 0.9.4, so it may be a bug with meteor, just not sure if there was a change that would affect what I'm trying to accomplish.
I'd provide code examples if needed, but since the code itself seems to be working properly and the each not updating to reflect the order, i'm not sure it'll help at all.
Thanks!
UPDATE
I've put together a standalone demo of the problem, listed out in my comment below:
Ok, here's a crazy example of the issue:
demo: app-9ryym2m2.meteorpad.com
source: meteorpad.com/pad/uQ42DRH95JcHtKnb9
Try doing some sorting of items to see part1 of the issue. Next, after sorting, try hitting the togglers a few times, especially within the list of items you sorted. That's part2 of the issue. Now, if you refresh the page, everything gets caught up. Wat.
Double Update
Thanks to aldeed over at Github, I've got a solution: https://github.com/meteor/meteor/issues/2944
By changing my sub-document reference key from 'id' to '_id', Blaze seems to pick up on the changes to sorting no problem!
I confess that I haven't dug into your code, but the way it is updating indicates that you are picking up the previous state rather than the updated state. Wherever you drag, the final state reflects the last place you dragged to (even though it was probably in the wrong place when you started). Perhaps an order-of-execution/async bug?
Have you seen the drag and drop demo that was put together for blaze by Avital Oliver (Meteor core dev) when the blaze rendering engine came out? You can watch a video and check out the repo. If you try the demo and it fails on the current version of Meteor, you can submit an issue there and get some support from the pros :)
I receive the following error:
OH-TFS-Connector-0051: Operation failed getCollectionMetaData. Server Error : TF201063: Adding a Parent link to work item 1737 would result in a circular relationship. To create this link, evaluate the existing links, and remove one of the other links in the cycle.
I have completely flattened out the Work Items in the source project. When retrying the migration the timestamp is modified on the pending errors however the issues are not resolved. These Work Items now have no parents or children in the source project. So I'm wondering if the retry list is no longer valid but there doesn't appear to be a away to have it update?
I can run the whole migration again, however it takes 5-7 hours to just do the work items so it would be great if there is a quick fix.
Was able to solve this problem by doing the following;
Removing all links in the source for the work items with issues (recording this so it can be put back afterwards)
Ran migration again
Navigate to the task in question in the target. Notice that a new parent and child links were present (even though there should be none according to the source).
Opened the parent link and removed the child link then saved.
Then removed the child link in the parent.
Marked all items for Retry and restarted the migration.
Last task, is now to put the links back in the target as they were originally in the source.
Update It appears I have to rebuild/redeploy the app to see the changes. Anyone know why I have to do this? It's a static .xhtml page. Coming back to update, looks like I just have to stop/restart the server, not a rebuild. I was dumb and didn't try that first, mostly because I have to rebuild/deploy often anyways.
I'm working on a JSF 2 app that uses f:subviews. I'm on one subview where my changes aren't reflected in the UI when I refresh the browser. I've worked on other subviews where I don't have this problem.
I have a batch script which copies my .xhtml files into my installed apps folder. The batch script reports the file is copied over. It's business as usual... If I drill down into this particular installed app, I see my change in the file. Again, seems like business as usual. The change is not reflected in the UI when I refresh, however.
These are simple text changes I'm making, but not seeing.
The problematic subview doesn't appear to be anything special, it's just a p:datatable that's included via a ui:include with a couple of parameters for the data and to give it a unique id. If I replace the p:datatable with just simple text, the "old" table still shows up in the UI when I refresh. I just can't get any changes in this subview to be reflected in the UI.
Console doesn't throw any errors.
I'm using WebSphere 7.0.
Never encountered this problem before. It isn't a browser caching issue as I can edit other subviews and see those changes when I refresh the page.
Anyone have any ideas?