Fork me on GitHub
2sxc 9.33 for DNN 7 to 9
Website Builder, Content Manager, App-System: open-source and amazing
You are here: Home  >  Docs  >  Feature

Breaking Changes in all Versions

Introduced in Version

2sxc has very few breaking changes - our philosophy is as follows:

  1. Plan ahead, do things as well as possible to prevent breaking changes
  2. If we do introduce breaking changes, then only on large-version-numbers (so from 6.x to 7.0)
  3. New features, which are still prone to changes, are hidden or communicated as beta-features. These are not stable and can easily change. Once we officially communicate them, they can be regarded as stable. 
  4. Internal API - like mechanisms in the EAV - count as internal and can easily change, but should not affect the users. 

So when we do introduce breaking changes, we do so because we really believe we have to get rid of a bad idea from the past or fix something. When we do this, we still try to minimize your impact. But if it is necessary you should find it documented here. 

 

Breaking Changes in 2sxc 7.0

 

Breaking Changes in the EAV

Note that if you programmed with interfaces, the way we usually create our samples (like ToSic.Eav.IEntity) everything should work and you should not be affected by these changes. We moved a few object-types into other namespaces. In 99.9% of all cases you never referenced these - so you shouldn't be affected. But if you are, these are the ones we moved:
  1. ToSic.Eav.EntityModel is now ToSic.Eav.Data.Entity
  2. ToSic.Eav.AttributeBaseModel is now ToSic.Eav.Data.AttributeBase
  3. ToSic.Eav.AttributeDefinition was removed as it's not needed
  4. ToSic.Eav.AttributeModel is now ToSic.Eav.Data.Attribute
  5. ToSic.Eav.AttributeModel<t> is now ToSic.Eav.Data.Attribute<T>
  6. ToSic.Eav.AttributeWithMetaInfo is now ToSic.Eav.Data.AttributeWithMetaInfo
  7. ToSic.Eav.EntityRelationshipModel is now ToSic.Eav.Data.EntityRelationship
  8. ToSic.Eav.ContentType is now ToSic.Eav.Data.ContentType
  9. ToSic.Eav.ValueModel is now ToSic.Eav.Data.Value
  10. ToSic.Eav.ValueModel<T> is now ToSic.Eav.Data.Value<T>
  11. ToSic.Eav.TypeValue<T> is now ToSic.Eav.Data.TypeValue<T>
  12. ToSic.Eav.ValueViewModel was removed
  13. ToSic.Eav.DimensionModel is now ToSic.Eav.Data.Dimension
  14. ToSic.Eav.ZoneModel is now ToSic.Eav.Data.Zone
  15. ToSic.Eav.AttributeMoveDirection was moved
  16. ToSic.Eav.AttributeScope was moved

 

Breaking Changes in the Token Engine

We did not introduce breaking changes that we are aware of. We now recommend using the newer syntax as follows, but the old syntax will still work:
  • Prefer [Content:Presentation:Color] to [Presentation:Color]
  • Prefer <repeat repeat="Content in Data:Default"> to <repeat>
  • Note that in general, tokens are now less case-sensitive than before, which may have side-effects when a token didn't work previously, but works now.

Breaking Changes in the Razor Engine

We improved / changed a few things but these should not affect you. If they do - here are the things we're aware of which may surprise or cause side-effects:

  1. The Content-object now offers a property called Presentation - so that you can loop through Content (like foreach(var Book in AsDynamic(Data["Default")) { @Content.Presentation }. This new feature could cause a side-effect if you had a field called "Presentation" within your content-item. 
  2. The Data.In / Data.Out used to have 4 streams by default - Default, Presentation, ListContent, ListPresentation. Since the presentation is now supplied by the Content-object, we optimized the streams and only deliver 2 streams by default: Default and ListContent. This does not affect normal templates or loops, but if you were specifically accessing the Presentation-stream (Data["Presentation"]) and not the Presentation object @Presentation, this may affect you.

     

Breaking Changes in the JavaScript API

None that we are aware of. 

Breaking Changes in the Database Structure

We moved all data in the tables ToSIC_SexyContent_ContentGroupItems and ToSIC_SexyContent_Templates into EAV content-items. This should not affect you, as you should not access these tables in your code. 

Breaking Changes in Import/Export

None that we are aware of.

Breaking Changes in Previously Hidden Features

  1. The Visual Query Designer existed in previous versions but we had to change some features. Because of this, previously created Queries will not work - please just create them again. 
  2. The data-export / import was a hidden, undocumented feature. Some aspects have changed, especially the placeholders for "empty" or "not translated"

Tags for this feature