Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The parameter "stof_doctrine_extensions.uploadable.validate_writable_directory" must be defined. #205

Closed
ornj opened this issue Jun 24, 2013 · 18 comments

Comments

@ornj
Copy link

ornj commented Jun 24, 2013

Why? I'm not using the uploadable feature.

I haven't had this issue before. I'm still using Symfony 2.1 but am planning to upgrade soon. Could that be part of the problem?

@ornj ornj closed this as completed Jun 24, 2013
@ornj ornj reopened this Jun 24, 2013
@ornj
Copy link
Author

ornj commented Jun 24, 2013

Didn't mean to close.

@ornj
Copy link
Author

ornj commented Jun 25, 2013

Upgrading my server environment to PHP 5.4 made the error disappear. Running Symfony 2.1 and 1.1.*@dev.

@sogos
Copy link

sogos commented Jun 25, 2013

Same problem here but already in 5.4 (Symfony 2.3)

@cocomode18
Copy link

Same problem with PHP 5.4 Symfony 2.2, and setting the config file still didn't solve the problem.

@cocomode18
Copy link

I cleared my cache files manually and it fixed the problem.

@ornj
Copy link
Author

ornj commented Jun 25, 2013

I stopped having problems once I was using Symfony 2.1 and PHP 5.4. Before that I noticed that clearing the cache manually fixed my problem locally. When I deployed my application I had the error again when running my deploy hooks. You might want to check for that.

@stof
Copy link
Owner

stof commented Jun 26, 2013

This has been fixed by 2a15188

@stof stof closed this as completed Jun 26, 2013
@epicwhale
Copy link

If you face it by any chance, just delete the cache directory manually.

@pats
Copy link

pats commented Jun 24, 2014

This error still exists in symfony 2.5 and PHP 5.5.13

@toby-griffiths
Copy link

I can second @pats on that. I'm having this with Symfony 2.5 & PHP 5.5

@DougHayward
Copy link

👍 Also just had this error,

@Rekkuzan
Copy link

I just get this error. (Symfony 2.5, PHP 5.5) But delete the cache directory seems to solve the problem.

@aurelijusrozenas
Copy link

Deleting cache dir manually did the trick (Symfony 2.5, PHP 5.5).

@yLark
Copy link

yLark commented Dec 30, 2014

Deleting the cache manually worked for me too.
(Symfony 2.6, php 5.4.35)

@OskarStark
Copy link
Contributor

yes, this does the trick! manually clean the cache dir

@takeit
Copy link

takeit commented Mar 17, 2015

I also get this error with Symfony 2.5 and PHP 5.5.9, clearing cache folder manually fixes it, but actually this is not a proper solution.

@hilvar
Copy link

hilvar commented May 10, 2015

Symfony 2.6.5, PHP 5.5.20 with OpCache 7.0.4 and Xdebug 2.2.3, OS X 10.10.3 still has this problem in production but not dev environment

@michel1991
Copy link

delete the cache manually worked for me thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests