I'm upgrading a react-admin application from react admin v3 to v4. There's a note in the upgrade guide that I should also upgrade material-ui from v4 to v5 with a link to the (very lengthy) MUI upgrade guide. This leads to a few questions:
What's the order of operations? Do the react-admin upgrade first? MUI upgrade first? Some mixture?
The first step of the MUI upgrade guide is "add <ThemeProvider> at the top level of your application". In the case of a react-admin application, the theme is passed in as a prop to <Admin>, so it's not clear if this is something that we need to do. How should this be handled in a react-admin application?
Related
CRA now uses React 17 default and it is advised that we use an older version of CRA that uses R16 whilst MUI5 is being developed. Can someone advise me how they download an older version of CRA? I have tried npx create-react-app client --typescript --scripts-version react-scripts#3.4.4 and I get Error: Cannot find module 'cra-template'. I know this is strictly a CRA question but I thought someone that uses MUI might already have some experience with this problem.
I have a popup in code written in Kony visualizer V8, I want to export all of them and import it to Kony Visualizer V9.
Note: Kony Visualizer V9 doesn't support the normal popups and I don't need to create it from scratch.
This is the popup's image inside the Visualiser V8:
Had a similar requirement recently and as V9 doesn't support HBOX or VBOX, created a component for popup and used that in UI. After changing all popups to components you can upgrade from v8 to v9 without issues.
Also do not use masters as that is also not compatible with V9.
You can use components and reuse them for popups wherever needed.
Gone thru the same situation before. Found that HBOX, VBOX and few other widgets which are used in the old versions are deprecated in the recent versions. Hence all the old widgets should be updated to the latest equivalent widgets.
If the project is mobile application then Temenos has an upgrade tool which will help you in making the changes to the project and upgrade it. But if the project is of Desktop web then we need to manually update the widgets one by one. Once all the deprecated widgets are upgraded then export the project and import the same in latest visualizer.
I have a (complicated, live, in production) ionic app that is currently on ionic-angular 3.9.2 but has been around since (I think) the v1 days. There are no tests (yikes).
I see that Ionic 4 ships with some e2e testing support which is great, but does me little good since it's not compatible with the version that I'm on.
I'd like to get some e2e tests in place prior to biting the bullet and migrating up to v4 and all the many changes that will entail.
Are there any resources available that can help me add tests to a v3 app in a way that will be compatible with v4 as I go through the update process?
I have a meteor project. In this project Bootstrap v3 used. now I want to update this project in Bootstrap v4. What the steps I need to do.
Bootrap have a migration guide -
https://v4-alpha.getbootstrap.com/migration/
Where can I find information about upgrading Magento Enterprise 1.7. to the latest 1.9. ?
There's no such documentation.
Your general approach:
1. Close production server
2. Backup all DBs and Magento installation
3. Turn off all your custom extensions and themes
4. Delete from HDD: core Magento modules, their layouts, all standard themes and cache.
5. Get 1.9 EE, copy it over your installation
6. Request Magento through http
7. Walk at your site, notice errors and warnings, fix them
8. Check documentation and update for your theme, whether it supports EE 1.9. Turn it on if it supports, otherwise you'll need another theme.
9. Check documentation and updates for all your custom extensions - whether they support 1.9. Turn them on - one by one.
You won't have any problem with upgrading all core DB data - it's made automatically.
You'll have problems with your custom theme, as you'll need new version with support for 1.9. And you'll need to check your custom extensions and upgrade their source and DB data to fit 1.9.
Generally all Magento upgrades work by running the updated code with the old database. The differences will be detected and incorporated automatically on the next page request. Magento keeps track of every module's version number for this reason.
Because there is a chance some modification will break it is best to do this on a new (temporary) site then add the modifications back in gradually. That way the old site is still active and uninterrupted.
I think there is no official documentation. The best way is to figure out what core functionality is used in your customizations and after that look at theirs realization in new version: does it changed or not.
To know what was changed in new version you could check changeslist