Hi Maurits > Yes, warmly recommended by one of its authors. ;-)
As usual, I have tried it and now keep it :) > I have not written an uninstall profile myself yet (I probably should), > but I saw one in collective.blogging, including the accompanying > Extensions/Install.py that is indeed necessary. There is nothing in > GenericSetup that registers a profile A as the uninstall/undo profile of > profile B. Thank you for the pointer to c.blogging. > If you use the portal_quickinstaller I would think the CSS and > javascript get cleaned up automatically even without a custom > uninstaller, because portal_quickinstaller takes some notes during the > install. I am not completely sure if the same is true in Plone 3.3 when > using the Add/Remove Products control panel in the Site Setup. I will make some more tests around this. > If you call one profile 'default' and the other profile 'uninstall' then > the quick installer will sort these alphabetically and pick the first > one as the profile to apply when installing your package. So do not > call your uninstall profile 'cleanup' as then it will get picked as the > main install profile. Also, please use only lowercase letters, because > if you have profiles 'default' and 'Uninstall' I don't know which one > will get picked as the first; and there may even be differences in > sorting between Operating Systems. > I would be more surprised and alarmed at having a tests folder and a > tests.py file; I have seen this... I defenitly need to look at collective.testcaselayer more seriously. This is not a tests.py it would have been a python error, but testing.py as notice by the documentation. > At least in some Plone 3 versions (maybe all, maybe in Plone 4 too, but > Hanno may have fixed something there), when you do not have an 'en' > locale and your site has English as default language and French as > allowed second language, and someone comes along with a browser that > accepts first English and then French, the French translations will show > up instead of the default English. > > The idea is that Plone thinks like this: browser accepts English and > French, we have only a French translations, so we serve French. > > If a browser that only wants Dutch (with perhaps English accepted too) > comes along, Plone thinks: browser wants Dutch, we do not have it, so we > do not translate (which will usually mean: fall back to the default > English). > > Basically, if you add an English po file and do not translate anything > in there, this is a signal to Plone that the strings in your package are > English. If you sprinkle French words in your templates and python > files, you should add an untranslated French locale. Right, I will add then "en" locale for the b2 release. Thank you Maurits ! ----- Jean-Michel François aka toutpt http://toutpt.wordpress.com http://twitter.com/toutpt -- View this message in context: http://plone.293351.n2.nabble.com/collective-gallery-1-0b1-ask-for-feed-back-tp5084379p5103194.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
