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

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

Related

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

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.

instance of ParseError given in /var/www/html/myanants/lib/Cake/Error/ErrorHandler.php

After I did first upload cakephp project to server ,this fetal error occurrs.
Fatal Error
Error: Uncaught TypeError: Argument 1 passed to
ErrorHandler::handleException() must be an instance of Exception,
instance of ParseError given in
/var/www/html/myanants/lib/Cake/Error/ErrorHandler.php:116 Stack
trace: #0 [internal function]:
ErrorHandler::handleException(Object(ParseError)) #1 {main} thrown
File: /var/www/html/myanants/lib/Cake/Error/ErrorHandler.php Line:
116
Notice: If you want to customize this error message, create
app/View/Errors/fatal_error.ctp
You are running a non-PHP7 compatible CakePHP 2 version on a PHP7 system - that won't work. Upgrade your CakePHP dependency to at least CakePHP 2.8.x.
2.8 Migration Guide
CakePHP 2.8 is a fully API compatible upgrade from 2.7. This page
outlines the changes and improvements made in 2.8.
PHP7 Compatibility
CakePHP 2.8 is compatible with, and tested against PHP7.
[...]
https://book.cakephp.org/2.0/en/appendices/2-8-migration-guide.html

Blank white page when finished uploading files to server laravel5

I have finished uploading files to server inside demo folder, but when i visited i got blank white page. when i visited somedomain.com/demo i got blank white page. Can anyone help me please. My folder directory start with demo. Inside demofolder i have app,bootstrap,config etc folders.
when i view storage/log file i got
[2015-09-20 06:38:00] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()' in C:\xampp\htdocs\sidinsu\project\vendor\laravel\framework\src\Illuminate\Foundation\Console\ClearCompiledCommand.php:28
Stack trace:
#0 {main}
[2015-09-20 06:52:16] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()' in C:\xampp\htdocs\sidinsu\project\vendor\laravel\framework\src\Illuminate\Foundation\Console\ClearCompiledCommand.php:28
Stack trace:
#0 {main}
[2015-09-20 06:53:23] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()' in C:\xampp\htdocs\sidinsu\project\vendor\laravel\framework\src\Illuminate\Foundation\Console\ClearCompiledCommand.php:28
Stack trace:
#0 {main}
[2015-09-20 06:58:28] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to undefined method Illuminate\Foundation\Application::getCachedCompilePath()' in C:\xampp\htdocs\sidinsu\project\vendor\laravel\framework\src\Illuminate\Foundation\Console\ClearCompiledCommand.php:28
Stack trace:
#0 {main}
The blank page suggests a 500 error and your logs back this up.
Looking at your logs it is an issue with the vendor/compiled.php file.
Just delete this file, run composer update, and then php artisan optimize after the update to rebuild compiled.php.
On a side note, the URL to view this should be somedomain.com/demo/public as this is where the index.php file is located - unless you have already dealt to this.
When you move Laravel 5 to a production server please do the following:
Change permissions of storage and bootstrap folders to 0755 or 0777 chmod -R 0777 storage/
composer install
composer update
artisan cache:clear
This will resolve your dependencies and make laravel functional.
When you get packages conflicts after doing the above steps remove the packages from app/config/app.php and delete their folders from vendor and run composer update.
Also make sure you will meet Laravel 5 minimum requirements. PHP 5.5.9 is required.

Yii 2 The directory does not exist on shared enviroment

I have problem with my web site, when i try to access it says
Fatal error: Uncaught exception
'yii\base\InvalidParamException' with message 'The directory does not exist: C:\HostingSpaces\zerguttnalog\zergutt.com'
in C:\HostingSpaces\zerguttnalog\zergutt.com\vendor\yiisoft\yii2\base\Module.php:224 Stack trace:
#0 C:\HostingSpaces\zerguttnalog\zergutt.com\vendor\yiisoft\yii2\base\Application.php(358): yii\base\Module->setBasePath('C:\\HostingSpace...')
#1 C:\HostingSpaces\zerguttnalog\zergutt.com\vendor\yiisoft\yii2\base\Application.php(223): yii\base\Application->setBasePath('C:\\HostingSpace...')
#2 C:\HostingSpaces\zerguttnalog\zergutt.com\vendor\yiisoft\yii2\base\Application.php(202): yii\base\Application->preInit(Array)
#3 C:\HostingSpaces\zerguttnalog\zergutt.com\wwwroot\index.php(12): yii\base\Application->__construct(Array)
#4 {main} thrown in C:\HostingSpaces\zerguttnalog\zergutt.com\vendor\yiisoft\yii2\base\Module.php on line 224.
On my local machine everything is ok (xampp on windows), i don't know what is happening on the server. Can anyone help?
Apparently you have set the base path of your application to (C:\HostingSpace..), it will work fine on your local machine because the directory exists, but on a different server yii will not find this directory.
Check your configuration files, you will fine a line starts with.
'basePath' => ... you need to change it to 'basePath' => dirname(__DIR__), and hopefully it will work fine.

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