question Reagarding siteurls_override.config

Hi Telligent Support,


we are trying to upgrade existing site to Zimbra Community 8.0 version. We have one custom authentication module.

For that module to work  some  settings are   added in siteurls_override.config.


See sample code (siteurls_override.config)



  <Override xpath="/SiteUrls/locations/location[@name='controlpanel']" mode="add">

    <url name="myGroup_ControlPanel_CustomConfiguration" path="Groups/CustomConfiguration.aspx?GroupID={0}" />



  <!--SSO Start-->


  <Override xpath="/SiteUrls/locations/location[@name='common']/url[@name='login']" mode="change" name="physicalPath" value="/xxxx/"/>

  <Override xpath="/SiteUrls/locations/location[@name='common']/url[@name='login']" mode="change" name="page" value="sso.aspx?action=login"/>

  <Override xpath="/SiteUrls/locations/location[@name='user']/url[@name='user_ChangePassword']" mode="change" name="page" value="sso.aspx?action=changepwd"/>




In 8.0 these files are no longer valid(siteurls_override.config, siteurls.config).



Now could you please help us with some samples/code snippets  of how to move this values from this file (siteurls_override.config) to the plugins.

If you have samples in please provide the link




  • You can use the cookies auth plugin that replaces the old SSO module,

    It has definitions for the login url, but you are own your own for change password.  Your custom login page should define this link, not the community platform.

  • In reply to Patrick Mason:

    Thanks for your inputs. I am actually looking for a way to override siteurls using plugin which is mentioned in

    if i want to override any of the urls mentioned in the site url config file, how can I achieve it using appropriate site url plugin .

  • In reply to swapna:

    You can no longer override any Zimbra provided urls.  In the case of Login/Logout links as you described above, you can achieve similar results in 8.0 through our SSO module as patrick described above.

    For custom urls, you need to implement an INavigable plugin - .

  • In reply to Alex Crome:

    We need to set the homepage to a custom page that we developed, which is []/p/custompage. Now that override siteurls is no longer an option, can you provide the steps to accomplish same using the INavigable plugin? There is not much detail on the referenced page.

  • In reply to Nimbus:

    The platform no longer supports overriding core Urls in this manner.  If you want to have a custom page then you would have to do one of the following:

    1. Have the page be a static page and have your community live in a sub domain or virtaul directory

    2.  Intercpet the request and redirect either using a widget on the dashboard or a .net level component

    3.  Rework the user dashboard to be like your custom page and turn off user ability to modify the dashboard

  • In reply to Patrick Mason:

    thanks for the suggestions. option 1 is out, because the page incorporates Zimbra elements, so it can't stand alone.

    option 2 sounds like the ideal solution, but we have already unsuccessfully tried using a .net level component. we placed a custom page at the root, redir.aspx, and made this the default document. the script we implemented is the following:

    <%@ Page Language="C#" AutoEventWireup="true" %>

    <script runat="server">

     protected void Page_Load(object sender, EventArgs e)





    however, Zimbra intercepts the inbound requests and ignores redir.aspx, even though IIS has this set as the default document. is there anything further we need to do within the web.config or elsewhere for IIS to instead recognize redir.aspx as the default document?

  • In reply to Nimbus:

    The default probably doesn't work becasue our home page is invoked first.  That said you can accomplish the same thing by putting a widget on the home page that redirects via widget API or javascript

  • In reply to Patrick Mason:

    For widgets its $core_v2_page.Redirect(url)

    Its the same code as above

  • In reply to Patrick Mason:

    Thanks Patrick. I was able to create a widget with $core_v2_page.Redirect("/p/custompage") and it works great. This also allows me to remove the code vis-a-vis the widget itself, just in case we later want to return to the page from which we're redirecting.