Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6391357
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T03:39:42+00:00 2026-05-25T03:39:42+00:00

I`v been upgrading CakePHP from 1.2.10 to 1.3.11 by using Migrating from CakePHP 1.2

  • 0

I`v been upgrading CakePHP from 1.2.10 to 1.3.11 by using “Migrating from CakePHP 1.2 to 1.3” Guide and i’m aware that i must ensure that my routes are compatible with 1.3.

However my routes don’t do anything that’s incompatible:

This is no longer supported as mid-route greedy stars behaved
erratically, and complicated route compiling. Outside of these two
edge-case features and the above changes the router behaves exactly as
it did in 1.2

The other edge case is:

First path segments using full regular expressions was removed.

How my routes behave:

  • When opening homepage, doesn’t work, however on 1.2 it sucessfully matched route #1 (solved by Ivo)
  • /lv/products *doesn’t work*. Should have matched #6 using controller “Products” and default action “index” but it thinks that “lv” is controller (ignoring the :lang param)
  • /lv/products/index works!
  • /lv/products/view/productname works!

Cake provides errors similar to this error (copied when opening /lv/products:

Missing Controller
Error: LvController could not be found.
Error: Create the class LvController below in file: app\controllers\lv_controller.php
<?php
class LvController extends AppController {

    var $name = 'Lv';
}
?>

My routes:

    //Route #1: This route should have worked as a root route, because we have a default for :lang. But now i cannot open up the homepage if i don't define explicit "/" route
    Router::connect("/:lang/",
        array("controller" => "start", "lang" => "lv"),
        array("lang" => "[a-z]{2}")
    );

    //#2 This route seems to work ok.
    Router::connect("/admin/:lang/:controller/:action/*",
        array("lang" => "lv", "admin" => true),
        array("lang" => "[a-z]{2}")
    );

    // ==============================================================================

    //#3 Routes with static parts - works
    Router::connect("/:lang/info/*",
        array("controller" => "sections", "action" => "view", "lang" => "lv"),
        array("lang" => "[a-z]{2}")
    );

    //#4
    Router::connect("/:lang/news",
        array("controller" => "news", "action" => "listall", "lang" => "lv"),
        array("lang" => "[a-z]{2}")
    );

    //#5
    Router::connect("/:lang/employees",
        array("controller" => "employees", "action" => "index", "lang" => "lv"),
        array("lang" => "[a-z]{2}")
    );

    // ==============================================================================


    //#6 Catch all route. 
    Router::connect("/:lang/:controller/:action/*",
        array("lang" => "lv"),
        array("lang" => "[a-z]{2}")
    );

Thank you for any assistance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T03:39:43+00:00Added an answer on May 25, 2026 at 3:39 am

    For a default root, I would guess that you want '/', or '/<param>'

    '/:lang/' expects something to be there for lang – it’s not optional, afaik. Try '/:lang' instead.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm upgrading an app from Rails 3.0 to 3.1. We've been using Compass and
I am a .Net developer that has been tasked with upgrading a classic asp
I've been using LaTeX since 2005 with the TeXLive distribution and I've been upgrading
I've been playing around with upgrading from an iPhone app to a Universal application,
I have noticed since upgrading to iOS5 that an audio app I have been
I have recently been tasked with upgrading an application from .net 1.1 to 3.5
We've been using VS2008 and soon will be upgrading to VS2010. I have been
I have Core Data application and I have been migrating (upgrading) the core data
We've been successful in upgrading our SSRS servers from 2005 to 2008. Now when
I have been tasked with upgrading a large web application from .net 1.1 to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.