Fatal error: Allowed memory size
When such errors occur, it is because the memory_size feature within the server's php.ini must be increased twice or as much as necessary.
1. Find the php.ini file with these sample paths:
- Linux: /opt/NetMake/v9/components/apache/conf
- Windows: C:\Program Files\NetMake\v9\components\php
2. Then edit the php.ini with administrative permissions and search for "memory_limit":
3. Place a double value to the one you have by default, for example: from 512 to 1024.
4. Save the changes and restart the apache: https://scriptcase-support.kayako.com/es/article/1321-reiniciar-apache
PHP error level - error_reporting
The error_reporting directive in php.ini defines the levels of errors that PHP will report, the levels of errors are: Errors and Logging Value Constant Description Note 1 E_ERROR (integer) Fatal run-time errors. These indicate errors that can not ...
Fatal error: Uncaught GuzzleHttp\Exception\RequestException
The Fatal error: Uncaught GuzzleHttp\Exception\RequestException: cURL error can be displayed in the Scriptcase interface in two situations When using the Google-integrated Calendar application When using the Google Drive API So that the error doesn't ...
The size of the backup file is larger than supported by PHP
If some users encounter this problem, perform the following changes below: In php.ini, there is the upload_max_filesize and post_max_size directives where both are policies that determine the maximum size of files that are uploaded to the server. ...
Fatal error: Array and string offset access syntax with curly braces is no longer supported
You can come across this error when running a login application created by a security module generated before Scriptcase 9.8. This error occurs only in an environment with PHP 8 or superior because of a change in the array elements access, that now ...
Connection error: error_profile_test_module
When we deploy a project and we find this type of error: "Connection error: error_profile_test_module" This error normally occurs when you use a different production environment DBMS Type than the development environment. To solve this, access your ...