I'm not really sure that I'm on the right track here but I think I am
and that I just need to the last pieces of the puzzle to get there ...
I want to use an seperated xManager for my entities (lets say
UserManager just like in the FOS\UserBundle).
Looking at the documentation about service
Thanks for the response, I got a lot of info from browsing more code
on github today.
The hardest part was actually getting the right syntax for yml instead
of the xml files I had been browsing :(
--
If you want to report a vulnerability issue on symfony, please send it to
security at
I've been playing around with sf2 lately and been looking at code from
the various github projects but I'm still not really sure what (and
more importantly *why*) is going on with the Model classes.
I've picked up on the concept that Entities should remain fairly
untouched from complex (business)
Maybe splitting up the google group for sf1 and sf2 would make it
easier to search for answers to
--
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
Looking around the google group and the various blogs (and
documentation in the book/cookbook) I get the feeling that most people
are now using twig as their templating engine.
When I started with sf2 I almost instantly decided that I wouldn't
want to use twig since learning and using yet another
I forked symfony-standard on github and I have no problem merging new
PRs into my repo.
But I think the problem for you is that you should have the vendors on
ignore already in P10 (I think I have) so try putting those on your
ignore and remove them from your repo before doing the merge so that
I personally just added new vendor bundles to the vendors.sh script
(since im a git-noob I dont know much about submodules and such).
I guess they use the vendors.sh to create the symfony standard
package ...
--
If you want to report a vulnerability issue on symfony, please send it to
security
I've been playing around with sf2 for a while now
and between the changing API,
low level of tutorials (because of the changing API I guess ^^)
and my inability to remember even APIs which I write myself I've been
digging through a lot of code to figure out what the functions I
should be called
I created a very basic form with sf2 but since it contains a lot of
fields I want to spread the process out of multiple pages to improve
the usability.
Now I was wondering how I should do that?
I think that the best way to do it would be to keep the whole form
config (the ***Type class) the way
I've been going at this problem for hours now so I figured I better
just ask for help to avoid my head exploding soon ...
I'll paste some snippets and then try to explain.
yaml mapping for doctrime ORM
GoGreat\DemoBundle\Entity\DemoUser:
oneToMany:
comments:
targetEntity:
https://github.com/rubensayshi/DemoBundle I placed the whole bundle on
github so you can take a look
--
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
-project.org/docs/orm/2.0/en/reference/association...
BR Stephan
On May 28, 6:54 pm, Ruben de Vries rubensay...@gmail.com wrote:
I've been going at this problem for hours now so I figured I better
just ask for help to avoid my head exploding soon ...
I'll paste some snippets and then try
*bump* I'm still stuck here :-(
On 4 jun, 11:21, Ruben de Vries rubensay...@gmail.com wrote:
cascade persist works like a charm (check out my ' this does work'
example) when called stand alone, but it just doesn't work when going
through the form.
because it seems the form API doesn't use
I'm struggling a bit to get my linux file permissions setup in a
manner where I can both use the CLI (app/console) and avoid issues
with apache not being able to access files.
The most often occuring problem is (ofcourse) the cache directory;
If I do `app/console cache:clear` WITHOUTH
Are there any bundles on github that demonstrate a fileupload?
I'm trying to implement handling the fileupload but I'm not really
sure how to do it 'the symfony way'
So some source code to dig through on github would be really helpfull
(A)
--
If you want to report a vulnerability issue on
I've created a small demobundle with the case, since that's a lot
easier then pasting a lot of code in here:
https://github.com/rubensayshi/DemoBundle
The bundle has two entities (DemoUser and DemoComment) which are
linked by a oneToMany relation which has the `casecard [persist]`
set on the one
Wow, awesome!
I won't be able to try implementing it untill 2night but the docs are
clear, thanks!
--
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
17 matches
Mail list logo