Yii2: /vendor/autoload.php causes error 500 - yii2

I have installed yii2 (I have tried advanced and basic installations and deleted / repeated the process several times). In all instances the autoload line in the index file causes an error 500:
require __DIR__ . '/../vendor/autoload.php';
If I comment out the line above, I do not get the error 500 (although Yii obviously does not work). As soon as I include the line, I get an error 500.
I have reinstalled composer and reinstalled Yii2 but no success.
My only observation is that the alphanumeric below does not seem to match the alphanumeric seen in the /composer/autoload_real.php but I am not sure if it should.
return ComposerAutoloaderInit76b6976ae6a0da7190a4d881939374a2::getLoader();
Please advise
UPDATE
I deleted the composer.phar file
I deleted the full html directory
I reinstalled composer
I reinstalled yii2 basic in html
The same error occurs:
==> error_log <==
[Tue Jun 11 04:49:50.851130 2019] [:error] [pid 21494] [client 10.176.18.31:63288] PHP Fatal error: Class 'ComposerAutoloaderInit76b6976ae6a0da7190a4d881939374a2' not found in /var/www/html/vendor/autoload.php on line 7
Interestingly, I notice that the alphanumeric 76b6976ae6a0da7190a4d881939374a2 is exactly the same despite reinstalling composer. I am not clear how composer works but I would've presumed this alphanumeric would update?? Is there a cache I am supposed to clear somewhere?
When I view the /vendor/composer/autoload_real.php I see it is called:
ComposerAutoloaderInitcc7884a20c85dc8a5213cc9c1a84bc90
This does not match the autoloader file and has changed following the re-installation. Again, I am not completely clear how composer works but this seems to be odd.
Many thanks for your help

Thank you Yerke - your suggestion worked perfectly
I simply ran composer dump-autoload and then composer update

Related

Fedora 33 openjdk 8 error showing on terminal

I am getting below error whenever I open the terminal. This began happening after upgrading Fedora Workstation 32 to 33.
ERROR: ld.so: object '/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.265.b01-1.fc32.x86_64/jre/lib/amd64/libzip.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
I still have OpenJDK 8 installed and even when uninstalled, above error keeps popping up making my terminal untidy
The answer here helped me to get a solution. I had the below the line in .bash_profile
./home/admin/Adempiere/postgresql/8.1.5/PGSQL.env
. I simply commented it out as below and my issue was solved. Read the above answer for the details of why this caused me issues. In my case, the program "Adempiere" had been uninstalled but it didn't remove this path which no longer existed.
#./home/admin/Adempiere/postgresql/8.1.5/PGSQL.env
If you get any error related to the above, review paths set in your .bash_profile
or /.bashrc , if you have a missing path; definitely this will throw this error

Cloud Function Build Failed

I just changed two lines of code in the Google cloud functions source code using inline statement, the two lines of code involve parsing date string using datetime library, no updates to anything else. This same deployment has been working for more than a year now.
All of a sudden I get two errors -
Error 1 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"pip_install_from_wheels had stderr
output:\n/opt/python3.7/bin/python3.7: No module named pip\n\nerror:
pip_install_from_wheels returned code: 1", "errorType":
"InternalError", "errorId": "ECB5F712"}}
Resolved that by removing pip from requirements.txt (again not sure why this is a problem now and not for over a year)
If I address 1, I get the following error -
Error 2 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"gzip_tar_runtime_package gzip /tmp/tmpGLHQx9.tar -1\nexited with
error [Errno 12] Cannot allocate memory\ngzip_tar_runtime_package is
likely not on the path", "errorType": "InternalError", "errorId":
"2A1581FF"}}
Memory is already at 2048 and nothing changed other than the two lines of code above.
Let me know if this has been happening and what is the resolution.
It looks like this has to do with packages than anything else. I deployed a dummy function and added each package from requirements.txt until it failed. It turns out the problem packages were
a. gpflow
b. tensorflow
Last deployment with these packages was successful as of Feb 20. Not sure why I can't install them without those errors anymore. regardless, tried using the versions that would have been consistent with Feb 20 timeline with no luck. So refactored my code and removed all the functionality that was using that and deployed successfully.
Request to Google Cloud Folks : Why this behavior ? Also "Invalid ARGUMENT" in logs (Stackdriver or google cloud logging whatever you call it) is misleading.
The first error, as explained in this post, is due to pip being defined in your requirements.txt file. Specifying pip as a dependency for the function causes message to appear. You did the right thing by removing it from the requirements.txt file.
The second error usually appears if the number of files or the size of the content that is being uploaded is too big and the instance used to deploy your code runs out of memory. You perhaps were using too many dependencies or static files, as explained here.

Moodle: Installation failed - Coding Error Detected

I have tried to install Moodle 3.5.1 on my development server (Apache 2.4.29 and MySQL v.5.7).
The installation process went smoothly: The MySQL database has been set up, all required PHP packages are installed, the system has been successfully installed, all file permissions are correct.
After the installation I only get the following error:
"Coding error detected, it must be fixed by a programmer: PHP catchable fatal error"
There are no further error messages. There are no error messages in Apache Error log or PHP log files. In the PHP ini file the display of error messages is activated.
So I can not figure out what did not work or how to fix it.
Put error_reporting(E_ALL); and ini_set('display_errors', 1); in the beggining of the script you see problem in for more debug info
Moodle 3.5 requires PHP 7
https://docs.moodle.org/35/en/PHP
Could that be your problem?

In RouteRegistrar.php line 75: Attribute [Groupe] does not exist

when i usephp artisan serveto run my project it show me on error like this:
-->In RouteRegistrar.php line 75:
-->Attribute [Groupe] does not exist.
I had the same issue and bumped into your question via the Google-sphere.
Running composer install did the trick for me. I believe (at least in my case) that this error is the result of mismatched Laravel versioning vis-a-vis the routing code (I had the later version of Laravel specified in my composer.json but was working on an environment where I hadn't yet updated my composer packages).

PHP Parse Error: /vendor/cakephp/cakephp/src/I18n/functions.php on line 26

I've encountered this error in my apache2 error.log while accessing a project running on WSL.
[Tue Feb 28 14:42:17.331656 2017] [:error] [pid 25334] [client 127.0.0.1:52043] PHP Parse error: syntax error, unexpected '.', expecting '&' or variable (T_VARIABLE) in /mnt/c/development/public_html/xxxx/vendor/cakephp/cakephp/src/I18n/functions.php on line 26
I'm running:
Cake 3.4.2
PHP 7.0.16-3+deb.sury.org~trusty+1
On Windows Subsystem for Linux
I have other cake projects working fine on this setup but none that are v3.4*.
I have no idea how to solve this problem as it's in the Cake core. Any advice on how to proceed from here would be great.
Please ask if you need any more info.
There is no 3.4.3 branch (yet)
There is no 3.4.3 branch (yet), double check that you are looking at the correct info. Maybe it was published by accident and has been retracted, if you really have version 3.4.3, try reinstalling your applications dependencies.
Ensure that PHP used by Apache PHP is up to date
Also make sure that your server is actually using the PHP version that you think it does, the Apache PHP module and the PHP CLI binary are two different things, and the FPM/CGI binary usually also isn't used on the CLI, ie the CLI and the server often times use different versions.
The error message you are referencing suggests that PHP couldn't handle the ... variadic function operator, which would mean that Apache is using a PHP version prior 5.6