Closed apex- closed 12 years ago
When commenting out the line $this->importFootprintData() in the run() method of src/backend/de/RaumZeitLabor/PartKeepr/SetupFootprintSetup.php the program continues until "Setting up the SI Prefixes..." and keeps hanging there
Something is going wrong here...since i'm not a PHP programmer I unfortunately don't know how to debug this right now.
During footprint setup, the installer loads data from remote servers. I know this is unfortunate and this might take quite a while - on my 3Mbit DSL line, it takes about 60-90 seconds.
You can try to increase the PHP value "max_execution_time" in your php.ini file to a bigger value, like 120 seconds or more. Additionally, if you are running chrome or firefox (with the firebug extension), you can open the JavaScript console and see if there are any errors coming back from the server.
If nothing helps, I can offer you personal assistance using IRC (I'll be there from around 8AM CET).
I'm leaving this bug open as a reminder to re-work the installer routine for downloading the footprint PDFs, as well as for adding a check regarding "max_execution_time".
I have solved my installation problem. The Apache error.log gave me the right hint:
[Mon Dec 26 18:32:11 2011] [error] [client 127.0.0.1] File does not exist: /var/www/partkeepr/setup/css/PartKeepr.css, referer: http://localhost/partkeepr/setup/ [Mon Dec 26 18:32:32 2011] [error] [client 127.0.0.1] PHP Fatal error: Doctrine\Common\ClassLoader::loadClass(): Failed opening required 'Doctrine/Symfony/Component/Yaml/Yaml.php' (include_path='.:/usr/share/php:/usr/share/pear') in /usr/share/php/Doctrine/Common/ClassLoader.php on line 0, referer: http://localhost/partkeepr/setup/
I fixed it by installing the following package pear install doctrine/DoctrineSymfonyYaml
Is it possible to add a check for this in the installer?
Can you please also check for the error about the missing/wrong link to the CSS file?
Thanks for your replies and this great project. I think it really fills a gap!
Both issues are fixed now.
During setup the installer locks-up during "Setting up the default footprints...". This issue occurs with both, MySQL and PostgreSQL databases.
Here is some more information which might help to track down the problem: