nathan

He is more of a front end developer, though

nathan

I'm shocked there isn't a #hosting channel yet...

nathan

I see it in all the ways mentioned here, but also as a massive security hole. All it would take is one admin to lose control of their account, and (depending on what apache modules you have enabled) the intruder can take control of the entire website and codebase. If you're relying on the FTP method, the likelihood of having the proper backups and systems in place to restore the site is slim to none...

nathan

If there's something you need to do in .htaccess to the point that a content editor should have access to it, your architecture should probably be rethought.

nathan

@chillu - So, it'd become this...?

  1. ---
  2. Name: rootroutes
  3. ---
  4. Director:
  5. rules:
  6. '$url': 'RedirectController'
nathan

(We have a pending upgrade ticket coming....)

nathan

@chillu Oh, I should have clarified... This is SS Framework(only) 3.1.12 😁

nathan

So, we have the following routes set up:

  1. ---
  2. Name: rootroutes
  3. ---
  4. Director:
  5. rules:
  6. '': 'RedirectController'
  7. '//': 'RedirectController'

I basically want ALL requests to go to the RedirectController (except for /admin/*). This seems to be working locally. But when we deploy to our dev/staging servers and attempt to go to https://www.example.com/abc/123/, we get Action 'abc' isn't available on class RedirectController. Again, it works correctly locally (same apache/php versions). I'm a bit stumped... Here's the code for RedirectController.php: https://gist.github.com/nathanbrauer/9b06292c0fa587629c7ebb0dd7f1ffac