I just saw this and I am very sorry that you haven't heard from anyone here. I must have missed a notification, if any was sent at all.
Did you manage to get it working, or did you give up?
It's a very simple XSLT macro so the only things that can really cause this would be using the old XML Schema (Umbraco 4.1 and earlier) or simply not having any published nodes (i.e., a node has to be published before the Latest Edits Dashboard can see it).
If you're using 4.7.1 there's a good chance you upgraded from a version using the old schema? — It's not a huge task to support it, just hadn't had any requests for it yet...
We really need your program to work for us. We're having intermittent site crashes and we'd like to easily see who was changing documents. We're on 4.71 as stated. We had to update to the schema that is compliant w/4.71. As to schemas post 4.71, we're obviously not compliant. I am not sure if you are stating that your extension only works w/schemas such as in 4.9 for 4.10. Could you clarify and/or point us in the direction of getting your invaluable extension to work w/our version short of having to upgrade.
The package currently only works with the new Schema introduced in Umbraco 4.5.
It's not a huge undertaking to make it work with the old Schema, and I'll see if I can
get that done in a couple of days, but you say that you'd like to see who made certain
changes, right? The package doesn't currently do this but I've added it myself to more than
one instance of it already, so it's planned for inclusion.
One thing to note though: This package works by using a simple XSLT macro,
so it's only possible to see published content - I don't know if that defeats the purpose
you're after (causes to crashes etc.) and if you know a specific page was edited,
you could try the Audit trail action from the rightclick menu on it's node in the content tree?
Thanks so much. As far as who makes the changes, we can easily figure that out. If you add that feature, it would of course be great. As far as published vs unpublished, that is not critical either. Believe it or not, I never thought to use the Audit Trail for anything. That's a good heads up. Anyway, if you get the package to work w/the old schema, I will look for a subsequent post form you.
Not working - any ideas
We've installed this on 4.71 - its not working. We haven't configured the media but the content nodes are not being returned. Any ideas?
Hi Richard,
I just saw this and I am very sorry that you haven't heard from anyone here. I must have missed a notification, if any was sent at all.
Did you manage to get it working, or did you give up?
It's a very simple XSLT macro so the only things that can really cause this would be using the old XML Schema (Umbraco 4.1 and earlier) or simply not having any published nodes (i.e., a node has to be published before the Latest Edits Dashboard can see it).
If you're using 4.7.1 there's a good chance you upgraded from a version using the old schema? — It's not a huge task to support it, just hadn't had any requests for it yet...
/Chriztian
Thanks. I will pass this along.
@Chriztian,
We really need your program to work for us. We're having intermittent site crashes and we'd like to easily see who was changing documents. We're on 4.71 as stated. We had to update to the schema that is compliant w/4.71. As to schemas post 4.71, we're obviously not compliant. I am not sure if you are stating that your extension only works w/schemas such as in 4.9 for 4.10. Could you clarify and/or point us in the direction of getting your invaluable extension to work w/our version short of having to upgrade.
Thanks. Richard
Hi Richard,
The package currently only works with the new Schema introduced in Umbraco 4.5.
It's not a huge undertaking to make it work with the old Schema, and I'll see if I can get that done in a couple of days, but you say that you'd like to see who made certain changes, right? The package doesn't currently do this but I've added it myself to more than one instance of it already, so it's planned for inclusion.
One thing to note though: This package works by using a simple XSLT macro, so it's only possible to see published content - I don't know if that defeats the purpose you're after (causes to crashes etc.) and if you know a specific page was edited, you could try the Audit trail action from the rightclick menu on it's node in the content tree?
/Chriztian
Chriztian,
Thanks so much. As far as who makes the changes, we can easily figure that out. If you add that feature, it would of course be great. As far as published vs unpublished, that is not critical either. Believe it or not, I never thought to use the Audit Trail for anything. That's a good heads up. Anyway, if you get the package to work w/the old schema, I will look for a subsequent post form you.
Thanks again.
Hi Richard,
If you download the XSLT file here: https://github.com/greystate/LatestEditsDashboard/blob/master/dist/LatestEdits.xslt and just overwrite the existing (please backup the old one first), you should be able to have a working macro in either of the XML schemas.
Let me know how it works - I'll be adding the "whodunnit" info next, so stay tuned.
/Chriztian
It works great for published content pages, but per my developer not for media uploads. Any idea?
is working on a reply...