This package has broken all XSLT functionality on my site...
6.1.3
Azure hosting
upgraded from 1.4.5 or whatever
Why in the world is there NOT a complete list of ALL changes that this package makes? Can somebody please provide this? Why is it not listed in the readme? Why are most things Umbraco so lazy and poorly documented? Most of us are not .NET programmers and have no ability or desire to load this crap into Visual Studio to see what is going on.
I have installed this package on (4) 6.1 sites. It broke every one of them.
I restored a backup of my site, both files and DB and still had the problem. At that point, the only possible solution was to delete the ENTIRE app_data folder... and of course, that fixed the problem.
While the fix works, it is rather unreasonable in context to simply installing a package. Umbraco bug or 301tracker bug...
Just as back-reference, this was the content of the original first post:
This BROKE MY SITE
This piece of crap has broken all XSLT
functionality...Why in the world is there NOT a complete list of ALL
changes that this package makes? Can somebody please provide this?
Seriously dude, what is wrong with you?! I'd suggest you should look for some help, and I'm not talking about technical help, but more like a shrink...
I was adult enough to edit my post shortly after submitting it. Instead of addressing my very valid concern or responding to the numerous unanswered threads, you instead opted to take the time to repost deleted content in favor of a personal attack.
I find it bothersome that there is in effect no documentation for this project and would hope that you would publish and keep up-to-date the changes that this project makes to Umbraco. In fact it should be required by any project author. To be fair, it is not your fault that Umbraco accepts projects that are not properly documented. So I am a bit frustrated with your project, but extremely frustrated with the entire state of the Umbraco project and its lack of strict convention for anything, including documentation.
IMO this project is one of the better documented projects. Everything you should know is documented, but I can't help it if you mess things up yourself and go blame other people for your faults.
You're in no way an adult. This project and almost all other projects for umbraco are free. FREE...
This means I've put alot of effort into something for people like you without asking anything in return.
If you just want to be a huge ass (because this is not the first time you're ranting like this), find some other place to do so.
Talking about being an adult:
"load this crap into Visual Studio"
Right...
Ps. I was on holiday for 2 weeks, that's why some posts aren't answered :-)
If it is so well documented, where are those documents? While it may be your opinion that your own project and umbraco as a whole are well documented, I do not agree, can provide countless examples, and have openly stated as much. In context to my frustration here and in regard to THIS package, what changes does the installer make to the umbraco instance and DB during the installation process? Dlls, configs, sql, cache, etc? This is basic information that is extremely helpful to those who encounter issues, as I did and should be clearly published. It is nowhere to be found.
The "visual studio" comment was in context to the advise of may to look at the source code, employ deubgging tools, etc. Many (most?) Umbraco users have no desire to work in visual studio and/or with actual code and instead are interested using the CMS to build websites.
You infer that I am the one who messed up. All I did was install your package, and it broke Umbraco. I was able to reproduce the issue on numerous 6.x installations by simply installing your package. Blaming you? No! I am just telling you that your package appears to break existing installations with predictable and repeatable results. As such, and because there is no document outling the exact changes made during installation, resolving the issue was frustrating and the fix was not obvious.
Lastly, the "cost" of the package or the platform is of absolutely no relevance to my issue here or with the project in general.
So in conclusion. You may want to look at your package and see what can be done to prevent the issue I have reported. It would also be very helpful if you built a document describing all fo the changes that the 301 installer makes to Umbraco. Likewise and beyond the scope of this package forum: It would be helpful if the core team refused to admit a package into the repository unless a list of criteria is met; one of the criteria being documentation of ALL changes made to the umbraco instance by the package installer and done so with standardized convention and format.
If you would've asked this in a normal polite way, I would have helped you. But the way you're behaving makes me sick.
This is the last thing I wanted to say to you and I hope you will stop for a minute and think for yourself why you're acting out like this.
I was extremely frustrated after intalling this package and bringing a live site and at least 4 development sites down. I was even more frustrated after looking for any documentation regarding changes this package makes, and yet more frustrated after trying (with no luck) to restore those sites from backup. I dropped into the forum here and found numerous unanswered threads and reached my limit of frustration.
I may have posted in frustration, but I came back and edited my post to be less inflamatory.
You ignored that and made public what was deleted (by me in favor of a more level headed post), for the sole purpose of attacking me.
You attempted to portray me as the fool for messing things up and breaking my own site, when in fact the installation of your package breaks 6.x sites until the cache/temp folders are cleared. The results are predictable and repeatable. (why is this not documented?)
You attempted to attack me again by linking to other posts in the umbraco forum without providing context
You have taken comments here out of context in order to attack me
You have not once addressed the valid issues that have been raised
Who is really acting out here? Call me any name you wish Sir, but your behavior here is far from mature, as every one of your posts in this thread has been combative and a further attack.
A simple question: Would your time not be better spent providing a bug fixes, responses to the multiple other unanswered threads, and proper documentation to the community and users of your package (a nice package btw)?
Hey guys remember it's the friendliest CMS community ;) so i don't think it has any value accusing each other
But remember it's always a good practice to install a new package on a dev site before bringing a live site down (with something you didn't test) and then being frustrated, if you test it locally and polity ask for some help I'm pretty sure things would have been sorted pretty fast..
You know what William? Let's fix this by starting all over again...
If you'd like, you can create a new topic and describe the issues you've stumbled upon (the original issue and the problems you're having with the current documentation) in a normal friendly way.
And if you do, we can ask Tim, or somebody else with administrator rights, to completely remove this obsolete topic.
This BROKE MY SITE
This package has broken all XSLT functionality on my site...
6.1.3
Azure hosting
upgraded from 1.4.5 or whatever
Why in the world is there NOT a complete list of ALL changes that this package makes? Can somebody please provide this? Why is it not listed in the readme? Why are most things Umbraco so lazy and poorly documented? Most of us are not .NET programmers and have no ability or desire to load this crap into Visual Studio to see what is going on.
I have installed this package on (4) 6.1 sites. It broke every one of them.
I restored a backup of my site, both files and DB and still had the problem. At that point, the only possible solution was to delete the ENTIRE app_data folder... and of course, that fixed the problem.
While the fix works, it is rather unreasonable in context to simply installing a package. Umbraco bug or 301tracker bug...
Just as back-reference, this was the content of the original first post:
Seriously dude, what is wrong with you?! I'd suggest you should look for some help, and I'm not talking about technical help, but more like a shrink...
Bye.
kipusoep
I was adult enough to edit my post shortly after submitting it. Instead of addressing my very valid concern or responding to the numerous unanswered threads, you instead opted to take the time to repost deleted content in favor of a personal attack.
I find it bothersome that there is in effect no documentation for this project and would hope that you would publish and keep up-to-date the changes that this project makes to Umbraco. In fact it should be required by any project author. To be fair, it is not your fault that Umbraco accepts projects that are not properly documented. So I am a bit frustrated with your project, but extremely frustrated with the entire state of the Umbraco project and its lack of strict convention for anything, including documentation.
IMO this project is one of the better documented projects. Everything you should know is documented, but I can't help it if you mess things up yourself and go blame other people for your faults.
You're in no way an adult. This project and almost all other projects for umbraco are free. FREE...
This means I've put alot of effort into something for people like you without asking anything in return.
If you just want to be a huge ass (because this is not the first time you're ranting like this), find some other place to do so.
Talking about being an adult:
Right...
Ps. I was on holiday for 2 weeks, that's why some posts aren't answered :-)
If it is so well documented, where are those documents? While it may be your opinion that your own project and umbraco as a whole are well documented, I do not agree, can provide countless examples, and have openly stated as much. In context to my frustration here and in regard to THIS package, what changes does the installer make to the umbraco instance and DB during the installation process? Dlls, configs, sql, cache, etc? This is basic information that is extremely helpful to those who encounter issues, as I did and should be clearly published. It is nowhere to be found.
The "visual studio" comment was in context to the advise of may to look at the source code, employ deubgging tools, etc. Many (most?) Umbraco users have no desire to work in visual studio and/or with actual code and instead are interested using the CMS to build websites.
You infer that I am the one who messed up. All I did was install your package, and it broke Umbraco. I was able to reproduce the issue on numerous 6.x installations by simply installing your package. Blaming you? No! I am just telling you that your package appears to break existing installations with predictable and repeatable results. As such, and because there is no document outling the exact changes made during installation, resolving the issue was frustrating and the fix was not obvious.
Lastly, the "cost" of the package or the platform is of absolutely no relevance to my issue here or with the project in general.
So in conclusion. You may want to look at your package and see what can be done to prevent the issue I have reported. It would also be very helpful if you built a document describing all fo the changes that the 301 installer makes to Umbraco. Likewise and beyond the scope of this package forum: It would be helpful if the core team refused to admit a package into the repository unless a list of criteria is met; one of the criteria being documentation of ALL changes made to the umbraco instance by the package installer and done so with standardized convention and format.
If you would've asked this in a normal polite way, I would have helped you. But the way you're behaving makes me sick.
This is the last thing I wanted to say to you and I hope you will stop for a minute and think for yourself why you're acting out like this.
I was extremely frustrated after intalling this package and bringing a live site and at least 4 development sites down. I was even more frustrated after looking for any documentation regarding changes this package makes, and yet more frustrated after trying (with no luck) to restore those sites from backup. I dropped into the forum here and found numerous unanswered threads and reached my limit of frustration.
I may have posted in frustration, but I came back and edited my post to be less inflamatory.
Who is really acting out here? Call me any name you wish Sir, but your behavior here is far from mature, as every one of your posts in this thread has been combative and a further attack.
A simple question: Would your time not be better spent providing a bug fixes, responses to the multiple other unanswered threads, and proper documentation to the community and users of your package (a nice package btw)?
Hey guys remember it's the friendliest CMS community ;) so i don't think it has any value accusing each other
But remember it's always a good practice to install a new package on a dev site before bringing a live site down (with something you didn't test) and then being frustrated, if you test it locally and polity ask for some help I'm pretty sure things would have been sorted pretty fast..
You know what William? Let's fix this by starting all over again...
If you'd like, you can create a new topic and describe the issues you've stumbled upon (the original issue and the problems you're having with the current documentation) in a normal friendly way.
And if you do, we can ask Tim, or somebody else with administrator rights, to completely remove this obsolete topic.
Sounds good?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.