How to fix "photos can not be regenerated" bug in Piwigo? - imagick

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.

Related

TestLink 1.9.20 installation problem with $tlCfg->testcase_cfg->glue_character = '-';

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.

Fatal error: Uncaught Error: Call to undefined function wp_unregister_GLOBALS() when upgrading to 5.5

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

Laravel example project on PhpStorm is not compileable

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?

PHPBB 3 error while disapprove a post

Hi I have installed PHPBB3 and I tried to disapprove a post and i am getting following error
Fatal error: Uncaught exception
'Symfony\Component\DependencyInjection\Exception\InvalidArgumentException'
with message 'The service definition
"phpbb.report.report_reason_list_provider" does not exist.' in
/var/www/html/ddugky/forum/vendor/symfony/dependency-injection/Symfony/Component/DependencyInjection/ContainerBuilder.php:871
Stack trace: 0
/var/www/html/ddugky/forum/vendor/symfony/dependency-injection/Symfony/Component/DependencyInjection/ContainerBuilder.php(478):
Symfony\Component\DependencyInjection\ContainerBuilder->getDefinition('phpbb.report.re...')
1 /var/www/html/ddugky/forum/includes/mcp/mcp_queue.php(1245): Symfony\Component\DependencyInjection\ContainerBuilder->get('phpbb.report.re...')
2 /var/www/html/ddugky/forum/includes/mcp/mcp_queue.php(122): mcp_queue::disapprove_posts(Array, 'queue', 'unapproved_post...') #3
/var/www/html/ddugky/forum/includes/functions_module.php(674):
mcp_queue->main('queue', 'unapproved_post...') #4
/var/www/html/ddugky/forum/mcp.php(311): p_master->load_active() #5
{main} in
/var/www/html/ddugky/forum/vendor/symfony/dependency-injection/Symfony/Component/DependencyInjection/ContainerBuilder.php
on line 871
I found out reason because phpbb did not contain reports folder and now i created report folder and its contents yet again same error is displayed
Can anyone please help

Joomla - Uncaught exception, Error 500 - less block

I've migrated a Joomla site to a new server, updated the configuration.php file, and I'm getting these errors:
Fatal error: Uncaught exception 'RuntimeException' with message 'Less Parse Error: parse error: unclosed block' in
/var/www/websites/alwaysevolving/libraries/gantry/core/gantry.class.php:1141 Stack trace: #0
/var/www/websites/alwaysevolving/templates/rt_cerulean/features/styledeclaration.php(45): Gantry->addLess('mediaqueries.le...') #1
/var/www/websites/alwaysevolving/libraries/gantry/core/gantry.class.php(415): GantryFeatureStyleDeclaration->init() #2
/var/www/websites/alwaysevolving/libraries/gantry/gantry.php(289): Gantry->initTemplate() #3
/var/www/websites/alwaysevolving/libraries/gantry/gantry.php(439): gantry_template_initialize() #4
/var/www/websites/alwaysevolving/templates/rt_cerulean/lib/gantry/gantry.php(21): include('/var/www/websit...') #5
/var/www/websites/alwaysevolving/templates/rt_cerulean/index.php(15): require_once('/var/www/websit...') #6
/var/www/websites/alwaysevolving/libraries/joomla/document/html/html.php(531): require('/var/www/websit...') #7
/var/www/websites/alwaysevolving/libraries/joomla/do in /var/www/websites/alwaysevolving/libraries/gantry/core/gantry.class.php on line 1141
It looks like there's a problem parsing one of the less files, but:
I can't tell which one of the less files has the issue
The less files were fine on the other server
The site seems fine, so it seems like something in this template doesn't like my new server.
Thoughts??
Thanks!
The error message is a stack trace, but looking at it, it appears that the Gantry framework parsing the less file called mediaqueries.less.
I strongly believe that you have forgetten to close braces }. make sure to check the line number will help you resolve the issue.

Resources