menu
Logo
  • Why azing?
  • Blog
  • Help
ENarrow_drop_down
  • DE
  • EN
Suche in Checklisten
search
azing Logo ENarrow_drop_down
  • DE
  • EN
  • Why azing?
  • Help
2sxc
drive_folder_upload
  • homeChecklist Templates
  • south

folder_sharedTrash

  • homeChecklist Templates
  • south

folder_sharedTrash

Folders and checklists

  • folder_sharedApp Auto-Installer
  • folder_sharedApp: Slider
  • folder_sharedDeveloping with Content Types
  • folder_sharedDnn-Sxc-Angular 10
  • folder_sharedJS: Enable CORS in DNN/2sxc for local development
  • folder_sharedPro: Content Migration / Update
  • check_circleAdd a new wiki documentation
  • check_circleApp: Image Hotspots
  • check_circleBuild Custom Styles for a Standard 2sxc App [todo: Aaron]
  • infoGo To: App - Administration
  • infoGo to: App - Data
  • check_circleHow to analyze Issues on Websites like DNN (2illumin8)
  • check_circleImportant Release (major version / feature)
  • check_circlePrepare existing Content-App for Upgrading to Standard Content-App
  • check_circleSelect Content Effects TODO

Parts (0) expand_more

These are small document-parts which are used in other documents. They are not a starting point for any real activity. Because of this, they will be listed further down and the search will not list them unless requested. 

Basics

  1. Create a copy of your site, and only work on that

Prepare Templates

  1. Move all templates in the main folder into a subfolder "old"
  2. Adjust all view-configurations to point to the new location
  3. test the website to verify everything still works

Prepare Content-Types you want to Drop

  1. Add OLD to the front of the shown name so it's easy to spot these in the list

Prepare Content-Types you want to Upgrade

Do this only for the content-types which have a lot of data and which you want to keep in this schema. Don't do this for content-types whose data you'll manually copy paste anyhow.

  1. Verify the static name is the same as the static name of the upgrade you'll add later on (this may be very technical, make sure you know what you're doing)
    1. If the static name does not correspond, rename the old content type on the existing installation
    2. After changing the content type static name, re-assign the content type for all templates
  2. Review the field names of the old / new schema, and rename the old field names to match the new fields for import
    1. This will probably require that you also adjust the old templates to use the changed field names
  3. Verify everything still works

 

Logo
Legal | Content Copyright CC-BY 4.0
bug_reportReport Bug
  • info
  • Links
  • Permissions
code Share
code
URL copied to clipboard.
Embed Checklist close
Copy Copy
Content Copyright

CC-BY 4.0

Translations

None

2sxc - Content Management for DNN & Oqtane Logo

2sxc - Content Management for DNN & Oqtane

QR-Code
azing.org/2sxc/r/dxmzf45Q
View & Use

Public (can be used by everybody)

Edit & Admin

Default (all members can edit)

This catalog has a simple permission model, where all members have the same permissions. For advanced permissions, upgrade to Enterprise.

Get something to say?

Comment to start a discussion or make a note
send

please log on to chat

close

Durchsuche ganz Azing