[FLOW3-general] Problem with activating packages (alpha7, Windows) [solved]

[Jochen Froehlich]

Hi Karsten,

yes, the environment variables are set correct.

I renamed the PackageStates.yaml file and I was able to run the Blog 
application in the browser without getting a "not active" error. (I 
didn't activate it explicitely.)
Listing the available packages on the command line worked either.

Thanks for your help! :)

Jochen



Am 21.01.2010 11:30, schrieb Karsten Dambekalns:
> Hi.
>
> On 21.01.10 11:07, Jochen Froehlich wrote:
>> I tried various CLI commands like ...
>> php Packages\Framework\FLOW3\Scripts\FLOW3.php FLOW3 Package Manager
>> activate Blog
>> ... and ...
>> php Packages\Framework\FLOW3\Scripts\FLOW3.php FLOW3 Package
>> PackageManager activate Blog
>> ... but nothing worked.
>
> The needed environment variables are set and correct?
>
>> The error I always get is:
>> "404 Not Found.
>> No controller could be resolved which would match your request."
>
> Does listing the available packages work?
>
>> The FLOW3 manual (section 4.4) states that "The current behavior is that
>> all directories which are found below the Packages folder are assumed to
>> be packages and are active by default. Just make sure that you created a
>> Package.xml file in the Meta  directory of your package."
>
> Well, that is outdated, sorry! Now packages can be activated and
> deactivated. One way would be to remove PackageStates.yaml and it should
> be regenerated with all packages active.
>
> Or you use the command you tried to activate a package.
>
> Regards,
> Karsten
>
> PS: I updated the manual in SVN and will push it to the FLOW3 website soon.

-- 
Jochen Froehlich
TYPO3 Programmierung in Stuttgart
http://www.jochen-froehlich.de