Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Yes I downgraded back to 2.0.0 and then it worked again, then I made some tests on my test server and: 2.0.0 worked 2.0.2 and 2.0.3 ampresand modules checks out under symbolic module name instead of what was set in -d parameter 2.1.1 Nothing happens when I try to checkout module including ampresand modules, but a normal checkout from a direct path in the repository worked Oliver Koltermann wrote: > bc at passagen.se (Björn Carlsson) writes: > > I am using a lot of ampresand modules and when I upgraded from 2.0.0 to > > 2.0.3 it stopped working. My module is defined like this (simplified): > Just a small comment: Are you sure it worked in 2.0.0? I also use a > lot of ampersand modules and have problems since 2.0.0rc4. This > version introduced a new handling of those modules which is not > compatible with older releases. It improves with every new release, > but it looks like the best to do is to stick with an older version > until a more stable ampersand module handling is regained if you > depend on the ampersand modules. > bye, > OK.