Symfony2 Deployment

2
votes

I'm currently installing a Symfony project on my PC having the same specifications yet it has been giving me the following error whenever I'm running the app in the dev environment:

Authentication request could not be processed due to a system problem.

I thought by just simply clearing the cache it would solve everything. I even tried to do the suggested process that might solve the problem from here. Yet it's still the same. I already cleared the cache(console and manual), created a new user by running this command:

php app\console fos:user:create testuser [email protected] p@ssw0rd

And even these:

php app\console doctrine:schema:update --force

php app\console doctrine:schema:update --dump-sql

What else do you think I should do?

Add-ons

When I run it with the prod environment, I receive the following errors and warnings:

Warning: Erroneous data format for unserializing 'Matrix\MatrixUserBundle\Entity\User' in C:\xampp\htdocs\Tracker\vendor\doctrine\orm\lib\Doctrine\ORM\Mapping\ClassMetadataInfo.php on line 869

Notice: unserialize(): Error at offset 46 of 47 bytes in C:\xampp\htdocs\Tracker\vendor\doctrine\orm\lib\Doctrine\ORM\Mapping\ClassMetadataInfo.php on line 869

Fatal error: __clone method called on non-object in C:\xampp\htdocs\Tracker\vendor\doctrine\orm\lib\Doctrine\ORM\Mapping\ClassMetadataInfo.php on line 872

1
phpsymfony
Need more info that that. How are you accessing the page? where is this error showing up? what version of symfony? - Chase
I'm using symfony2, I'm only new to this framework and still have a limited knowledge about this. This error appears whenever I attempt to log into the system. I'm using xampp by the way. - user123
do you login with app_dev.php in the URL? do you have any other errors in your server logs? - Chase
@Chausser I added something - user123
Have you installed the vendor libs? composer install ? - Chase

1 Answers

0
votes

There is an issue where upgrading to PHP 5.6 breaks the unserialize function. I encountered this using the JMSSerializerBundle in Symfony. It is fixed in the current master of JMSSerializerBundle so I fixed this problem by changing composer.json to use

"jms/serializer-bundle": "dev-master"

It may be that updating your doctrine version to use master in composer.json as mentioned here:

Symfony 2.5.3 and PHP 5.6.0: incompatibility issues?