|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Is this an issue related to my computer, my staging server, or Umbraco?
When i click save i get a javascript alert saying: "FAILURE[object Object]"
This occurs even if I reboot my computer (leading me to believe that the issue is not related to my browser), and it still occurs after I've done an IIS Reset (leading me to believe that it's not related to Umbraco).
Even if I have an empty xslt file, clicking save throws an error.
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Stephan Kvart wrote:
Is this an issue related to my computer, my staging server, or Umbraco?
When i click save i get a javascript alert saying: "FAILURE[object Object]"
This occurs even if I reboot my computer (leading me to believe that the issue is not related to my browser), and it still occurs after I've done an IIS Reset (leading me to believe that it's not related to Umbraco).
Even if I have an empty xslt file, clicking save throws an error.
I'm dizzy... What I wanted to say was that I believe it's related to Umbraco, and not my stuff. The site is running on Win 2003, with SQL 2005 and Umbraco 3.0.2. Steph
|
|
Rank: Enthusiast
Joined: 4/19/2007
Posts: 14
|
I am seeing the same thing when saving XSLT in umbraco version 3.02. Any ideas?
|
|
Rank: Newbie
Joined: 7/12/2007
Posts: 7
|
I had a similar problem before. Check that you don't have two templates/documenttypes with the same name.
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Checked, and there wasn't any...
|
|
Rank: Fanatic
Joined: 7/20/2006
Posts: 449
Location: NL
|
Did you copy the XSLT-files manually to the XSLT-folder?
If so, delete them (not in umbraco, but from the file-system). Make sure you have a backup of the files before you delete them.
After that, create new XSLT-files in umbraco.
I had the same experience and found out that when you manually copy the xslt-files, the permissions of the file might not be set correct.
Hope this helps,
PeterD
Working on an events-calendar with recursion. Post requests on my blog!
|
|
Rank: Devotee
Joined: 7/22/2006
Posts: 64
Location: Heraklion Crete
|
Check if you use, umbacoRedirect as property alias to your start node. I had problem with my start node and xslt saving was broken.
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
I have this, but it's a requirement for my site. How can this possibly affect the XSLT editor? And if it does, I'd say it's a bug. (And yes, I've reported it @ codeplex) :)
Thanks though!
|
|
Rank: Enthusiast
Joined: 6/22/2007
Posts: 29
|
Its a file ownership permissions problem. Go into your XSLT folder - select all the .xslt files. Right click - goto the Security tab - in the Groups or User Names your should have Network Service - if you don't click add and type it into the box - check the name then hit OK. - the with Netwrok Service highlighted clcik the Full Control check box in the permissions box below. Click OK and that should do it. Remove all the garbage that was created (tmp xslt files) when it couldn't overwrite them.
Hope this works for you. It did for me :)
Rob
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Tried it, didn't work. You did get my hopes up though :)
|
|
Rank: Enthusiast
Joined: 8/23/2007
Posts: 12
|
I was also experiencing this error, but managed to get past it by doing the following...
1. Load your xslt that causing problems in to the editor
2. Delete the associated file in the xslt folder
3. Press save on the editor
I can only guess that this means the issue is related to a file locking or permissions problem. Anyway, it worked for me.
Cheers,
Chris
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Tried this too, didn't work out either.
|
|
Rank: Enthusiast
Joined: 8/23/2007
Posts: 12
|
Have you also cleaned out all the temp xslt files from the directory?
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
Cleaned out everything. Still throws the javascript alert. This is weird.
|
|
Rank: Enthusiast
Joined: 6/22/2007
Posts: 16
|
I had the same problem. Copy the code, then delete the xslt in the umbraco tree and in your xslt/folder. Then create a new xslt with the same name and copy your code in it. This should work. Did in my installation.
I think there is a problem with the permissions, when copying files physically from one folder to the other.
Martin
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 148
Location: aalleren, Denmark
|
The Alert should in *theory* never be shown, it would only happen if the request to the webservice saving the file did something unexpected. Just did some debugging on it, and yes it does seem that the Failure Alert is caused by the umbracoRedirect property on a top node. Now we just need to figure out why it does that... Anyway, on my test installation I got passed the alert by turning off debugging in the editor.. this *should* fix the problem for now.
Umbracian Personal blog: Objects.dk
|
|
Rank: Devotee
Joined: 11/9/2006
Posts: 47
Location: Stockholm
|
In my book, this is definetly a bug :) Another way around it, in my case, is to write my XSLT by hand, and just paste the files. This is so far only in my dev. environment, so it's not a big issue, I doubt that there's gonna be much XSLT development in the production environment anyway.
But thanks for putting so much effort into solving my problem.
/S
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 148
Location: aalleren, Denmark
|
Yes it's absolutely a bug :D will get a fix for it uploaded to the source (as soon as I get my codeplex access setup again...)
Umbracian Personal blog: Objects.dk
|
|
Rank: Newbie
Joined: 11/17/2007
Posts: 4
|
Hi
Was this resolved?
I have added umbracoRedirect on my dummy root node in the contents
and now this bug appear for me.
I have removed umbracoRedirect from the document template but the bug
is still presented.
Any suggestions?
TIA
|
|
Rank: Enthusiast
Joined: 2/14/2007
Posts: 12
|
* Remove read-only permission
* Add security permissions
|
|
|
Guest |