Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
An URL Router extension for Symphony
PHP JavaScript
Tag: 1.1.0

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
assets
LICENCE.txt
README.markdown
extension.driver.php

README.markdown

URL Router

Version: 1.1.0

Author: [Symphony Team]

Build Date: 2011-07-08

Requirements: Symphony 2.2

Installation

  1. Upload the files into a folder named "url_router" in your Symphony 'extensions' folder.

  2. Enable it by selecting "URL Router" on the "System -> Extensions" page, choosing "Enable" from the with-selected menu, and clicking "Apply".

  3. Once installed, under the preferences page, you can choose between adding a Redirect or a Route in the URL Router section.

Changelog

1.1.0

  • Removed the global option to redirect routes.
  • Changed the duplicator templates to allow either Routes or Redirects, instead of the global choice.
  • Added updating logic.
  • Added prevention of routing if the code is updated, but the extension reference in Symphony isn't. This is due to the functionality changing, and will prevent errors.

1.0.2

  • Stupidity fixes.

1.0.1

  • Bug fix to remove rogue query I forgot to remove, thanks Vlad Ghita for spotting that one

1.0 (John Porter, Nick Dunn)

  • Update as Symphony Team takes ownership.
  • Renamed extension class and folder to url_router.
  • Manually merged @nickdunn's changes.

0.5:

  • Symphony 2.2 compatiability update

0.4 (John Porter):

  • Applied patches from pull requests to fix various issues including save failure when no redirects entered and pass-by-reference warning

0.3 (Max Wheeler):

  • Remove router.js as it's no longer needed
  • Fix error in save logic, no longer tries to write to config.php

0.2 (Max Wheeler):

  • Only add router.js to the /system/preferences/ page (was breaking other JS)
  • Updated README with correct installation details

0.1:

  • Initial release, brief documentation forthcoming.
Something went wrong with that request. Please try again.