• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Feature
    • More Customizeable URL Routing

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: More Customizeable URL Routing

    • Issue Tools
      • View Changes
    1. issueid=2007 September 27, 2010 6:16 PM
      pegasus pegasus is offline
      VaultWiki Team
      More Customizeable URL Routing

      With 3.1, we should finally introduce more advanced URL routing features - like:
      • Define custom URLs for articles without creating plugins
      • Define nested URLs for namespaces
      • Use simpler rewrite rules for custom URLs, but still support vBSEO and content.php
      • Define custom URL parts for certain page actions.
        e.g. /wiki/article?do=comments&page=2 becomes /wiki/article/talk/page2/


      Doing this requires passing all requests to non-existent files through one file (wiki_index.php) and matching them against a cascading rule list. Fetching the rule list needs to occur with minimal overhead (i.e. not calling init.php) and use an opcode cache when available, then the vb-cache, then the respective database dump.

      As of this posting, the router itself is complete, but there is no data in the appropriate format.
    Issue Details
    Issue Number 2007
    Issue Type Feature
    Project VaultWiki 4.x Series
    Category URLs / Routing
    Status Implemented
    Priority 8 - Major Features / Enhancements
    Suggested Version 4.0.0 Alpha 1
    Implemented Version 4.2.0 Alpha 1
    Milestone VaultWiki 4 Alpha X
    Software DependencyAny
    License TypePaid
    Votes for this feature 2
    Votes against this feature 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. March 26, 2011 4:09 PM
      pegasus pegasus is offline
      VaultWiki Team
      Completed the DMs and controllers needed to save and parse custom routing. The rule list is fetched as described above, since the models for the various cache retrievers have been abstracted and instructed to create a database link if none already exists. Routing just needs to be implemented via a form field for each content type, but this should be considered part of the completion of the editors for those types.

      Setup for custom page action routing should be handled as a separate feature since it will not be completed for Alpha 1.

      Originally suggested for 3.0.4.
      Reply Reply  
    2. January 17, 2021 5:49 PM
      pegasus pegasus is offline
      VaultWiki Team
      Implemented in 4.2.x. At the current time, we don't allow changes to the page actions, but we do allow the following:

      - Admin defines which domains can be used for the wiki, and if any domains are used only by the wiki.
      - Admin defines which paths, relative to a domain, can be used for the wiki, and if those paths are used only by the wiki.
      - Admin defines which route-prefixes can be used for the wiki, and if those routes are used only by the wiki.
      - Admin defines which route-prefixes can be used in combination with which paths.

      - Admin defines a default path which applies to all content within an area.
      - Admin defines which paths can be used as a custom path within an area.
      - Admin defines a default path which applies to any content not within an area (index, certain feeds).

      - User must have permission to customize URLs. If the user does not have permission, existing content will continue to use the existing URL. For new content, the default URL would be used.

      - In the editor for a page, users specify a domain, path, and route-prefix respectively. Users can choose to have the URL relative to the area (or certain other parents) or not. Users can specify a custom title which is used only for the URL (without affecting the page's name). For example, a page named "This is a test" can have a custom URL such as "domain/path/route/Test-page" instead.

      - Altering a custom URL after the fact will create a special kind of synonym even if the page's title was unchanged (this can be suppressed using the same mechanism as before). This prevents existing bookmarks, search engine listings, and direct links from suddenly breaking.

      - Existing custom URLs that were created by plugins in VaultWiki 3.x are automatically converted so they continue to function normally.

      If there is enough demand, we may revisit page-action customization in the future.
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 11:31 PM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.