|
|
-
KB10068: How to create a link selector programmatically
You can reuse an existing link selector (ManageLink) using a PageCall control and some tricks.
-
KB10065: List of the sites in top menu gets too long
You can list the sites in 3 columns with a simple CSS-modification.
-
KB10064: Does AxCMS.net produces XHTML-compatible pages?
AxCMS.net does not prevent you from creating XHTML compatible output.
-
KB10061: Customizing ReleaseOverview page in MS
Customizing ReleaseOverview requires a workaround, which is described in this article.
-
-
KB10048: Text looks in the text editor differently as in the preview mode
Put all the CSS formatting information into external CSS-files rather than directly into the template.
-
KB10047: Structure elements are shared between the pages on different sites, even if the users don’t have enough permissions
You could extend your structure elements with an additional parameter which makes the element instances unique to a particular site.
-
KB10046: How to get all users for a user group
Getting users of a group or groups for an user is done in similar way – through using AxUserAuthorizationAdapter class
-
KB10045: Publishing fails
If publishing fails, search for exception with additional information. You should also check check web.config - publishing configuration, file system permissions, max request size and request timeout.
-
KB10044: Changing type of the existing structure elements
If you change the type of a structure element from structural to static/dynamic in CmsSite.xml, current instances in the existing pages do not work as expected. To solve it you need to update them in the DB manually (AxStructureElement-table).
-
KB10043: AxLanguage translation does not work in Live System
If translations do not appear in live system, chances are high, that some configuration is missing.
-
KB10037: Exception: Object reference not set to an instance of an object
This is the most often exception encountered.
-
KB10036: ASP.NET Validator Controls do not work on the client in FireFox
Due to the htmlConformance=Legacy ASP.NET Validator Controls do not work on the client side in FireFox.
-
KB10035: Categories out of sync
There are some cases when categories are out of sync. DB state and application state or MS vs LS.
-
KB10034: How to update the Sequence if creating new keys manually
If you are creating new objects with keys in the database manually don't forget to change the sequence tables accordingly.
-
KB10033: How to reset the version history
How to delete previously created versions of the pages and/or documents if you want to reset the history.
-
KB10032: Problems with Database Connections
This is the case when database connection is interrupted while trying to connect to the database.
-
KB10028: Error while publishing: Not all content elements are checked in
If a developer removes placeholders without first checking the content in such placeholders, an error while publishing may occur.
-
KB10025: Invalid column errors on Language Overview page
The Date and URL columns only exists for the default language and an error occurs while using another language
-
KB10016: Parser error loading a template
Parser error is thrownbecause of the templates .dll-s are not in the right folders.
-
KB10014: System.ServiceModel.CommunicationException
Usually indicates a problem in communication between client (Silverlight ribbon control) and server (Concept.svc WCF service).
-
KB10013: CreateApplication throws PRIMARY KEY violation during member import
If PRIMARY KEY violation exception occurs during member import
-
KB10010: Page.Header is not accessible from a Custom Editor for a Structure Element
If you try to access Page.Header, you cannot add anything to the Head-element of the ASPX-page, because In the Management System of AxCMS.net a master page approach is in use
-
KB10009: ArgumentException: , hexadecimal value , is an invalid character
when calling WebQueryService
-
KB10008: System.InvalidOperationException: Timeout expired
when using AuthenticationModule for protecting documents
-
KB10004: *.aspx not found when using asynchronous postbacks
"Page not found" error after asynchronous postback result when using ASP.NET AJAX on AxCMS
-
KB10003: "The page cannot be found" error returned by ASP.NET
If no AxCMS httpHandler in web.config is defined or httpHandler extension differs from actually used
|