I rebuilt everything from the beginning and now it works: symfony
mysteries!
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to t
Thanks for your hints, I'll follow all your suggestions. I hope I can
solve my problem.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
T
You may have already checked this stuff, but I find that whenever I
get a white screen it is typically one of these things:
1. The cache and or log dirs are not 777 (chmod -R 777 cache log)
2. There is a open_basedir issue (this will add an error to the apache
error_log)
3. There is a var_dump or p
my error log is completely blank... I don't know how to solve this
problem...
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to
On Tue, 4 May 2010, SatBoy78 wrote:
> I've seen apache log, and I've seen that all works well...
The error log?
Usually a blank screen means the action died before it could complete and
fender the page. In those situations, the Apache error log is useful to
look at.
--
--
If you want to
yes, I'm using backend_dev.php and I've seen log file: all flags are
green, no one is red...
thanks a lot
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symf
To view error log in web page (instead of the blank page), check you have
fo_dev.php in your url.
2010/5/4 Daniel Lohse
> It's in the plugin itself but when you need to customize the templates for
> the signin action then you'll need to create a module in your app
> (frontend), create a template
It's in the plugin itself but when you need to customize the templates for the
signin action then you'll need to create a module in your app (frontend),
create a templates directory inside it and copy over the signinSuccess.php from
the plugin. At this point you can customize it and symfony know
I've seen apache log, and I've seen that all works well...
I've a question about sfGuardAuth module: symfony doesn't generate it
when I install the plugin?
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message bec
Ok. Maybe you should customize the sfGuardAuth module. See the step
corresponding at
http://www.symfony-project.org/plugins/sfDoctrineGuardPlugin, section begin
by "Customize sfGuardAuth module templates."
It could solve you problem.
In my case I customized it and it works fine.
2010/5/4 SatBoy78
no, I don't have a sfGuardAuth module...
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-use
Ok I see nothing strange in your settings.yml.
Have you a directory sfGuardAuth in apps/yourBackOffice/modules ?
If yes, what do you have in your templates/signinSuccess.php and in the
action that correspond ?
2010/5/4 SatBoy78
> this is my settings.yml
>
> prod:
> .settings:
>no_script_n
this is my settings.yml
prod:
.settings:
no_script_name: false
logging_enabled:false
dev:
.settings:
error_reporting:
web_debug: true
cache: false
no_script_name: false
etag: false
tes
13 matches
Mail list logo
