I'm afraid that using this forum is turning out to be a complete waste of time. I am completely stalled with a problem that was added to this forum some time back.To date no response from anyone. I notice that I am not the only one with the problem and they seem to be having similar experiences getting support. For the last time before I switch to another CMS product can anyone help with a problem which manifests itself as either "error in sub-tree" or in not expanding a tree that has multiple "childern" . This occurs with IE7 , Firefox 3.08 (Windows and Linux) and Chrome. It basically means that we cannot continue with the site we are trying to create.
Do you really think thats the way to get people to help you?
Did it occur to you that mayb nobody knows the answer? Personally I have never come accross this issue. Have you checked open.silverstripe.com to see if a ticket has been posted or tried posting one yourself?
SS is open source, which means it's free, which means you don't automatically have the right to instant support (unless you pay). Everyone on here is volenteering their help for free. It's called a community and being the relatively small community that we are, there are bound to be questions that slip through the net, but on the whole a lot of people do get help here.
If you feel like you wan't to stop using SS then that is up to you, there is no point threatening us with leaving, we're all here because we love using SS to build sites and we wan't to try and help people where we can. An attitude like yours isn't going to win you any help and I can't say I'll be losing any sleep if you decide to leave.
I realise that this product is Open Source but from I can see it is also commercial in that I can get help "if I pay". I have no problem paying so please do not take high minded attitude of being a "community" of volunteers. If there is a bug in the software and if it can be fixed by paying for the fix surely then the concept of Open Source goes out the window. I have recommended SS to many people and also praised the forum process for the timely help you get but when you spend over 2 weeks chasing your tail you get a bit frustrated and a bit embarressed for having recommended the product.
As to raising a "bug ticket" , this has already been done by another contributor and I have added to it. I am not the only one experiencing this particular problem.
I apologise for any upset I may have caused you , it was not intentional.
If there is a bug in the software and if it can be fixed by paying for the fix surely then the concept of Open Source goes out the window.
Actually, there is nothing about Open Source that says you are not allowed to pay for things! What it means is that you are welcome to use, modify and redistribute the code for free. Anyone is able to provide paid services to support and enhance the product but if you opt for the free then you have to accept that you are not likely to get a paid service response.
In an open source project you have to consider the motivations of the people who are contributing. Mostly open source contributors are motivated by making their product as good as possible but they still have limits on their resources. If you want something prioritized then you have to give some them motivation.
If you are using SS to build something for a paying client and you have some kind of problem then it is only fair that if you want a fix urgently you pay for it.
The other option, of course, is to fix the problem yourself; this is something in which open source projects excel. In closed source projects you are completely left out to dry until the next release comes which hopefully fixes your problem.
We will probably review tickets (or sminnee and ajoneil will) before 2.3.2 stable is released so its likely they will investigate your ticket while they are going through them then.
To help with the ticket make sure you are running the latest stable (2.3.1) on a clean installation and list any other information about your environment to the friendly folks on open.silverstripe.com, screenshots, browser versions anything that will make your issue easier to replicate. As if we can't replicate it on our machines it will most likely be marked as invalid or not fixed at all :(