1. |
- Centralpoint Module Gallery
- Development Tools (Utilities), Content Management, Knowledge Management, Search Engine Optimization, User Experience
- Everyone: All Users
- 1/14/2013
- Relevance: 400
-
-
12/31/9999 11:59:59 PM
-
Centralpoint, Oxcyon, Gartner, Magic Quadrant, MQ, Digital Experience, Portal, SSO, SAML, AD, Data Migraiton, Document Management, Metadata, Taxonomy, Enterprsie Content Management, Knowledge Management, metadata,ontology,intranet,portal,transformation,Artificial Intelligence,aggregation
-
URL Rewrite permits Web administrators to easily replace the URLs generated by a Web application in the response HTML with a more user friendly and search engine friendly equivalent. Links can be modified in the HTML markup generated by a Web application behind a reverse proxy. URL Rewrite makes things easier for outbound response content and headers rewriting with outbound rewrite rules that work with HTTP request and response headers and with IIS server variables.
You will want to upload an Excel spreadsheet here which must contain the following fields (URL and SystemName columns). In order to see the template file for what your upload should like, you can download it here.
, This tool can be found under the Development section within the Client Console, under 'Utilities'. Log in the Client Console, click on development, and search for this tool within this page. You can also ask your production manager to turn on the 'Tools' section of your client console. When this is done, each tool will appear individually within the console, for easy access.
-
-
-
-
-
-
-
2/19/2024 12:08:29 PM
-
https://qc.xoprod20.com/Uploads/Public/Centralpoint_Oxcyon_DevelopmentUtilities.jpg
-
|
2. |
- Centralpoint Module Gallery
- Information Architecture
- Everyone: All Users
- 8/15/2017
- Relevance: 61
-
-
12/31/9999 11:59:59 PM
-
Centralpoint, Oxcyon, Gartner, Magic Quadrant, MQ, Digital Experience, Portal, SSO, SAML, AD, Data Migraiton, Document Management, Metadata, Taxonomy, Enterprsie Content Management, Knowledge Management, metadata,ontology,intranet,portal,transformation,Artificial Intelligence,aggregation
-
This advanced module developed for IT and Developer personnel empowers you to configure query string and url schemas around your needs. This module gives you control over the rules which govern the URL strings created by your site. This is often required for multi site management, print friendly marketing campaigns and even search engine optimization.
-
This module was designed for technically savvy administrators only. The powerful rule based engine can lead to difficult to understand configurations and potentially break existing URLs. Some common difficulties and pitfalls include:
- All relevant routes are checked with every page load. Adding a large number of records to this module could affect the load time of every page in the site because the HttpModule executes on every page load and must check each route. URL generation is also executed multiple times per page load and a large number of complicated patterns may affect the performance of this feature. This is not an alternative to Admin > Error Messages/Redirects > Type = 404 Redirect. 404 Redirects are designed for migrating old dead URLs to new URLs and they are optimized to do that efficiently. Friendly URLs is designed for routing and generating the URLs of existing pages.
- Domain and Audience routing requires a Navigation or Document route. Domain and audience routes won't apply if the Routing module property is set to Fallback mode and the navigation and document portion of the path is not routed. The "System: Extension-Less URLs with Fallback Routing" record was designed to route all standard Centralpoint navigation and document paths. Enabling this record or restoring it to it's original values will typically resolve this problem.
- Routing is executed in the following order: Domain, Audience, and then Navigation & Document. If two records have the same order the newer record will be tested first. A preferred URL is chosen when building a URL in a slightly different way. When a document URL is being built records with specific documents selected will be tested first, and when a navigation url is built records with specific navigation items selected will be tested first. Records with no navigation item will always execute after those with specified values.
- Only managed (ASP.NET served) requests are supported by default. If you wish to route non-managed requests like .htm, .css, or .custom extensions you must set run AllManagedModulesForAllRequests to true in the Root/Web.Config. This will cause all HttpModules, regardless of their preCondition attribute setting, to fire on all requests which could lead to performance problems and unexpected behaviors.
- Conflicts may occur with the IIS URL Rewrite module. Similar redirects set up in the web.config or IIS could cause issues or even infinite loops. They should be removed from the web.config when they are added to this module.
- Permanent redirects are cached at many levels. When the Redirection module property is set to enabled and Enable Permanent Redirection Cache is set to Yes the browser and proxies will cache the redirection. If the preferred URL is changed later it may lead to 404 errors until browser cache is cleared.
- Changing URLs can lead to SEO problems. If the site has already been indexed by search engines you must ensure that the indexed URLs resolve properly including the appropriate canonical URL meta tags or redirect to the correct URL.
- Domain routing skips Default.aspx. If the site is using features that require the domain to redirect to Default.aspx then you cannot enable records with Type = "Domain." Domain routing automatically loads the the Default Path without the redirect to Default.aspx and then to the default path. The most commonly used features that require Default.aspx and are incompatible with Type = "Domain" are Admin > URL Redirect to Audiences and Admin > IP Manager > Action = "Redirect".
Utilizing this module typically involves creating or enabling a record and testing the route and URL generation then testing all other routes to make sure they weren't negatively affected. It is highly recommended that you set up and test one record at a time being sure to include the test URLs in the Test URLs attribute. A unique Notes attribute will display for each Type selection which explains how to configure that type for routing and generation. By default all system pages will generate a canonical URL meta tag when the page is loaded on a non-preferred URL, but the Redirection module property can be enabled to redirect to the preferred URL instead. You can use the Friendly URLs module to perform many URL manipulation tasks, some of which include:
- Supporting extensionless URLs. Enable the "System: Extensionless URLs with Fallback Routing" record to route and generate system URLs without the extension (.aspx). The legacy urls (including .aspx) will still be supported. If a hardcoded URL is accessed with the extension it will render normally including a canonical URL meta tag pointing to the preferred (extensionless) version of the URL. The path to all records will exclude the extension: /aud/nav or /aud/nav/doc.
- Enforcing all lowercase URLs. Enable the "System: Extensionless URLs with Fallback Routing" record, add .aspx to the Preferred URL if you'd prefer to keep the extensions ({smi}{doc}.aspx), and set Admin > Properties > Web Site Generated URL Casing to "Lowered". If a hardcoded URL is accessed in a different casing it will render normally including a canonical URL meta tag pointing to the correct casing. Set the Redirection module property to "Case Sensitive (Enabled)" to force a permanent redirection to the correct URL and casing.
- Supporting pathless audience homepages. Enable the "System: Pathless Audiences" record to route and generate system URLs that point to audience homepages without the homepage system name or extension. If a hardcoded URL is accessed with the homepage in the URL it will render normally including a canonical URL meta tag pointing to the preferred audience URL. This record will automatically utilize Site Architecture > Homepages > SystemName = "Home" for all audiences. If all audiences do not utilize this homepage you must create separate records for each audience/homepage combination. The path to all audiences will exclude the homepage: /aud.
- Supporting pathless domain homepages. Enable the "System: Pathless Domains" record and make sure that the Default Path and Navigation relate to the homepage of the Main audience to route and generate system URLs that point to the main audience home page without the audience or home page system name or extension. If a hardcoded URL is accessed with the audience and homepage in the URL it will render normally including a canonical URL meta tag pointing to the domain only. Set the Default Path and Navigation attributes accordingly to use a different homepage. The domain alone will render the main audience home page: /.
- Changing the audience system name. Create a new record with Type = "Audience", set the Pattern to the new audience system name supporting an optional trailing slash (custom-aud/?), set the Default Path to the home page portion of the URL (home), set the Preferred URL to the new audience system name (custom-aud), select the homepage under Navigation, and select a single Audience. You may also want to change the Order to 95 if you want to the "System: Pathless Domains" record to execute first.
- Changing the path to a document. Create a new record with Type = "Document", set the Pattern to the new path supporting an optional trailing slash (custom/doc/?), set the Preferred URL to the document path (custom/doc), select the Navigation, and select the Document. The selected navigation must have a page type of module and its module must include the selected document. The path will still contain the audience system name unless you have configured an audience specific domain: /aud/custom/doc.
- Changing the path to an HTML page. Create a new record with Type = "Navigation", set the Pattern to the path supporting an optional trailing slash (custom/nav/?), set the Preferred URL to the navigation path (custom/nav), and select the Navigation. The path will still contain the audience system name unless you have configured an audience specific domain: /aud/custom/nav.
- Changing the path to a module. Create a new record with Type = "Navigation", set the Pattern to the path including {doc} and supporting an optional trailing slash (custom/module{doc}/?), set the Preferred URL to the navigation path including {doc} (custom/module{doc}), and select the Navigation. The path will still contain the audience system name unless you have configured an audience specific domain: /aud/custom/module or /aud/custom/module/doc.
- Using a custom extension instead of ASPX. Open the site's Root/Web.Config file and set runAllManagedModulesForAllRequests attribute to "true" in configuration/system.webServer/modules. This will cause all HttpModules, regardless of their preCondition attribute setting, to fire on all requests which could lead to performance problems and unexpected behaviors. Disable the "System: Extensionless URLs with Fallback Routing" because this new record will handle all system URLs. Create a new record with Type = "Navigation", set the Pattern to include the custom extension ({smi}{doc}\.custom), set the Preferred URL to include the custom extension ({smi}{doc}.custom), and select All Site Map Items under Navigation. The path to all records will end in the custom extension (.custom): /aud.custom, /aud/nav.custom, or /aud/nav/doc.custom.
- Configuring an audience specific domain.Create a new record with Type = "Domain", set the Pattern to the audience specific domain (www\.yourdomain\.com), set the Default Path to the homepage portion of the URL (home), set the Preferred URL to the audience specific domain (www.yourdomain.com), select the homepage under Navigation, and select a single Audience to generate fully qualified URLs in canonical URL meta tags using your audience specific domain. By default audience specific domains do not support or generate the audience system name in the URL. If your site contains hardcoded URLs which include the audience system name they will return 404 errors which will be detected automatically by the error handler and redirected to the same URL without the audience system name regardless of the selection in the Redirection module property. If you would prefer to maintain the audience system name in the URL it should be included in the Default Path (main/home).
- Configuring a preferred domain. Create a new record with Type = "Domain", set the Pattern to catch all potential domains (.*), set the Preferred URL to your preferred domain (www.yourdomain.com), and select the related Audiences to generate fully qualified URLs in canonical URL meta tags using your preferred domain.
- Requiring HTTPS on a specific domain. Create a new record with Type = "Domain", set the Pattern to catch all potential domains (www\.yourdomain\.com), and select Yes under Requires HTTPS to generate fully qualified URLs in canonical URL meta tags using your preferred scheme. Set the Redirection module property to "Enabled" to force a permanent redirection to the correct scheme.
-
-
-
-
-
-
2/19/2024 12:10:19 PM
-
https://qc.xoprod20.com/Uploads/Public/MobileIcons/Centralpoint_Oxcyon_Digital_Experience_Platform_Friendly_URL.jpg
-
|
3. |
- Centralpoint Update History
- Everyone: All Users
- 11/2/2009
- Relevance: 44
-
-
12/31/9999 11:59:59 PM
-
Centralpoint Updates, Centralpoint Version, Oxcyon Release, Centralpoint Release, Digital Experience, Magic Quadrant, ECM, Content Management, Portal, Enterprise, User Experience, MDM, Master Data Management, Gartner
-
-
- The standard file upload popup window has been enhanced with light security. This allows its use in forms management, but prevents its use when the opener is not the same page or JavaScript is disabled. This page and all other integrations are also no longer accessible to robots.
- The URL rewriting HttpModule used on the front end of the site has been updated to support a query string variable (rewrite=no) to prevent rewrites. It also does not rewrite URLs when the first directory exists in the file system, even if that directory is also the system name of an audience. The Site Architecture > Audiences module now validates the System Name attribute to ensure that you do not create an audience where the system name is equal to the name of a folder at the root of the site.
- A bug in the sync process related to the Console folder has been repaired. Previously, changes made to non-synchronized files and sub-folders would be synchronized if the files had been modified in the parent site. This caused changes submitted in the Admin > RTF Editor module to be lost after a sync that occurred after changes were made to this module in the parent site. This problem will not be officially repaired until version 8.0.24.
- A new utility called “SQL Non-Query” has been added to Master > Development > Utilities. This utility allows us to execute non-query SQL statements on one or more database within a master with a single button click. This is commonly used for debugging and situation resolution. It is a non-reversible, highly technical utility that should only be used by experienced Centralpoint developers.
- A bug in the Roles and Users modules has been repaired that caused the checkboxes displayed on the grid views to return an error when clicked.
- A bug in the login form has been repaired that caused the enter key press event to submit the search instead of the login form when the search occurred before the login form on the page and used an image button for submission.
- The file upload button maximum file size has been increased to 50 megabytes.
- We are releasing a new sync feature that allows us to execute custom methods during an update installation or sync. With this feature we can modify the structure of the database or file system beyond the sync’d elements and even add new sync’d elements within an update release. If the site being sync’d is more than one version behind its parent, the updates will all occur in order when the site is sync’d. These methods will also be executed when a backup from an older version is restored and sync’d to the current version.
- We have added a way to manually download update packages due to problems some servers have had downloading the archive file. After update version 8.0.23 has been successfully installed, subsequent updates will provide instructions to manually download the update archive in Development > Process Log when the automated download fails.
- A bug that caused the image resizing component to fail on 1 pixel images has been repaired.
- The new Design > Styles > Global > Drop Shadow attribute allows us to add a drop shadow (glow) to a static width site by simply enabling the feature, entering the width, and uploading three images.
- A new script has been added to CpScripting called FormStateAction and has been documented in the help file. It allows the execution of custom actions on form state objects.
- The CpScripting UserInfo script can now return a list of users RoleIds.
-
-
-
-
-
-
11/16/2009 2:50:59 PM
-
-
|
4. |
- Centralpoint Update History
- Everyone: All Users
- 5/22/2009
- Relevance: 20
-
-
12/31/9999 11:59:59 PM
-
Centralpoint Updates, Centralpoint Version, Oxcyon Release, Centralpoint Release, Digital Experience, Magic Quadrant, ECM, Content Management, Portal, Enterprise, User Experience, MDM, Master Data Management, Gartner
-
-
- Site Architecture / Module Designer / Initialize / Module has been modified to remember missing items. This allows users who do not have access to a module to update a design for that module without receiving an error message. It is still recommended that administrators with access to the module designer have access to all modules.
- Dynamic search forms containing a custom PostBackUrl are now supported on pages containing other forms. Previously, this scenario would prevent the other forms from submitting properly. These changes also included updates to the URL rewrite HttpModule so that we now fully support cross page post backs.
- The web site search SQL function has been modified to prevent duplicate records displayed when a record contains a searched keyword in more than one related taxonomy. It has also been modified so that search results where the criteria is found in the Title are ranked higher than when it is found in other attributes.
- A problem has been resolved which caused modules to disappear from client consoles when the Uber group selections for the web site were incorrect. Previously you could select module groups for a web sites that were not accessible to the master. When an unpredicted master event occurred these invalid selections were removed making modules disappear. The selectors are now filtered properly so that the invalid selections cannot be made.
- Most references to Response.End() have been replaced with ApplicationInstance.CompleteRequest() to prevent early termination exceptions from being reported in the Development / Errors modules.
- All SqlSiteMapProviders have been updated to prevent an error that was recorded in the Event Viewer when the OnSiteMapChanged event was triggered without an active HttpContext. Unnecessary caching has also been removed from the providers.
- The system has been updated to return a 404 error when an end user enters a URL containing an audience or role system name that does not exist.
- Dynamically generated login URLs have been updated to include the new audience in the path as opposed to the query string. The role must remain in the query string so that the Login page itself is loaded in the Public role.
- The lead tracking application has been updated to prevent the insertion of leads with null UserIds.
- The Resource (Design / Media Manager) HttpHandler has been completely rewritten for efficiency and to address “Server Too Busy” errors.
- The “Server Too Busy” errors have been resolved by removing the Response.Close call after Response.TransmitFile as described here: http://www.improve.dk/blog/2008/03/29/response-transmitfile-close-will-kill-your-application.
- Caching has been built into the handler including automatic expiration via the media manager module.
- Additional response headers have been added to resolve browser support issues.
- The class has been optimized for performance, memory management, and concurrency.
- All references to application state have been checked for proper use of locks to prevent issues with concurrency under high traffic situations.
- A problem with Master / Deployment / Synchronize that caused a JavaScript error when more than one site was included in the sync has been repaired. This JavaScript error caused you to lose track of the sync after the first site and forced you to manage the sync using the Process Monitor.
- Abstract views of documents in all modules previously redirected you to the home page of the module. This has been repaired so that abstract views display the appropriate content from the module designer.
- An advanced locker system has been implemented into the Management class for synchronization over page based code. This system allows us to lock sections of code like the ad banner click counter to ensure accurate counts.
-
-
-
-
-
-
6/8/2009 10:25:26 AM
-
-
|
5. |
- Centralpoint Update History
- Everyone: All Users
- 7/28/2014
- Relevance: 17
-
-
12/31/9999 11:59:59 PM
-
Centralpoint Updates, Centralpoint Version, Oxcyon Release, Centralpoint Release, Digital Experience, Magic Quadrant, ECM, Content Management, Portal, Enterprise, User Experience, MDM, Master Data Management, Gartner
-
-
Feature |
Summary |
FormAudienceProximity CpScript
|
This new script is used to render a record’s related audiences, and the distance to each audience, when the user enters an address or zip code into a form field and executes the search. It was intended to work with the FormAudienceProximityOrderBy CpScript, and requires that individual audiences are selected instead of using 'All Audiences'. This script has been documented in the Scripting help file.
|
FormAudienceProximityOrderBy CpScript
|
This script is used to sort search results by their related audience distances when the user enters an address or zip code into a form field and executes the search. It was intended for use at the beginning of a Site Architecture > Module Designer > Results View (#2) > Order By attribute, and requires that individual audiences are selected instead of using 'All Audiences'. This script has been documented in the Scripting help file.
|
MobileNavigation2 CpScript
|
A new IncludeHiddenPages property has been added. When set to 'false' navigation items whose Visible attribute is set to 'No (Hidden Page)' will not be included.
|
ModulePageOverrides CpControl
|
A new HomeErrorWhenDocExists property has been added. By default Centralpoint displays the Home View (#1) of the module when a URL containing a document identifier (/Audience/SiteMapItem/Document.aspx) is accessed and the Document doesn't exist. When this property is set to 'true' the module will return a 404 error instead which can be handled by the Admin > Error Messages/Redirects module. This property is set to 'false' by default.
|
Pager CpControl
|
A new "cpsty_PagerCurrentPage" CSS class has been added to the current page link.
|
URL Rewriter
|
A bug in Centralpoint's URL rewriter as it relates to query string variables has been discovered and repaired. During the URL rewrite the query string variables were being decoded which apparently had very little effect on how they worked until a site was accessed with an encoded ampersand. When it became decoded Centralpoint then treated the ampersand as the end of the query string variable and truncated it at that point. To repair this problem we have updated the URL rewriter to leave the query string variables encoded as it should have in the first place.
|
-
-
-
-
-
-
8/11/2014 9:41:36 AM
-
-
|