Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sympony Location Errors #309

Closed
Avotronics opened this issue May 6, 2013 · 5 comments
Closed

Sympony Location Errors #309

Avotronics opened this issue May 6, 2013 · 5 comments

Comments

@Avotronics
Copy link

Strange one this.
I'm not sure where the Sympony directory is supposed to be, so I put it in the Doctrine folder.
When I ran the install of partkeepr it complains that it cannot find Sympony, so I moved it up one directory so that it is in the same folder as Doctrine and Twig.

Now Partkeepr setup continues and gets to installing footprints, which is where it hangs indefinitely. When I looked at the PHP error logs, it said that it could not find Yaml, which is what caused the hang on footprints, even though partkeepr passed all other checks.

So I tried moving the Yaml directory back into Doctrine directory, it didn't work.Only way to make setup complete was to copy the Sympony directory into the Doctrine directory.

So in order for Doctrine setup to complete, I had to have Sympony directory in two places; One inside Doctrine directory and one on same level as Doctrine directory.

Is this a bug or are my directories in the wrong place somehow?
It is reproducible every time for me, I've tried it on wamp, IIS and Zend server and it always happens.

@Drachenkaetzchen
Copy link
Member

Your best bet is to install symfony and doctrine using PEAR, and not downloading/installing directories manually.

Which version of PartKeepr are you using?

@Avotronics
Copy link
Author

Version 0.1.9.
It seems odd because everything works fine once installed.

@Avotronics
Copy link
Author

Okay this still happens with pear install too.
I've managed to get get Partkeepr installed on my Linux web hosting, I used pear install but this time when it failed I knew how to correct it, kind of.

Symfony directory was inside doctrine directory. Setup went smoothly until it required Yaml, then failed and said it couldn't find it. I copied the symfony directory to sit on the same level as doctrine and the installed completed without further error.

@Avotronics
Copy link
Author

Additional info:

Setting up the database schema...OK
Setting up the admin user...OK
Setting up the part units...OK
Setting up the default footprints...Error

Invalid Response from server:
Warning: Uncaught exception 'ErrorException' with message 'require(Symfony/Component/Yaml/Yaml.php) [function.require]: failed to open stream: No such file or directory' in /removed/for/security/Doctrine/Common/ClassLoader.php:164 Stack trace: #0 /removed/for/security/Doctrine/Common/ClassLoader.php(164): __lambda_func(2, 'require(Symfony...', '/removed/for/...', 164, Array) #1 /removed/for/security/Doctrine/Common/ClassLoader.php(164): Doctrine\Common\ClassLoader::loadClass() #2 [internal function]: Doctrine\Common\ClassLoader->loadClass('Symfony\Compone...') #3 /removed/for/public_html/pk/src/backend/PartKeepr/Setup/Setup.php(124): spl_autoload_call('Symfony\Compone...') #4 /removed/for/public_html/pk/src/backend/PartKeepr/Setup/FootprintSetup.php(98): PartKeepr\Setup\Setup::loadYAML('../setup-data/f...') #5 /removed/for/public_html/pk/src/backend/PartKeepr/Setup/FootprintSetup.php(32): PartKeepr\Setup\FootprintSetup->importFootprintData() #6 /removed/for/public_html/pk/src/backend/Pa in /removed/for/security/Doctrine/Common/ClassLoader.php on line 164

Fatal error: Doctrine\Common\ClassLoader::loadClass() [function.require]: Failed opening required 'Symfony/Component/Yaml/Yaml.php' (include_path='.:/path/to/php:/removed/for/security') in /removed/for/security/Doctrine/Common/ClassLoader.php on line 164

@Drachenkaetzchen
Copy link
Member

This will be fixed as soon as #323 is done, so technically this is a duplicate of the other bug. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants