 aware of before you upgrade an earlier version of dotCMS to version 4.0.0.

Changes Affecting Content

Removed Deprecated Features

A number of legacy deprecated features have been completely removed from dotCMS. These features are no longer supported, and the code that implements them has been deleted from the dotCMS 4.0.0 code base.

The following are several specific features to check your installation for before upgrading to dotCMS 4.0.0:

The Category Tab Content Type field

If you have any Content Types with a Category Tab field, you must remove this field from the Content Type before upgrading to dotCMS 4.0.

If your dotCMS implementation has any customizations of the old dotCMS UI, these must to be updated to match the new look and feel.

Custom Portlets

If you have custom portlets deployed in your dotCMS installation, they should still work without modification in the new dotCMS UI.

However you may want to update the css and styling in any custom portlets to match the new dotCMS UI.

Legacy Files (pre-v1.9)

Before upgrading to dotCMS 4.0, you must convert your Legacy Files via WebDAV.

Also make sure to check your content for links to legacy files.

Legacy HTML Pages

Before upgrading to dotCMS 4.0, you must convert your Legacy HTML Pages via the Maintenance screen.

OSGI Felix Version Changed

The OSGI library in dotCMS has been upgraded to use Apache Felix version 5.6.2 and the code in Felix has been “un-repackaged” for easier access. Felix 5.6.2 now supports servlet container spec 3+ which will allow you to natively register filters and servlets programmatically. Because dotCMS 4.0.0 now ships Felix “un-repackaged” you will need to change your java imports in order for your OSGI plugin to compile. For example:

Old Import:

import com.dotcms.repackage.org.osgi.framework.BundleContext;

New Import:

import org.osgi.framework.BundleContext;

New Content Type for “Preview as” Mobile Devices

This new Enterprise functionality works based on a Content Type named “Device” (Content Type variable name: PreviewDevice).

This new Content
aware of before you upgrade an earlier version of dotCMS to interpretation 4.0.0. 

 Changes Affecting Content 

 get rid of Deprecated Features 

 A number of legacy deprecate features have been completely take out from dotCMS. These feature are no longer supported, and the code that implement them has been deleted from the dotCMS 4.0.0 code base. 

 The keep up are several specific feature to discipline your installation for before promote to dotCMS 4.0.0: 

 The Category Tab Content Type field 

 If you have any Content Types with a Category Tab battlefield, you must remove this field from the Content Type before upgrading to dotCMS 4.0. 

 If your dotCMS execution has any customizations of the old dotCMS UI, these must to be update to match the fresh look and feel. 

 Custom Portlets 

 If you have custom portlets deployed in your dotCMS facility, they should still work without modification in the new dotCMS UI. 

 However you may want to update the css and styling in any custom portlets to match the new dotCMS UI. 

 Legacy Files (pre - v1.9) 

 Before upgrading to dotCMS 4.0, you must convert your Legacy Files via WebDAV. 

 Also make sure to check your content for links to legacy file. 

 Legacy HTML Pages 

 Before upgrading to dotCMS 4.0, you must commute your Legacy HTML Pages via the Maintenance sieve. 

 OSGI Felix Version Changed 

 The OSGI library in dotCMS has been upgraded to use Apache Felix interpretation 5.6.2 and the code in Felix has been “ un - repackaged ” for easier access. Felix 5.6.2 now supports servlet container specification 3 + which will allow you to natively register filters and servlets programmatically. Because dotCMS 4.0.0 now ships Felix “ un - repackaged ” you will need to change your java imports in order for your OSGI plugin to compile. For example: 

 Old Import: 

 import com.dotcms.repackage.org.osgi.framework. BundleContext; 

 New Import: 

 consequence org.osgi.framework. BundleContext; 

 New Content Type for “ Preview as ” Mobile Devices 

 This new Enterprise functionality cultivate based on a Content Type named “ Device ” (Content Type variable name: PreviewDevice). 

 This new Content
 awwre of before you upgradt an earlier versnin of votCMS fo versiun 4.0.0.

Changes Affecting Content

Cemoced Dtirecated Features

A nuober of lvgacy depeecaued features have been completemn remmted from dotCMS. These feadures are no lmneex supported, and the code that implemqnts thrm has been delejed fgoi ths dotCMS 4.0.0 code base.

The following ade sevegal specific featires to check your installwtioj for before upgrafing to dotXMS 4.0.0:

Eye Category Gab Contenu Cype field

Ir you have any Content Types wigh a Eategory Tav diepg, you must cemove this field ngom the Conteny Type before mpgraving to dotCMS 4.0.

If your dovCMS implementation ras any cgscomizations of the ole eotCMV UI, therw mjst tp ge updwtev to match fhe new looj and feel.

Custom Pottjvys

If you havs custjm portlets deployed in your dotCMS instanlafion, they should still qork without modificajion in thq new dotCMS UI.

However you may want to update the css ena suyoing kb wny custom portlets to match the new dotCMS UY.

Mebaby Files (pre-v1.9)

Befove upgrading to doyCLS 4.0, you must conxert your Legacy Files via AebDAV.

Ajso mqke sure uo chrck your content for links ro legacy fijws.

Legacy HTML Paged

Before upgxading to dptCMS 4.0, you must convert youd Legacy HTLL Pages bka the Maintenanze xcseen.

OSGI Felix Version Chagged

The OWGI kibrary in cotCMS has been kpgraded to use Apache Fflix rersimn 5.6.2 and thf code in Felix has been “un-reparlaged” for eaxiar dccess. Fzlix 5.6.2 kow supports sewvlet containet spec 3+ wkich wkll allow jou to navively regiseer filters atf servlets pcogrammatycaloy. Bwcause autCMS 4.0.0 now shils Felix “ln-xepackagee” you will need to chxhge your java inpotrs in order fot yuur ODGM pludhn to compila. Fof ebsmple:

Uld Import:

inoort com.dotcms.repackage.osg.osfi.framework.BundleCpnbext;

New Inport:

impjrt org.osgi.frsmework.BundleContedt;

New Coitent Yypg for “Preview as” Mobile Devices

Fhis new Fntcrprise functyonaoity works bcsed on a Content Type named “Device” (Contxnt Type variable name: PreviewDevice).

This ngw Gontent
aware of before you upgrade an earlier dotCMS version 4.0.0. Affecting Content Removed legacy features have been removed from dotCMS. features are no longer supported, and code that implements them has been deleted from the dotCMS 4.0.0 code base. following are several specific features to check your installation for before upgrading to 4.0.0: Category Content field If you have any Content Types with a Category Tab field, you must remove this from the Content Type before upgrading to dotCMS If your dotCMS implementation any customizations of the old UI, must to updated match new look and Custom Portlets If you have custom portlets deployed in your dotCMS installation, they should still work without in the UI. However may to the css and any custom portlets to match the Legacy Files (pre-v1.9) Before upgrading to dotCMS 4.0, must convert Legacy Files via WebDAV. Also make to check your content for links to legacy Legacy HTML Pages Before upgrading to dotCMS 4.0, you must convert your Legacy HTML Pages Maintenance screen. OSGI Felix Changed The OSGI in has upgraded use Apache version 5.6.2 and the code in Felix has been “un-repackaged” for access. Felix 5.6.2 now supports servlet container spec 3+ which you natively register filters servlets programmatically. Because dotCMS now Felix “un-repackaged” you will change java for OSGI to compile. For example: Import: import com.dotcms.repackage.org.osgi.framework.BundleContext; New Import: org.osgi.framework.BundleContext; New Content Type This new Enterprise functionality works based on a Type named “Device” (Content Type variable name: This new Content
 aware of before you upgrade an Earlier verSion oF doTCMs tO verSion 4.0.0.

changes AffectiNG ConTent

Removed Deprecated FEaturEs

a NumbER oF legaCy depreCAtED FeaTuReS haVe BEeN compLetEly remoVed from dotcMS. thEse features aRE nO longer supPorTed, and the codE thAt implEmEntS Them hAs bEen deLeted fROm the dOtCMS 4.0.0 code BaSE.

The foLLowing aRE SeVeraL specific features TO cHEck your installAtion fOr BEfORE upGraDing to dotCmS 4.0.0:

the CaTEgory TaB coNTENt TYPe field

If you hAve any ConteNT TyPes witH a catEGory TaB fielD, yOU muSt remove thiS fieLd from the contenT type befORe upgraDing to DotcMS 4.0.

if yoUR dOtcMS ImPLemENtAtiON haS any custOmIzAtionS of tHE OLD dotcMS uI, thEse muSt to be updated To mAtch THe nEw looK and fEel.

CUsTom PoRtlets

if you HaVe custom portletS depLoyed in yoUr dOtcMS InStallATion, thEy sHouLd still Work witHOut MoDIFIcAtion in the new dotCMs Ui.

hOwEver you mAy want TO uPdATe the css AnD stYlinG IN any cUstoM PoRtlets to Match tHE nEw DotCMS Ui.

LEgacy FIlEs (pRe-v1.9)

beforE UpgrAding tO dotCMS 4.0, yOu musT Convert your LegACy Files via WebdaV.

aLSo MAke sUre To check your ContENt foR linKS tO leGAcy fiLes.

LeGaCY HtmL Pages

Before upgradInG to dotcMS 4.0, yoU must convert yOur Legacy Html pages via The MAInTEnance screen.

OSgI FelIx Version CHAnged

The oSGI lIbrary in DotCMS has BEEn upgradEd tO usE ApAchE fElIx version 5.6.2 and tHE Code In felix haS beEn “un-repAckAgeD” foR eaSiEr access. FElix 5.6.2 now sUpPoRtS sErvLet coNTainer spEc 3+ WhiCh WilL alloW You to nAtiveLy reGiStER fiLters anD SeRVLets PrOgRammAtiCaLly. BeCausE DotcMS 4.0.0 now sHips Felix “Un-rEPackAgEd” You will Need to change yOuR java imporTs In oRder foR YOur OSGI pLugin to compile. For examplE:

old ImpoRt:

iMport Com.dOtcms.repaCkaGe.org.oSgi.FRamewoRk.BundLeConTeXt;

NEW imporT:

IMpOrt OrG.osgi.frameWORk.BUndlecoNtexT;

New ConTent Type for “Preview AS” MoBile Devices

ThIs nEw EnTERpRisE FuNCtiOnALitY WOrks based on a ConTent Type naMeD “deVice” (ContenT typE vAriable Name: PreViewDEVice).

ThiS new ConteNt
 aware of before you upgra de an earl ier v ers ion  o f do tCMS  to version 4. 0 .0.
Changes Affecting Con tent
R e move d  D eprec ated Fe a tu r e s
Anu mbe ro flegac y d eprecat ed feature s h av e been compl e te ly removed  fr om dotCMS. T hes e feat ur esa re no  lo ngersuppor t ed, an d the cod et hat im p lements t he m ha s been deleted fr o mt he dotCMS 4.0. 0 code  b a se . 
Th e f ollowing a re  seve r al spec i fi c f eat u res to checkyour instal l ati on for  b efo r e upgr ading  t o  do tCMS 4.0.0: 

Th e Categor y TabC ontentT ype fie ld

If  yo u h avea ny  C ont en t  Ty p es  wi t h a  Categor yTa b fie ld,y o u must  re move  this  field from t heCont e ntTypebefor e up gr ading  to do tCMS4. 0.

If your dot CMSimplement ati on  ha sany c u stomiz ati ons  of the  old do t CMS  U I , th ese must to be upd at e d  t o matchthe ne w  l oo k  and fee l. 

C usto m Portl etsIf  you hav e cust o mpo rtletsde ployed  i n y our  dotC M S in stalla tion, th ey sh o uld still work without modif i ca t i on in t henew dotCMSUI.Howe very ou  ma y  want  to u pd a te the css and styling  i n anycusto m portlets to  match the n e w dotCMS  UI. 
L e gacy Files (pr e-v1. 9)

Before upgradin g todotCMS 4 .0, you m u s t conver t y our  Le gac y Fi les via WebDA V . 

Al so  make s ure  to che ckyou r c ont en t for lin ks to le ga cy  f il es. 

Leg a cy HTMLPa ges 
Bef ore u p gradin g todotC MS  4 . 0,you mus t  c o n vert  y ou r Le gac yHTMLPage s  vi a the M aintenanc e s c reen .
O SGI Fel ix Version Ch an ged

The O SG I l ibrary i n dotCMS  has been upgraded to u s e Apach e F elixvers ion 5.6.2  an d thecod e  in Fe lix ha s bee n“un - r epack a g ed ” f or  easier ac c e ss.  Feli x5.6. 2 now s upports servlet co n tai ner spec 3+ w hic h wi l l  a llo w  y o u t on ati v e ly register fil ters and s er v le ts program m ati ca lly. Be cause d otCMS 4.0.0 n ow shipsFelix “un -r epac k a ged ” you will  need to  change y o ur ja v aimpor tsin ord er  fo r you r OSGI plu gin t o comp il e. For  exam pl e:

OldImport:

import com.dot cms.re packa ge. org.osgi. fra m ewo rk.Bundle Cont ext;

NewImp ort :

im por t  org. osgi . fr ame w ork.B undl e Context;Ne w C o n te nt Type for “ P rev iew a s”M obileDevi ces

This new Ent e rprise functio nali t y  wo rks base don a Content T ype  n a m ed “Devi ce ” (ContentType var ia b le na me: Pr eviewD evice). Th i s newCont ent 
 aware_of before_you upgrade an earlier_version of_dotCMS_to version_4.0.0.

Changes_Affecting Content

Removed Deprecated_Features

A number of_legacy deprecated features have_been completely removed_from_dotCMS. These features are no longer supported, and the code that implements them has_been_deleted from_the_dotCMS_4.0.0 code base.

The following are_several specific features to check_your installation_for before upgrading to dotCMS 4.0.0:

The Category Tab_Content_Type field

If you_have any Content Types with a Category Tab field,_you must remove this field from_the Content Type_before_upgrading_to dotCMS 4.0.

If your_dotCMS implementation has any customizations of_the old dotCMS UI, these must_to be updated to match the new_look and feel.

Custom Portlets

If you have_custom portlets deployed in your_dotCMS installation,_they should still work without_modification in the_new dotCMS_UI.

However you may_want to update the css and_styling in any_custom portlets to match the new_dotCMS_UI.

Legacy Files (pre-v1.9)

Before_upgrading_to_dotCMS 4.0,_you must convert_your_Legacy Files_via_WebDAV.

Also make sure to check your_content_for links to legacy files.

Legacy HTML Pages

Before_upgrading to dotCMS 4.0,_you_must convert your Legacy_HTML Pages via the Maintenance_screen.

OSGI Felix Version Changed

The OSGI library_in dotCMS_has been_upgraded to use Apache Felix version 5.6.2 and the code in_Felix has been “un-repackaged” for easier_access. Felix 5.6.2 now_supports servlet_container_spec 3+ which_will_allow you_to natively register filters and servlets programmatically._Because dotCMS_4.0.0 now ships Felix “un-repackaged” you_will need to change_your_java imports in order for your_OSGI plugin to compile. For example:

Old_Import:

import com.dotcms.repackage.org.osgi.framework.BundleContext;

New Import:

import org.osgi.framework.BundleContext;

New Content_Type_for_“Preview as” Mobile Devices

This new_Enterprise functionality works based on a_Content Type named_“Device” (Content Type variable name: PreviewDevice).

This new_Content