hi federico,
did you check the apache error log?
can it be that your app/cache/prod directory does not exist or is not
writeable for the web server?
cheers,
david
Am 14.03.2011 18:44, schrieb Federico Bernardin:
> Hi,
> yes the production deployment is on the root of the domain.
> If I write: ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi federico,
did you check the apache error log?
can it be that your app/cache/prod directory does not exist or is not
writeable for the web server?
cheers,
david
Am 14.03.2011 18:44, schrieb Federico Bernardin:
> Hi,
> yes the production deployment
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
try to run app/console
you will see a list of available commands, one of them being
doctrine:schema:create
Processes the schema and either create it directly on EntityManager
Storage Connection or generate the SQL output.
there is a lot of docum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
i try to set up varnish in front of our symfony2 application and have a
few questions that seem not to be covered by the documentation [1] [2] [3]
we use form authentication with native sessions and the remember me
feature active.
1. can i te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi chris,
this approach sounds ok to me. you might realise that you want to have
some routes outside your cms anyways, for applications that display data
(like lists of pages or rss feeds).
i guess the most fancy approach would be to hook deeper into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi jab,
one of our customers just went online with http://www.joiz.ch/
all shiny new symfony2.
cheers,
david
Am 29.03.2011 20:23, schrieb Jab..:
> Any real time websites built with symfony that I could look at to
> understand its capability
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi and thanks for documenting this, it really helps.
i think there are two glitches in your config:
you duplicate "bundles" by having it both in write_to and and in your
stylesheet tag. the most simple use case is probably:
write_to: %kernel.root_dir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
until there is a doc up, i just post findings about assetic here.
we have now lessphp working if you want a less filter. you can update
your vendors.sh to get lessphp from git://github.com/leafo/lessphp.git
and put it into vendor/lessphp/
to make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
this is a shortcoming of the current file upload. there is an ugly hack
to make it "just work" for now, and some more info in this thread:
http://groups.google.com/group/symfony-devs/browse_thread/thread/f6ee02520e244c96/973d3cc5ac59cee5?lnk=gst&
hi,
for a symfony2 project, i use twig. i have a template that outputs a
tree (nested php array)
what i try to do is: check if there is a 'children' field on the entry,
then if the children list contains at least one entry. (i have 3 cases:
an entry has children, it has no children (empty array) o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yeah, that rename confused me as well. i opened an issue to at least
improve the exception message to something more clear.
Am 13.04.2011 12:32, schrieb Carl:
> Well then. I guess I should have just waited 20 minutes before posting
> anything. It look
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi cezar,
you can do something along
navigation:
pattern: /{path}
defaults: { _controller: your controller }
requirements: { path: .* }
the requirements for path make it also use the "/" character.
cheers,david
Am 13.04.2011 11:38, sc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i think the doc about routing still needs some love:
http://symfony.com/doc/2.0/book/routing.html
a section about the pattern separators would be helpful, with examples
like this one or the famous "catchall" as in
example:
pattern: /cms/{path}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
thanks oscar, john and jordi
a cool syntax, the for/else, twig is really useful :-)
actually i need to distinguish whether i have 0 children, > 0 children
or the children array is missing, which means the code did not check
whether there where children
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
was starting to write you should have a look at the doc
http://symfony.com/doc/2.0/book
but actually, it is not in there, or at least not where i would expect
it to be.
however, google for symfony2 event brings up this as second result:
http://blog.b
,
cheers,david
> Hey David,
>
> I was just looking at your post because I'm kind of facing the same
> issue, I want to avoid sending session cookies for users that are not
> logged in. I wonder whether you managed to solve it, did you?
>
> Cheers!,
> Mauricio.
>
Am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 29.04.2011 12:09, schrieb robjensen82:
> What's the point in the parameters.ini? why not just stick to
> config.yml?
the idea is that config.yml is under version control, while
parameters.ini contains confidential data like database password and
su
ght config_prod.yml would
> have been useful for exactly the situation you're describing. O well
> I've managed to chop it out.
>
> Rob
>
> On Apr 29, 11:20 am, David Buchmann wrote:
> Am 29.04.2011 12:09, schrieb robjensen82:
>
>>>> What's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi robert,
the master branch is where development takes place, so it is the latest
version. (except for development branches when some area is heavily
reworked - the rest comes in mostly with pull requests)
the beta1 distribution includes a slightly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i while ago (back in march) i had tried to use ESI and never managed to
have symfony render an tag. i gave up at some point, not
sure if we do something wrong or if symfony has a bug.
you do tell varnish to send the esi capability headers along with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
i think you should generate the current route with all locales you
support and directly use those to switch the language, instead of having
the client send a request and then redirecting.
as a side note, instead of the string replacement, you coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i have binary content that i have to deliver to the client. what is the
right way to do it? i found two solutions, but neither seems really good.
//in my controller, i get a binary stream (its stored in the database)
$picture = $this->method_t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
hm, yes i think this is what i thought. we did it that way but we have
extremly few routes in our project.
on the view layer, its easy as we just wrote a small snipped for that
element that is included in the base layout.
maybe somebody else know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
i am also afraid that the forums could have less replies.
unless people are so kind as to subscribe to get emails for the areas
they are interested in, and take the pain to go to the forum to type an
answer.
on the other hand, this list sees more traf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
is this in dev or production mode? if in production, did you generate
the assets with
app/console assetic:dump
?
cheers,david
Am 22.05.2011 14:23, schrieb John Blobsmith:
> I try to use assetic with php template like this :
>
> stylesheets(array('p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this sounds like you messed up your apache configuration - or you have
some other server running on 8080 already.
this has nothing to do with symfony. you should check the setup of your
machine.
just to try out, you can also try some other port differ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi alex,
what did you do, did you try out some bundles or write your own? i would
be interested in this too :-)
cheers,david
Am 18.05.2011 17:55, schrieb Alex Gilbert:
> Hey folks!
>
> With symfony 1.4, I used sfFeed2Plugin quite a bit.
>
> With S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bumping this up as i got no reply...
any input?
Am 11.05.2011 11:24, schrieb David Buchmann:
> hi,
>
> i have binary content that i have to deliver to the client. what is the
> right way to do it? i found two solutions, but neither seems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi everybody,
any updates on this one? the apply_to: annotations work fine, really
like them. i do not get any errors for assetic:dump, neither with the
- --watch parameter nor otherwise.
i would love to use the assetic.assets notation for a named s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi mauricio,
the _locale is automatically taken from the session, no need to
configure anything there. you can just to path('homepage') if you want
the path to the homepage in the current session language.
cheers,david
Am 31.05.2011 14:48, schrieb M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
seems to be a known bug that should be fixed soon:
https://github.com/symfony/symfony/issues/1152
and yes, we all hope to see a comprehensive assetic documentation...
Am 30.05.2011 14:12, schrieb Vyacheslav Slinko:
> config.xml:
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi thomas,
some feedback and hints on the AdminBundle. (i post this to the list, as
people might stumble over the same details as i did...)
i followed http://rabaix.net/AdminBundle/html/index.html
first: THANKS! this is an awesome tool!
tutorial c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this sounds spanish to me :-)
but maybe you want to have a look at https://github.com/sonata-project -
they provide a jquery bundle, and the adminbundle is using it... maybe
you can figure things out from the admin bundle source code...
cheers,david
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
according to UPDATE.md in the root of symfony:
...
beta4 to beta5
- --
...
* The AsseticBundle has been moved to its own repository (it still
bundled with Symfony SE).
...
so if assetic is not part of the SE, this sounds like a mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 for splitting into new lists
> As SF2 RC1 is about to be released, this is the perfect time to move to
> a new list. The answers on that list are more likely to be "correct" to
> anyone searching the archives (prior to the API being stable, an ans
35 matches
Mail list logo