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
  • fiber_manual_recordInstallation and Updates
  • south

folder_sharedSolve 2sxc Update Problems

  • homeChecklist Templates
  • south
  • fiber_manual_recordInstallation and Updates
  • south

folder_sharedSolve 2sxc Update Problems

Folders and checklists

  • check_circleCS1061: ToSic.Sxc.Blocks.IBlockBuilder
  • check_circleOlder 2sxc - Solve too many or too few content types found for the content-type App-Settings
  • check_circleRender Innercontent
  • check_circleSolve Edit UI - Field Configuration is Incomplete and should be fixed
  • check_circleSolve Error 500 after many 2sxc Updates
  • check_circleSolve Messed Up Languages / Translations after Update
  • check_circleSolve too many or too few content types found for the content-type App-Settings

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. 

In some cases when you update an old 2sxc site you may run into this error message in the UI for string-wysiwyg fields and probably also for custom-gps fields. 

Field Configuration is Incomplete and should be fixed

Cause

This is complicated and historic, so let's quickly explain.

  • Before 2sxc 10 the configuration for input-fields was stored in the SQL Database. In v10 we changed this to be JSON files but older installations still have the configuration stored
  • Normally the configuration was stored in App #1 which was not used except for system data. The default App which the first Content will get is normally #2
  • Now the rule in picking up Input-Field configurations is to check if the current App has any configurations (overriding the defaults or adding additional fields). Since normally App #2 has no configuration stored, it works. 
  • Now in rare cases installations which started very long ago put the Content in App #1. This doesn't usually matter, but in this case it will check and find a definition in the current App and prioritize it. 
  • Since the definition for string-wysiwyg changed for V10+, it's now missing data.

Verify this is your Issue

To verify that this is the cause, check that your call (F12) is actually trying to edit data on App #1:

Fixing this Issue

The goal is to deactivate the relevant settings in App 1. You could just remove all, but let's play safe. 

  1. Go to App Data and switch scopes to Fields
  2. Go to the Custom Input Type Configuration list
  3. Find the definition for string-wysiwyg and delete or edit it - like just add a few xxxs
    When multiple languages are installed delete it for sure.

Everything should now work. 

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/1yZjqy86
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.

Here you can see how this document is used and linked by other documents

Used in (0)

Others referencing this

Uses these (0)

Documents linked from this document

How it Behaves

How this document is categorized changes how it behaves.

This is a main document, it is listed normally and appears in search result.

Type

This is a Checklist. Lists are converted into checkboxes.

Get something to say?

Comment to start a discussion or make a note
send

please log on to chat

close

Durchsuche ganz Azing