I've seen a number of posts to the ML by people upgrading to 1.2 who are confused as to why their plugins aren't loading. I propose the following to make the upgrade smoother:
1. Update the project:upgrade1.2 task to upgrade ProjectConfiguration to include a call to ->enablePlugins() to enable those plugins installed at the time of upgrade. 2. Add a collapsable "new in symfony 1.2" message to the HTML exception template, explaining the necessity of enabling plugins explicitly. Thoughts? -- Kris Wallsmith | Community Manager [EMAIL PROTECTED] Portland, Oregon USA --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
