News:

At Osclass we have changed our Privacy Policy and Terms of Use in order to adapt them to the new General Data Protection Regulation (GDPR). We want you to know what user data we store, what we need them for, and who we share them with in each specific case. Furthermore, we are making it even easier for you to exercise your right to manage your own data.

Our goal is that you enjoy the best possible experience with our website. As the GDPR comes into force, legislation requires us that you grant us permission—both to us and our partners—to store cookies in your browser. Remember you can find more information about what we do with your data by clicking here.

Short answer .. yes you can by adding routes . But that depends on the number of users . More users harder and slower to match . Www.yoursite/london it is a user called london a category called london ot a city called london ? You have to make sure that your user names do not match either cities in your database or category name . Thats the short version . The long version will take some hours to write the answer and weeks to think and implement a new router inside some routes

No need to change core files . Just add username as route name . But like ive said .. implementint a username strategy on user register or edit username not allow names that already exist as city region or categoryY've made some tests with works well under 10 000 routes . Matching the route under 0.1 sec . With 512 mb ram.. shared hosting... But if the number of routes increases ,more memory is needed more time will be consumed ,and some changes to rewrite class to match faster . Now it used foreach routes as route {preg match } . You will have to implement a diferent strategy with static routes .

Short answer .. yes you can by adding routes . But that depends on the number of users . More users harder and slower to match . Www.yoursite/london it is a user called london a category called london ot a city called london ? You have to make sure that your user names do not match either cities in your database or category name . Thats the short version . The long version will take some hours to write the answer and weeks to think and implement a new router inside some routes

@Web-MediaThat's an easy fix. We could add a variable at the beginning of user-name.$users = 'user-'$users{USER-NAME}And we never get that kind of problems.

No need to change core files . Just add username as route name . But like ive said .. implementint a username strategy on user register or edit username not allow names that already exist as city region or categoryY've made some tests with works well under 10 000 routes . Matching the route under 0.1 sec . With 512 mb ram.. shared hosting... But if the number of routes increases ,more memory is needed more time will be consumed ,and some changes to rewrite class to match faster . Now it used foreach routes as route {preg match } . You will have to implement a diferent strategy with static routes .

When a user registers, by default user-name is user-id. And after that if we disable user-name changes for users, problem will be solved. Or as i explained above we could add a varibale at the beginning of user-name.

Or you can create a single route as new entry point of your website and you've just create a new index controller .From there you can define a new url matching for items categories regions cities and users and use an external library as your main router.