https://verint14-pre-03.socialedgeconsulting.io/practice-a/en-US14.0.0.622 14https://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/76/looking-for-your-feedback/1532Wed, 27 May 2026 19:50:00 GMTforumreply:1532This is another replyhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/76/looking-for-your-feedback/1531Wed, 27 May 2026 19:50:00 GMTforumreply:1531This is another replyhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/76/looking-for-your-feedback/1530Wed, 27 May 2026 19:50:00 GMTforumreply:1530This is a replyhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD29/test-videoWed, 12 Nov 2025 15:15:00 GMTarticle:364e58e1-a32b-4b55-b80e-7242eff9b5fcHow-to1.mp4 This is a how to video on how to testhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD28/test-faqMon, 10 Nov 2025 20:18:00 GMTarticle:647f41d2-6807-4377-a626-b90f4df8c104Certification Hi all - I'm starting my Magnolia certification today and I'm looking forward to getting started. I've been using Magnolia on and off for a few years now so I'm looking forward to seeing what's new since I last used it in earnest in 2018. What are everyone's favorite new features? Discussion Hi this is super exciting! One of my favorite features it the ability to hover over a community username and see a preview of their profile! You can also do the same for content! I also love that feature! Being able to lock discussions and questions is another added bonus!https://verint14-pre-03.socialedgeconsulting.io/practice-a/p/test-custom-pageMon, 09 Sep 2024 19:52:00 GMTpage:https://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/60/what-makes-our-product-stand-out-from-the-competition/199Wed, 13 Mar 2024 15:04:00 GMTforumreply:199Test Replyhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD23/check-out-this-latest-code-to-help-with-all-backupsTue, 07 Feb 2023 19:00:00 GMTarticle:eb145df6-81fd-412b-9582-5d9fa535891cHi all - please see this code to help with any issues you may come across while backing up code or contenttroubleshootingproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD22/hey-everyone---check-out-this-helpful-gitlab-codeTue, 07 Feb 2023 16:28:00 GMTarticle:357264b0-797f-4d0a-a2fc-e906e3e5ba41Hello - Please make sure to check out this GitLab code that helps with troubleshooting any practice issues!https://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/16/exporting-and-filtering-site-analytics-data-from-the-platform-analytics-consul/155Wed, 20 Jul 2022 13:24:00 GMTforumreply:155Thank you Jane Kratz appreciate it and looking forward to your updateshttps://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/18/unsubscribe-an-email-notification-from-magnolia/99Wed, 25 May 2022 15:57:00 GMTforumreply:99We would have to resubscribe them. Who is the user and I can help with this process?https://verint14-pre-03.socialedgeconsulting.io/practice-a/f/q-a/16/exporting-and-filtering-site-analytics-data-from-the-platform-analytics-consul/86Wed, 25 May 2022 15:28:00 GMTforumreply:86It was not done intentionally, have to confirm who headed that process. We are hoping to have it fixed soon as we have reached out to the tech team for supporthttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD20/enable-allowdotinpath-in-urlscanTue, 03 May 2022 19:47:00 GMTarticle:c7a4147f-cfd2-453f-8a00-bac256e4066cBy default, UrlScan denies access to any URLs which include a dot in the path, so any user uploaded content in these paths is inaccessible. To resolve this issue, take the following steps: Open urlscan.ini. Find the line that reads: AllowDotInPath=0 Change this to: AllowDotInPath=1 Save and close the file. If you're using versions prior to IIS7, you must restart IIS for the change to take effect.troubleshootingproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD21/magnolia-community-is-scheduled-for-maintenance-on-7-30Tue, 03 May 2022 19:47:00 GMTarticle:6268fb52-4b6e-429e-828a-f9da2beca64aPlease be advised the site will be down for maintenance on 9/30alertnotificationhttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD18/cachingTue, 03 May 2022 19:46:00 GMTarticle:fd42d518-7083-41dd-ab58-22b076f53e3fA cache allows applications to store results from expensive data operations (e.g., a database call or web service request) so they can quickly accessed if requested multiple times. Hierarchy The Telligent cache object is built by combining one or more layers together to form a single logical structure. Each layer sits atop another, creating a hierarchy that defines how requests are satisfied: When a retrieval request comes in, each layer is searched until the item is found. If the item is found, that item is copied to all layers above the cache that satisfied the request. This allows cached objects to move from slower caches to faster caches, maximizing locality principles and reducing global system stress. Providers and scope Each layer in the hierarchy defines how it caches objects. A layer specifies its supported caching behavior by using one or more CacheScope values. Only requests containing the supported scope will be sent to a provider. CacheScope values are: Name Description None No location specified. Context The Context location is specified. This scope is for storing items for a short amount of time and is typically private to the user. Process The Process location is specified. This scope stores items inside of the running process and is shared among users. Distributed The Distributed location is specified. This scope is used when items are available to all running processes. Typically, distributed-only caches will be the slowest cache types. All All possible scope values are specified. The Telligent cache object comes with built-in providers that are available for use. They include: HttpContext (Context scope): Items are cached inside the current HTTP request. This is the fastest cache available for web requests and should always be designed at the lowest level cache in a website environment. ASP.NET (Process scope): Items are cached inside the HttpRuntime object. Items cached using this provider are available to all threads that access the same HttpRuntime object. NOTE : This cache can be used outside of a web request. AppFabric (Distributed scope): Items are cached using the Microsoft AppFabric distributed cache system. Items in this cache are available to all processes that can access the AppFabric server. Default timeout When items are placed into cache, it is not necessary to give a timeout. In these cases, the currently configured default timeout value is used. The out-of-the-box default timeout is 1 minute and 40 seconds. Many objects in Telligent Community Server use the default timeout value. In addition to a very simple scaling mechanism, controlling the default timeout allows for finer control over the cache system in webfarm scenarios where staleness is a concern. Generally, if more than one server is running a site, the default timeout value should be low to keep staleness at a minimum. The lower the value, the less likely you are to see staleness - but at the cost of decreased cache performance. Default timeouts are set inside of the caching configuration XML settings. For more information, please see the Configuration documentation. Cache factors Cache factors allow us to complete the picture of how long items should be cached. Cache factor values can be set for any cache layer and is used as a universal adjustment on timeout. Where cache factors become important is when a cache is set up using a distributed cache. For example, assume we have a website that contains many nodes (webfarm). Each node is running the AspNetCache provider to cache items locally on each server. Because we're in a webfarm scenario, we have to reduce our default timeout because we can't risk staleness and other cache inconsistencies. To increase the cache performance of the website, we want to introduce a distributed cache so longer-lived objects can be held in memory for longer amounts of time. In this situation, we want to increase the default timeout because we know that all web nodes will keep the distributed cache in sync as long as we relay the changes back to the distributed cache server. But this poses a problem: If we increase the default timeout, then the locally cached items in the AspNetCache will risk being stale in any web server that doesn't handle the data operation. But if we do not increase the default timeout, objects will be removed from distributed cache much more frequently than they need to be. To solve this problem, we can use a cache factor on the distributed layer. By setting a cache factor on the distributed layer, we can keep a lower default timeout for our local server caches. Items sent to distributed cache will be cached longer, by default, then items cached on the local server. It should be noted that all timeouts are subjected to the factor, not just default timeouts. Cache factors are set inside of the caching configuration XML settings. For more information, see the Configuration documentation. Overrides Included in the Telligent cache system is a mechanism allowing runtime adjustments to be made to cache operations. This allows users to modify values used in Community Server (or added by a third-party component) if they have a site-specific need to do so. Overrides should be used sparingly, but they offer a level of control that may yield a large benefit. Before an item is sent to any cache layer, conditions are checked to see if a particular override should be applied. If a condition is met, that override is triggered and no further conditions are processed. This means that only one override can be executed for each cache operation. Conditions can be defined using any of the following constructs: Condition Description startsWith A condition that attempts to match keys or tags against a starting pattern. endsWith A condition that attempts to match keys or tags against an ending pattern. regex A condition that attempts to match keys or tags against a regular expression. object A condition that attempts to match the cached item's type against the specified object type. Additionally, conditions can be combined to form composite conditions. Composite conditions include: Condition Description and All child conditions must match in order for this composite to match. or Any child condition must match in order for this composite to match. not A special case composite that must contain exactly one child condition. The child condition must be false in order for this composite to match. Overrides are defined declaratively using XML. For more information on how to set and configure overrides, see the Configurationtroubleshootingproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD19/common-things-to-check-when-using-forms-authenticationTue, 03 May 2022 19:46:00 GMTarticle:73af6454-757b-406b-b296-dbf237d4f8adWhen using the Forms Authentication module, there are a couple of areas to check first when troubleshooting any issues you might encounter when setting it up. These include the authentication ticket name, the machine keys, the cookie path, and the cookie domain. Authentication ticket name The most common issue when using Forms Authentication is that the name of the cookie used for the authentication ticket is different between the two applications. Forms Authentication works by creating a certain cookie that contains basic information about the user. The name of the cookie is set in the web.config . In ASP.NET, the default name is “.ASPXAUTH” , however Telligent Community Server's out-of-the-box web.config sets it to “.Zimbra.Evolution” . If the two applications do not have the same name set, then the other application will not recognize the authentication ticket from the main application. To change this, you can either change the main application to match Community Server's setting by changing its line in the web.config to “.CommunityServer ”, or you can change Community Server to use the same setting as your own application, but changing its web.config to use “.ASPXAUTH” or whatever it already has specified. An example is: Machine keys When using Forms Authentication between two ASP.NET applications, you need to ensure that the machine keys between the two applications match. The machine keys are used to encrypt and decrypt the information within the authentication ticket. If they do not match, one application will not be able to utilize the other application’s authentication ticket. The machine keys are set within the section of the web.config . A sample machine key section looks like this: Cookie paths A frequent issue with the cookie created for the authentication ticket is the path on the cookie. Typically, an application will create the cookie with its path set to its own application path. So if your application is at /app and Community Server is at /tc , when you set the authentication cookie within /app , ASP.NET will automatically set the cookie’s path to /app . Then the browser will only pass the cookie along to page requests under /app , and not to /tc . To get it to carry over, you’ll need to set the cookie’s path to / , so that it will be accessible between the two applications. The cookie’s path can either be specified in the web.config or through code. To set it in the web.config , use the path attribute on the line in the parent application's web.config , such as: Additionally, it can be set in code when you use the GetAuthCookie method of FormsAuthentication instead of just the SetAuthCookie method when creating the cookie in the parent application. For example: HttpCookie cookie = FormsAuthentication.GetAuthCookie(username, true); cookie.Path = "/"; Response.Cookies.Add(cookie); Cookie domains Another common issue with the cookie for the authentication is the domain for the cookie. Similarly to the paths of the cookies, if the cookies are created on two different subdomains, then the cookie will only be accessible on the domain where it was created. For instance your main application may be on www.domain.com , but you have Community Server running on tc .domain.com. If you create the cookie on www.domain.com , the browser will only send it to that domain, and it won’t be passed along when they navigate over to tc .domain.com. The cookie can be carried over by setting the domain to “.domain.com” . Cookies don’t use the common “*” wild card. Simply use “.domain.com” . With this entry, the browser will not pass the cookie when it goes over to cs.domain.com as well. Like the path, the domain can be specified in either the web.config or through code. When setting the web.config file, it will only check for the authorization cookie. You must have this set for the site to correctly recognize the new domain level cookie: The "domain" name is ignored by the FormsAuthentication.SetAuthCookie method, so you must manually set it on your login page when creating the AuthCookie . For example: HttpCookie cookie = FormsAuthentication.GetAuthCookie(username, true); cookie.Domain = ".domain.com"; Response.Cookies.Add(cookie);troubleshootingproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD17/what-are-the-system-requirementsTue, 03 May 2022 19:44:00 GMTarticle:04ce3a5e-7514-4a85-8d94-2c075b289a13Server Requirements Database Server Microsoft SQL 2016 or higher Web Servers Windows Server 2016* or higher .NET Framework Community 12.0 (or newer) requires a minimum of version 4.7.2 IIS configured as described below Job Servers Windows Server 2016* or higher .NET Framework Community 12.0 (or newer) requires a minimum of version 4.7.2 Search Server ( Solr ) Windows Server 2016* or higher Java JRE 1.8 (update 121 or higher), 64-bit version (based on Solr * For production environments, only Windows Server operating systems are supported. Windows 2012 R2 will work but not recommended as mainstream support from Microsoft ended October 2018. For development environments, client operating systems (Windows 10 or higher) may be used. IIS Configuration The following IIS components must be installed - this can be done through Server Manage on Windows Server, and through "Turn Windows features on or off" on client versions of windows. Web Management Tools IIS Management Console World Wide Web Services Application Development Features .Net Extensibility 4.x Asp.Net 4.x ISAPI Extensions ISAPI Filters WebSocket Protocol Common HTTP Features HTTP Errors Static Content The following are not required, but are highly recommended: World Wide Web Services Health and Diagnostics HTTP Logging Request Monitor Tracing Performance Features Dynamic Content Compression Static Content Compression Security IP Security Request Filtering If you are setting up an internal community and plan on using active directory for authentication, you will require World Wide Web Services > Security > Windows Authentication. HTTP/2 To achieve optimal performance, it highly recommended to ensure HTTP/2 is working for your site. Starting with IIS 10, HTTP/2 support exists and no new configuration is necessary. If the site is behind other hardware (ex. load balancer) you may need to enabled HTTP/2 support there. To confirm your site, view the 'Network tab in your browser's developer tools and confirm the protocol is HTTP/2. Note: There are a few cases when HTTP/2 is not supported, most notably when using Windows authentication (NTLM/Kerberos/Negotiate). In these situations the requests will fall back to HTTP/1.1. Antivirus Antivirus should be installed on the server hosting the centralized file storage (CFS) files. It is recommended to configure the antivirus software to scan files only when writing. Supported Browsers Official support for browsers is divided into two tiers. In tier one, we evaluate all reported bugs. The browsers in this tier include: Microsoft Edge Google Chrome (latest stable version) Mozilla Firefox (latest stable version) Safari on Mac (latest stable version) Mobile Android 5.0+ Safari (latest stable version on iOS) Chrome (latest stable version on Android and iOS) In tier two, we evaluate bugs for broken functionality. The browsers in this tier include: Microsoft Internet Explorer 9, 10, and 11 Compatibility mode is not supported Administration backend is not supported in Internet Explorer 9 Safari on Mac (previous major macOS version) Mobile Safari (previous major iOS version)user guidesproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD14/how-to-configure-the-megamenuTue, 03 May 2022 19:43:00 GMTarticle:0b749927-304d-42c6-b474-8c9e69d23257MegaMenu A user-friendly menu that displays nested navigation levels that are set in a special configuration screen. Our MegaMenu features a custom administrative panel for the management of top-level navigation labels and submenu items. The configuration also allows for the inclusion of a featured image for each submenu topic. Key features: Easy to configure and maintainable even after using Select icons, background for elements of levels 3, 4, 5 ... Setup and Configuration Add the Mega Menu Widget to a Place or Application Page Navigate to the relevant group or application where you want the Mega Menu Widget to appear. If you want to add your menu to all community, you need to use the home page for changes. Select the Pencil icon at the top left. 3. Select Manage Group Theme . 4. Select Edit this Page 5. From the Widgets menu, search for the Mega Menu by SE widget and add it to the page by dragging and dropping the widget onto the page. 6. If you want to add your menu to all community, you need to lock Mega Menu Widget on the page. Configure the Mega Menu Mega Menu is needed for displaying menu items in a multi-levels format. Every item can have a unique link, avatars, banner, and configuration options. Below is a quick overview of what an item is and the main components involved. Menu Configuration You can add CSS class to your widget Useful functions for more comfortable setup settings: Expand and Collapse All. Expand All to see all items of the menu. After all changes, you can “Collapse All” items. Elements of Menu Item Name & URL & Description. Every item has separate settings. You can add Name, Url and Description. Banner Image & Avatar. Use it for making your menu unique and rememberanal. Configuration Menu Item Click Add Name your Menu Item Add URL for your item if needed (optional) Check the box if you want the URL to open in a new window Add Description for your item if needed (optional) Paste the link for a Banner Image Paste the link for an Avatar Click Save Repeat the steps above for creating new menu items. Scroll to the bottom of the widget and click the Save All button. You are not required to save after editing each section, but we recommend you do to avoid accidentally closing the configuration panel without saving. You can click Cancel to cancel all your changes and leave the configuration panel. Editing the created item Choose the item, which you want to edit Click 1 or 2 button for editing Change any needed information Click Save Deleting the created item Choose the item, which you want to edit Click 1 or 2 button for deleting Click Yes Click Save Publish the Page Click the Publish Button in the Management Console Panel to publish your changes 2. Click the X in the Management Console Panel, to close the Panel 3. Your page will appear published with your updatesuser guidesproduct ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD15/version-1-2-user-guideTue, 03 May 2022 19:43:00 GMTarticle:a80d7571-4b8c-499d-89c3-657407b16d93Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi viverra dignissim libero, vitae pretium ipsum feugiat eget. Suspendisse vel pretium est. Suspendisse in lacus nec sem tristique ultricies. Integer ut arcu a tortor convallis eleifend vitae in est. Donec ac ullamcorper nulla. Nulla nisi lacus, euismod porta volutpat a, elementum et dolor. In maximus luctus odio, aliquam faucibus metus maximus in. In tincidunt facilisis neque vel pharetra. Etiam vel congue ligula, at varius quam. Nullam fringilla, eros non rutrum elementum, ligula est auctor quam, et volutpat felis metus ac ante. Pellentesque ultricies viverra sollicitudin. Donec sed sagittis risus. Morbi cursus est ut nisi aliquet tristique. In lorem nulla, imperdiet ac odio a, sollicitudin tincidunt risus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos.user guidesversion 12product ahttps://verint14-pre-03.socialedgeconsulting.io/practice-a/a/practice-a-documentation/PD16/version-1-3-user-guideTue, 03 May 2022 19:43:00 GMTarticle:25cbd7db-d373-4582-8ec8-67b1a6d5823cLorem ipsum dolor sit amet, consectetur adipiscing elit. Duis pulvinar diam commodo lacus viverra, nec accumsan neque dapibus. Nullam non ante non mi placerat luctus eu id augue. In consectetur quam sodales ligula facilisis, non mattis massa dictum. Mauris sed eros nulla. Aenean condimentum augue sed vehicula porttitor. Etiam fringilla porta augue. Morbi nec tellus convallis, tincidunt est ut, eleifend sapien. Integer non libero ultrices, placerat tortor eget, congue sapien. Aenean non nibh finibus, luctus odio vitae, posuere orci. Nunc fringilla lorem eu nulla scelerisque euismod. Ut nec purus dictum, fringilla turpis ac, tempor ipsum. Ut nibh quam, bibendum vestibulum lacus vel, molestie suscipit velit. Aenean sollicitudin massa vel fermentum bibendum. Praesent interdum turpis id dolor blandit egestas. Nunc sagittis maximus mi id molestie. Nunc imperdiet, quam vel ultricies congue, turpis felis sagittis est, a faucibus felis lorem sit amet lorem. Nulla pharetra sapien mauris, at interdum nisi elementum ut. Vivamus sit amet dui gravida, consequat sem et, euismod libero. Nullam in diam at nulla semper pulvinar. Fusce convallis ullamcorper eros, nec sodales sem. Ut lacinia arcu a mi ornare, in viverra libero iaculis. Maecenas tincidunt tellus ligula, at placerat arcu molestie et. Nam gravida lectus at tellus pulvinar, eu finibus nulla dignissim. Proin id urna et ante commodo dignissim. Sed eleifend enim efficitur, consectetur nibh quis, iaculis velit. Fusce bibendum tortor sit amet eros euismod placerat. Pellentesque tortor eros, cursus in molestie at, bibendum non risus. Phasellus pretium in purus quis mollis. In nec porta lacus. Suspendisse ut tellus sit amet erat pellentesque interdum vitae nec orci. Phasellus posuere neque quis nulla accumsan, eu porttitor mi consectetur. Nunc tellus justo, gravida nec augue nec, rutrum aliquam sem. Cras dictum, tortor eget consequat vulputate, nisi nibh fringilla quam, sed pellentesque diam augue ac lorem. Suspendisse consequat congue turpis sit amet facilisis. Vestibulum viverra interdum aliquam. Suspendisse maximus odio eget urna mattis egestas. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque id mauris ac nisl blandit facilisis.user guidesproduct a