Trying to access Symphony after install with non-core extensions results in error
A bug in 2.2, submitted by bauhouse on 05 April 2011
Announcement
Symphony's issue tracker has been moved to Github.
Issues are displayed here for reference only and cannot be created or edited.
Browse
Closed#606: Trying to access Symphony after install with non-core extensions results in error
-
-
- bauhouse
- Comment #1
- 05 Apr 11, 4:26 am
-
-
- bauhouse
- Comment #2
- 05 Apr 11, 4:38 am
Nope. I'm wrong again :P
This only happens with specific extensions: Members and Schema Migration.
Even wronger :P -- the permissions weren't set correctly on the directories and files.
Feel free to close this issue.
This issue is closed.
I've never noticed this before, but it seems if you have extensions other than the core extensions in the extensions directory when doing a clean install, Symphony will return the following error until these extensions are removed from the extension directory:
Could not find extension at location /Users/stephen/Sites/sym/members/extensions/members/extension.driver.php /Users/stephen/Sites/sym/members/symphony/lib/toolkit/class.extensionmanager.php line 624 619 if(!isset(self::$_pool[$name])){ 620 $classname = $this->__getClassName($name); 621 $path = $this->__getDriverPath($name); 622 623 if(!is_file($path)){ 624 throw new Exception( 625 __('Could not find extension at location %s', array($path)) 626 ); 627 } 628