search

zfcampus / zf-apigility

BSD 3-Clause "New" or "Revised" License
258 stars 52 forks source link

development mode enable throws fatal error #154

Open NickClaywell opened 8 years ago

NickClaywell commented 8 years ago

Running the latest version of Apigility (1.3.2), if I disable development mode, the server just returns 500 errors for both the admin panel and any http reqeusts to the API. When trying to re-enable development mode, php throws a fatal error and the API still won't respond.

It seems like a path was hardcoded in:

$ php public/index.php development enable 
PHP Warning:  require_once(/home/matthew/sandbox/zf-apigility-skeleton-1.3.2/module/Application/Module.php): failed to open stream: No such file or directory in [...]/vendor/zendframework/zend-loader/src/ModuleAutoloader.php on line 147
PHP Fatal error:  require_once(): Failed opening required '/home/matthew/sandbox/zf-apigility-skeleton-1.3.2/module/Application/Module.php' (include_path='.:/usr/local/share/pear') in [...]/vendor/zendframework/zend-loader/src/ModuleAutoloader.php on line 147
jerfeson commented 8 years ago

I'm in the same situation, follow exactly what was in the tutorial in https://apigility.org/documentation/modules/zf-development-mode site

UPDATE I had the same problem, this is the cache on the date folder, it is seeking a path that does not exist, just delete the folder cache date that will work /home/matthew/sandbox/zf-apigility-skeleton-1.3.2/module/Application/Module.php'

zbintiosul commented 8 years ago

Also you can rename manual development.config.php.dist to development.config.php from config folder and development mode will be enabled.

jerfeson commented 8 years ago

This disable maintenance mode, but it does not solve the problem he reported.

lucianoreis commented 8 years ago

To solve clean the files in data/cache

ghost commented 8 years ago

in config/development.config.php comment this line

//'ZF\Apigility\Welcome',

michalbundyra commented 4 years ago

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at https://github.com/laminas-api-tools/api-tools/issues/35.