Is the standard way to go through a mult-step work-flow? I would like
to know too.
I don't think you will have a problem with your approach. I think back
in the day I had problems serializing forms because some widgets had
an unrealizable database/pdo handle bound to them, but I think its a
non i
I think using the ysfDimensions plugin would be the best way to go,
have you tried it with 1.4? with 1.2 it worked fine, I was able to
extend views, actions and configurations based of a dimensions, just
as the readme states. It was robust, consistent and worked well.
Multiple sites in production
Can someone get there experiences going with a small Symfony and Flex
project.
Perhaps a few chapters in a pdf along with all the other
documentation.
If there are no real world examples that we can find to get documented
then one could convert Jobeet to have portions of the R.I.A. (Rich
Internet
I like to:
a) Write a sitemape (using http://www.omnigroup.com/applications/OmniGraffle/)
and put colored background boxes of modules (i.e. app/front-end/
modules/) so you can clearly see on all the pages belonging to a
module and it tends to segregate the sites functionality too so
requirements
If one had to write a migration for sfGuardUser or some inherited form
of it. How would this issue affect the implementation.
With best regards,
Alex Stoneham
On Oct 14, 1:55 am, Matt Robinson wrote:
> On Oct 13, 3:13 pm, Pablo Godel wrote:
>
> > I am using sfDoctrineGuard plugin. When I run
I think this has doctrine support now, but its not documented yet.
On Jul 24, 2:37 am, kev wrote:
> Same here,
> i actually posted a message on the forum too
> :http://forum.symfony-project.org/index.php/m/82477/?srch=datagrid#msg...
> I also found the sfDataGrid plugin which is unfortunately o
PS, sounds like your using the wrong wheel for api requests. ;-)
On Jun 9, 3:25 pm, Marijn wrote:
> P.s. it makes use of sfWebBrowserPlugin to prevent reinventing the
> wheel for api requests but it can be injected with any object that
> implements a sfWebBrowserInterface
>
> On Jun 10, 12:23 am
You your talking about creating a solid 'Universal Payment API' plugin
and have what you think is a good core of it, I am sure we can work
out implementing an adapter from Paypal into that if you were to make
it robust enough to be a public symfony plugin and still easily
achieve PCI Compliance.
Has any one tried sfMultisiteGuardPlugin and sfMultisiteThemePlugin ?
I still think this thread needs more input on how others do this.
On May 26, 10:26 am, Guilherme Veras wrote:
> I casually create centralized applications.
> Put in the folder WEB systems available thus gain a high rate of re
