I foolishly updated the version of Adaptive Theme from 7.x 2.3 to 3.2 and broke my Pixture Reloaded theme which requires AT 2.3. I restored AT to 2.3 BUT several blocks are not visible (in particular the Content block. Can anyone suggest how I can fix this before my community group gets upset that their site is offline?
Related
Apparently, the ExtJS' forum isn't working anymore, so asking the question here.
I am trying to upgrade ExtJS integrated in a big application. Currently, it's using version 3.4.1 and I have to upgrade it to 7.5.0, so a lot of changes are expected. It's my first time working with ExtJS. I've been reading their documentation & examples for a while now, but I'm having issues understanding some things.
If someone's experienced with ExtJS, could you tell how big is the difference between these versions? What kind of effort is expected for this upgrade? Will I have to rewrite everything, or just changing files and API calls would be enough?
Another thing is that the folder structure in the new version looks quite different from the older version. Ours using 3.4.1 looks like this -
ext-js 3.4.1 image
There are no new adapter or resources folders in the new verion. Are these folders not required anymore, or is it possible to get the same folder structure with the new version?
Is it possible to download older versions of ExtJS like 4.x, 5.x etc.? I tried but couldn't find it, I was able to download the older documentation though.
Downloaded the latest ExtJS version from here.
Referring this Sencha ExtJS documentation.
Any help would be appreciated. Thanks in advance.
Download
You should download the version from support.sencha.com. There you can find all versions.
To access the download page, you need to log in. If you have lost your login, you can contact Sencha's licensing department.
Make sure you have a valid license.
Upgrade
If you are new to Sencha, you should not do the work yourself. Between version 3 and 7, there are at least two new coding paradigms and you'll have to rewrite everything. Unfortunately, there is no easy upgrade process from 3 to 7. If you had to upgrade from 5 to 7, it would be possible to ignore all the cool new features, but if you are starting from 3, you will have to rewrite everything.
Building process
In your screenshot, I can see that you are using the full ExtJS file. But are you really building the application? That means you end up with a single js file and a single css file.
Are you building your application?
Are you using SCSS?
You should definitely contact someone with experience. I've done quite a few upgrades in ExtJS to know that you need help with this.
I am working on consolidating DNN portals from various versions of DNN to the newest install I have at this time.
How do I take a DNN portal on DNN 5 (or even DNN4) and import into a DNN 7.3 host? Will the skin be supported? break? content? These are mostly content-rich portals so i want to move the portal content and skin over to the new host so its easier to maintain and have fewer installs that are outdated. Please let me know
This is not something that will be easy to do. You'd probably be best served by doing the following.
Backup the DNN 5 site (files and database)
Restore the backup to a new IIS website/database
Upgrade that DNN 5 site to 7.3
Export a Portal Template from the upgraded site
Import that portal template into your production 7.3 environment.
Even that won't be guaranteed, you'll likely have modules that won't work, and the skin almost definitely won't work.
I would simply upgrade the site to 7.3 and fix what is necessary myself.
I think that you have to do step by step. First backup both the code and the data base, after that upgrade to the last version 5.x, then to the first stable 6.x then to the last stable 6.x then to the first 7.x and then to the 7.4.
Good luck
As Chris said "Even that won't be guaranteed, you'll likely have modules that won't work, and the skin almost definitely won't work.
I would simply upgrade the site to 7.3 and fix what is necessary myself."
I would like to choose which versions of Silverlight plugin to target, but can't find any recent statistics on the install base, let alone the version break down. Statowl.com/silverlight.php isn't returning any data and riastats.com is down. Some articles are referencing a 76% web clients installation base around 2012 with high Silverlight version 4 usage, but that's pretty outdated information. Does anyone have up to date information for the Silverlight plugin install base, preferably with version breakdown?
The client is backwards compatible. I think you will find most users are running the V5 client as that is pushed out with MS updates and was released 2+ years ago. You can set the min runtime version on the html Silverlight plugin element to alert users running an older version to upgrade to a version compatible with the version your app is compiled against.
http://msdn.microsoft.com/en-us/library/cc917842(v=vs.95).aspx
I have an odd issue that started appearing after upgrading EPiServer CMS 6 to EPiServer CMS 6 R2.
DataFactory.Instance.GetChildren(page.ParentLink);
The above code returns no children when I run it on the actual site but when I'm using the Editor mode and browse to the page, I get 36 results (which is correct). The datafactory works every other place on the site and it works perfectly for the Swedish site, however it doesn't work for any other language. I should point out that this worked in all languages before the site upgrade to CMS 6 R2.
I need those children! Any ideas?
Are the child pages published for those languages?
Does this help? It's for CMS 5 but the principle is the same.
http://labs.episerver.com/en/Blogs/Mari-Jorgensen/Dates/2009/2/Breaking-change-in-GetChildren/
Managed to solve this by specifying the language branch in the call aswell. Didn't need to do this prior to Epi 6 R2 and I still think it's odd that it's working in Editor mode but not on the actual site.
DataFactory.Instance.GetChildren(page.ParentLink, new LanguageSelector(page.LanguageBranch));
We've noticed a compatibility issue with a Silverlight 3 app which runs fine with v3.0.40818, v3.0.50106 and v4.0.50401 but refuses to load in v3.0.40624. Instead it gives a message box saying a more recent version of Silverlight is required.
Does anyone know what the changes were between 3.0.40624 and 3.0.40818 or why the app might not be compatible?
I think you'll find that 3.0.40624 is a Beta version of Silverlight 3. You should recommend to any users you have that still have this Beta version to upgrade.