all,
I am having a problem when trying to install TestLink on Windows using the tutorial
These are the steps I am following:
Download and install Bitnamin v5.6.40-1 (XAMPP) on c drive – OK,
Open XAMPP control panel, start Apache and MySQL - OK
Download TestLink 1.9.20, unzip it and copy to ‘C:\xampp\htdocs‘ - OK
Modify file ‘config.inc.php’ in the ‘C:\xampp\htdocs\testlink’ - OK
$tlCfg->log_path = 'C:\xampp\htdocs\testlink\logs';
$g_repositoryPath = 'C:\xampp\htdocs\testlink\upload_area';
Open http://localhost/Testlink - FAILS with the following error:
Fatal error: Uncaught Error: Attempt to modify property "results" on null in C:\xampp\htdocs\testlink\cfg\const.inc.php:410 Stack trace: #0 C:\xampp\htdocs\testlink\install\index.php(20): require_once() #1 {main} thrown in C:\xampp\htdocs\testlink\cfg\const.inc.php on line 410
I’ve added the following line in const.inc.php to initialize the object:
$tlCfg = new stdClass();
It seems to fix the problem. http://localhost/Testlink opens fine now.
Proceed with the TestLink installation (http://localhost/Testlink).
The pre-requisites check is OK.
The installation FAILS at Process TestLink Setup (after I enter Database Admin login/password to define MySQL access and TestLink admin login/password):
Fatal error: Uncaught Error: Attempt to assign property "glue_character" on null in C:\xampp\htdocs\testlink\config.inc.php:192 Stack trace: #0 C:\xampp\htdocs\testlink\install\installNewDB.php(37): require_once() #1 {main} thrown in C:\xampp\htdocs\testlink\config.inc.php on line 192
The problem is with this line of the code:
$tlCfg->testcase_cfg->glue_character = '-';
Any help would be appreciated.
Go to your config.ini.php and add this line:
$tlCfg->testcase_cfg = new stdClass();
$tlCfg->testcase_cfg->glue_character = '-';
If you face the same error with other variable just try to do the same thing.
Related
I'm trying to install bwapp but when I clicked link I showed me an error something like
Fatal error: Uncaught mysqli_sql exception. Unknown database 'bwapp' in C\xampp\htdocs\bWAPP_latest bWAPP install php:40 Stack trace: #0 C\xampp/htdocs/bWAPP latest bWAPPnstall php(40) mysql select db(Object(mysqli), bWAPP) #1 (main) thrown in C:\xampp\htdocs\bWAPP latest bWAPP install.php on line 40
Can anyone suggest a method to solve this?
I have WordPress running on Windows 10 with IIS.
While upgrading WordPress to 5.5 this morning I received the following error:
PHP Fatal error: Uncaught Error: Call to undefined function wp_unregister_GLOBALS() in C:\inetpub\wwwroot\wordpress\wp-settings.php:70 Stack trace: #0 C:\inetpub\wwwroot\wordpress\wp-config.php(92): require_once() #1 C:\inetpub\wwwroot\wordpress\wp-load.php(37): require_once('C:\inetpub\wwwr...') #2 C:\inetpub\wwwroot\wordpress\wp-admin\admin.php(34): require_once('C:\inetpub\wwwr...') #3 C:\inetpub\wwwroot\wordpress\wp-admin\index.php(10): require_once('C:\inetpub\wwwr...') #4 {main} thrown in C:\inetpub\wwwroot\wordpress\wp-settings.php on line 70
This was a very easy fix. Since my installation was local I just copied all the files and directories located in the WordPress 5.5 upgrade folder (in my case it was C:\inetpub\wwwroot\wordpress\wp-content\upgrade\wordpress-5.5-no-content-cIBdh3\wordpress) to the root of the site (in my case C:\inetpub\wwwroot\wordpress) overwriting the file already there.
Very simple fix. I guess the installation hit something while it was copying or timedout, who knows. I'm sure you can do the same thing by FTPing to your site if you are hosting your site remotely.
i am updating to 5.5 in my hostiing and i got this problem, the solution is You should upload all and folder file update except wp-content but it depends
This question also posted on GitHub at https://github.com/Piwigo/Piwigo/issues/1003.
Getting error # photos can not be regenerated in Batch -> Generate Multiple Batch Size Images. Image sizes not being generated on upload.
Piwigo appears to be looking in the wrong directory for uploaded image files.
From the php_errors.log file:
[13-Apr-2019 18:48:48 America/New_York] PHP Fatal error: Uncaught exception 'ImagickException' with message 'unable to open image `././upload/2019/04/13/20190413172232-f087ab9d.jpg': No such file or directory # error/blob.c/OpenBlob/2702' in ...\piwigo\admin\include\image.class.php:415
Stack trace:
#0 ...\piwigo\admin\include\image.class.php(415): Imagick->__construct('././upload/2...')
#1 ...\piwigo\admin\include\image.class.php(87): image_imagick->__construct('././upload/2...')
#2 ...\piwigo\i.php(524): pwg_image->__construct('././upload/2...')
#3 {main}
thrown in ...\piwigo\admin\include\image.class.php on line 415
Installed on Windows 10 x64 with Apache 2.4 and PHP 5.6.2.
I am very new to using Frameworks/Laravel and I haven't achieved to run the Laravel welcome website in PhpStorm yet.
Steps I've done so far:
I have created a new "Composer Project" with PhpStorm and chose Laravel as Package.
I installed the IDE helper in line with this tutorial: http://blog.jetbrains.com/phpstorm/2015/01/laravel-development-using-phpstorm/
I installed XAMPP and started the Apache server on port 8000
Changed the PhpStorm Settings -> Language & Frameworks -> PHP -> Interpreter -> Path to php.exe inside of XAMPP
I tried to watch the results in a browser by clicking "Run". A PHP fatal error appeared in the debugger which said the class TestCase couldn't be found.
After googling I added the phpunit.xml as an alternative configuration file for my Run/Debug configurations. Furthermore I read that I need to add the "tests" folder inside of my project directory as "Directory Test Scope" there.
The debugger says "All Tests passed", but I am receiving a different fatal error which I wasn't able to solve until now:
Fatal error: Call to undefined method
PHPUnit_Framework_TestResult::deprecatedFeaturesCount() in
C:\xampp\php\pear\PHPUnit\TextUI\ResultPrinter.php on line 446
Fatal error: Uncaught exception
'Illuminate\Contracts\Container\BindingResolutionException' with
message 'Target [Illuminate\Contracts\Debug\ExceptionHandler] is not
instantiable.' in C:\Users\kentor\PhpstormProjects\test
Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php:752
Stack trace:
0 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php(633):
Illuminate\Container\Container->build('Illuminate\Cont...', Array)
#1 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(697):
Illuminate\Container\Container->make('Illuminate\Cont...', Array)
#2 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Bootstrap\HandleExceptions.php(154):
Illuminate\Foundation\Application->make('Illuminate\Cont...')
#3 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Bootstrap\HandleExceptions.php(79):
in C:\Users\kentor\PhpstormProjects\test
Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php
on line 752 PHP
Fatal error: Call to undefined method
PHPUnit_Framework_TestResult::deprecatedFeaturesCount() in
C:\xampp\php\pear\PHPUnit\TextUI\ResultPrinter.php on line 446 PHP
Fatal error: Uncaught exception
'Illuminate\Contracts\Container\BindingResolutionException' with
message 'Target [Illuminate\Contracts\Debug\ExceptionHandler] is not
instantiable.' in C:\Users\kentor\PhpstormProjects\test
Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php:752
Stack trace:
#0 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php(633):
Illuminate\Container\Container->build('Illuminate\Cont...', Array)
#1 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Application.php(697):
Illuminate\Container\Container->make('Illuminate\Cont...', Array)
#2 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Bootstrap\HandleExceptions.php(154):
Illuminate\Foundation\Application->make('Illuminate\Cont...')
#3 C:\Users\kentor\PhpstormProjects\test Laravel\vendor\laravel\framework\src\Illuminate\Foundation\Bootstrap\HandleExceptions.php(79):
in C:\Users\kentor\PhpstormProjects\test
Laravel\vendor\laravel\framework\src\Illuminate\Container\Container.php
on line 752
Process finished with exit code 255
So in the end I want to see the contents of my "Public" folder.
My questions:
Why did I need to specify the "tests" folder? Is this used for verifying that PHP is compiling correctly or any similar testing stuff?
What did I miss in order to see my Laravel example page in the end?
I got this error when trying to run my php artisan migrate on my production server...
PHP Fatal error: Uncaught exception 'Exception' with message 'Bugsnag Error: Invalid API key' in /var/app/current/vendor/bugsnag/bugsnag/src/Bugsnag/Client.php:19
Stack trace:
#0 /var/app/current/vendor/bugsnag/bugsnag-laravel/src/Bugsnag/BugsnagLaravel/BugsnagLaravelServiceProvider.php(61): Bugsnag_Client->__construct(NULL)
#1 /var/app/current/vendor/laravel/framework/src/Illuminate/Container/Container.php(738): Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider->Bugsnag\BugsnagLaravel\{closure}(Object(Illuminate\Foundation\Application), Array)
#2 /var/app/current/vendor/laravel/framework/src/Illuminate/Container/Container.php(631): Illuminate\Container\Container->build(Object(Closure), Array)
#3 /var/app/current/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(674): Illuminate\Container\Container->make('bugsnag', Array)
#4 /var/app/current/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(62): Illuminate\Foundation\Application->make('bugsnag', Array)
#5 /var/app/current/vendor/bugsnag/bugsna in /var/app/current/vendor/bugsnag/bugsnag/src/Bugsnag/Client.php on line 19
PHP Fatal error: Uncaught exception 'Exception' with message 'Bugsnag Error: Invalid API key' in /var/app/current/vendor/bugsnag/bugsnag/src/Bugsnag/Client.php:19
Stack trace:
#0 /var/app/current/vendor/bugsnag/bugsnag-laravel/src/Bugsnag/BugsnagLaravel/BugsnagLaravelServiceProvider.php(61): Bugsnag_Client->__construct(NULL)
#1 /var/app/current/vendor/laravel/framework/src/Illuminate/Container/Container.php(738): Bugsnag\BugsnagLaravel\BugsnagLaravelServiceProvider->Bugsnag\BugsnagLaravel\{closure}(Object(Illuminate\Foundation\Application), Array)
#2 /var/app/current/vendor/laravel/framework/src/Illuminate/Container/Container.php(631): Illuminate\Container\Container->build(Object(Closure), Array)
#3 /var/app/current/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(674): Illuminate\Container\Container->make('bugsnag', Array)
#4 /var/app/current/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(62): Illuminate\Foundation\Application->make('bugsnag', Array)
#5 /var/app/current/vendor/bugsnag/bugsna in /var/app/current/vendor/bugsnag/bugsnag/src/Bugsnag/Client.php on line 19
I ran env on the command line and I have an env variable called BUGSNAG_API_KEY and the value of it exactly matches the key at bugsnag.com for this project.
Furthermore, I have this line in my project at ./config/bugsnag.php
'api_key' => env('BUGSNAG_API_KEY'),
Weirdly, I eventually tried the same command again (php artisan migrate) and it worked! But it's left me very unsettled as it's a production server. So I'd like to understand the problem.
Errors seem to be logging in Bugsnag as well by the way.
Try to regenerate the configuration cache with php artisan config:cache. It will use the current data from the .env file to generate a new configuration cache. This worked for me.
In case this helps anyone...
The Bugsnag Git Repo mentions this issue:
(Uncaught exception 'ReflectionException' with message 'Class bugsnag.logger does not exist'
Github user GrahamCampbell suggested that what is actually happening is that another error exists, but it's "...trying to log to bugsnag which is causing this error, which is hiding the real error". I confirmed this was my issue by doing what user russianryebread suggested, which was to manually copy the bugsnag.php config file over to the Laravel /config directory. Once I did that now my real error shows:
[Symfony\Component\Debug\Exception\FatalThrowableError] Parse error: syntax error, unexpected '{'
Now to troubleshoot this issue :)
Hope this helps!