Anthony, The app mostly uses the default styling which is why I was surprised so much of it seemed broken when I tried to migrate, prompting my initial post. It seems like it might be easier to start a new app and just move the controllers/views/models over from the old app and go from there.
lillian On Saturday, November 14, 2015 at 9:13:01 PM UTC-8, Anthony wrote: > > You're going from Bootstrap 2 to Bootstrap 3, which is essentially a > different framework with different layout, class names, etc. So, it's just > like any switch in front-end UI -- you may have lots of little changes to > get your markup to work properly with the new framework. See > http://getbootstrap.com/migration/. Also, be sure to use the Bootstrap 3 > formstyles for forms. > > Anthony > > On Saturday, November 14, 2015 at 11:38:32 PM UTC-5, lillian wrote: >> >> Hello, >> >> I have an existing web2py app and would like to have access to the >> updated bootstrap/css/js components in the 2.12.3 release. What is the >> best way to approach this? I tried updating from the admin page, >> recreating the welcome app, then copied over the new js/css dirs and >> layout.html into my app. Afterward I could use things like the jumbotron >> but the styling of most everything else is a mess. Missing icons, >> incorrect alignments, dropdowns missing carets, etc. >> >> Is there a better way to do this or do I have to go in and work out all >> the problems by hand? >> >> Thanks! >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
