Hi,
I have the same problem. The most tricky part in our case is, that the
new symfony rendered parts have to feel and look like the old rendered
parts.
How did you do that in your cases? Did you manage two parallel code
bases for your css and js which did almost the same thing?
Frank
Am 30.01.2010 um 17:34 schrieb Eno:
On Sat, 30 Jan 2010, alessandro cinelli wrote:
No, it's a huge bad written dynamic site.... :(
Is it straight PHP or some other framework?
how can i do that?
I tought to write a custom routing class, one that holds the old
site parts
and one for the new one.
I would take a subset of functionality, that can be encapsulated in a
module. I would setup routing for those actions. Then configure your
web
server (create folders, setuo htaccess rules) to route those urls to
your
new module.
Repeat for other sections of the site...
--
--
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
.
--
You received this message because you are subscribed to the Google Groups "symfony
users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en.
