Upgrading umbraco version 4.11.10 to 6.0.0 - content-management-system

I want to upgrade my existing umbraco version project 4.11.10 to 7.5.4, and i decided to upgrade step by step in incremental manner. When upgrading version 4.11.10 to 6.0.0 using nuget package and replacing old dll files with newer one, i am able to run back end and front end side, but on back end, i am not able to view the list of "content" and list of "document types" from my existing project as well as looks like still it displays ui of back end of older version 4, but when i click on "about us", it displays version 6.0.0 as attached in screenshot, please help me to find out the solution, Thanks :) Check here in attached screenshotCheck here - Content not loading

Upgrading from 4.11 to the newest version of 7 should work, HOWEVER, if you're using custom data types, the chances are that some stuff is going to break, as v7 doesn't use UserControls for DataTypes anymore. Some data types can be straight swapped, some not so much. You should be able to see all the DocTypes and content etc though.
When you've swapped the DataTypes out, you may need to reformat the data to match the new DataTypes so you don't lose any data as well. This is something you'd probably have to do either with the API of directly in the database.
I've written some blog posts on upgrading Umbraco, have a read and see if they help:
http://www.attackmonkey.co.uk/blog/2015/10/upgrading-to-73-part-1-preparation
http://www.attackmonkey.co.uk/blog/2015/10/upgrading-to-73-part-2-the-upgrade
http://www.attackmonkey.co.uk/blog/2015/12/upgrading-to-73-part-3-switching-to-razor
http://skrift.io/articles/archive/umbraco-upgrade-strategies/

Related

TYPO3 new version

I'm preparing myself to work with the new version of TYPO3 (v10), and I need clear documentation which presents the changes between the old and new version (especially disappear of ("switchableControllerActions")
So if anyone has an idea I'll be grateful
Thanks in advance
There always (for all major versions) are slides "What's new" and a search gives this page: https://typo3.org/help/documentation/whats-new
the other option is the change log / Release Notes for each bugfix version:
https://get.typo3.org/list/version/10
And all together in one page: https://docs.typo3.org/Home/WhatsNew.html
Apart from the answer given, I would recommend the Changelogs in any case. The "What's new Slides" do not contain all changes. The changelogs contain all relevant changes as each change in the core with a deprecation or breaking change must include a Changelog. Also, the Changelogs contain a migration path and tips that should be helpful for you.
I admit, it is a huge long list. So here are some additional tips:
Since you mention switchableControllerActions: For your own extensions, you can use the extension scanner to search for deprecated or breaking functionality in your extension before moving to the next version: In the backend: Upgrade > Scan Extension Files
Also, since TYPO3 9, you can view and check off the changelogs you already handled in the backend, see Upgrade > View Upgrade Documentation in the Backend.
If you want to find out about changes even earlier, you can follow the changes via one of these sources and read them as soon as they come out:
https://typo3.slack.com: channel #rst-updates
https://review.typo3.org and read the core patches and follow the discussions
twitter: https://twitter.com/t3git_master
What I am also sometimes missing is a table with comparison of old and new. But there are some good resources for specific things, such as:
migrating to "new" doctrine QueryBuilder from $GLOBALS['TYPO3_DB']
About the what / when / why of some particular changes: The changelog explains it quite well, including a migration path. What is sometimes missing is, why a change was made. There is also often some more information and discussions in the review on Gerrit. To find that, click on the link to the issue in the changelog and then find the link to the review (should start with https://review.typo3.org) in the history.

Can I use ag-grid's old tree data without the enterprise version?

I'd like to use ag-grid community in plain JS project, which could be commercial soon. I don't know much about license policies.
From documentation I could suggest that community library is stored here?
src="https://unpkg.com/ag-grid/dist/ag-grid.min.noStyle.js
Further, I'm intersted in Tree Data (Legacy) feature, which is free. But it's source library looks like:
src="https://unpkg.com/ag-grid-enterprise#18.1.1/dist/ag-grid-enterprise.min.js
Am I breaking the license rules using this feature? How should I use it correctly? What if I use enterprise lib in non-commercial project, would it work?
You can indeed use the old tree data implementation without the enterprise version, there's a quote I didn't notice before which sums it up:
https://www.ag-grid.com/javascript-grid-tree-data/
How Tree Data is managed in ag-Grid was changed in ag-Grid v14. This
page presents the new way of working with Tree Data. The old way was
part of ag-Grid free, the new way is part of ag-Grid Enterprise. The
old way is deprecated but you can still use it, but we will not be
enhancing it. For documentation on the older version of the grid prior
to v14 see Tree Data (Legacy).
In their demo of old tree data, the JavaScript file used should really be the "community" version instead of the enterprise one. They just use the enterprise version in all demos to make it easier.

RPGLE opcodes - operating systems compatibility

I'd like to know where to find a "table" that lets me know if a specific opcode is compatible with a specific version of the IBMi O.S.
Example:
LEAVESR introduced in V4R4
Is there anything like this?
This may be of use to you. This page is a list of operation codes available to the RPG compiler in IBM i 7.3. There is a dropdown towards the top that let's you select a different OS version.
This would allow you to compare operation codes between OS versions.
You can also use this What's New page to see every version back to V3R2.
I'm not aware of anything quite as specific as your question, but all elements are documented in a similar way in the ILE RPG Reference manual. The link is for ILE RPG for IBM i 7.3, but earlier releases have the same section according to the release. So, having just the latest gives you essentially the complete list of changes for all releases.
If you download a .PDF every few versions/releases, you can have a full history of "What's New" even if some future release truncates the section. If you think over the latest section, it should become clear that just having new op-codes isn't totally sufficient.

Activity stream missing after JIRA upgrade

I upgraded our JIRA from version 6 to version 6.1. Suddenly the Activity Streams are always empty. It is very annoying for the users who were very dependent on them. So I need to get the activity streams back.
What I have tried so far:
1. Reindexing
2. Creating a new widget for activity stream
What log can I look into to see what is broken? Do I need to create a new filter or something?
Please do not create activitystream-gadget.xml. Instead, remove the gadgets you have now and install the latest versions of each--including the Activity Stream gadget itself.
Please look at your atlassian-jira.log file.
Mostly this is caused by outdated plugins using deprecated (and now removed) classes. Similar thing happened to me when OSUser class was removed due to deprecation and an older plugin still used it.
If you are not able to view the log, try disabling user installed plugins.

TinyMCE upgrade an modified editor to the latest version mayhem

It is this sad moment to a developer's life that he has to maintain and fix legacy code... In my case I have to deal with a modified (core scripts) tinyMCE 3.2.2 which I have to update to the latest version in order to play in IE9+...
So my question is if there is a way to check which files have been changed since version 3.2.2 and try to update only those cause it is an overkill to check all the code for the modifications...
Thanks in advance
I fear there are so many changes in so many files that most of them have changed since then and in order to work with IE9.
If possible you should never ever modify the core code. Instead use custom plugins if possible.