0

It says in a support thread that Expression Engine has a maximum number of segments allowed that can't be changed (I can't think of a reason why they would need to do so).

I can't change the directory structure of my resources since it is structured by a ready made template. So I am stuck.

Does someone have a solution circumvent the issue of having too many segments?

Or at least disable Expression Engine from capturing and interpreting that page since the the links that I have that go over the maximum limit point to CSS files which don't need EE interpretation.

5
  • The maximum number of segments is 9. Give us more details, please. Maybe we can find an alternative.
    – Sobral
    Jul 24 '14 at 13:06
  • I'm unclear, are these files on the server and not requests that ExpressionEngine should be handling? Jul 24 '14 at 18:28
  • @sobral The segments that I have is 10 Jul 25 '14 at 4:25
  • @Derek The files are on the server. They are just simple CSS files that don't need EE processing. Jul 25 '14 at 4:25
  • See Johnathan Waters answer below then, it sounds like you have a server config issue. ExpressionEngine is not involved in files served outside the application. If his answer does not help, I suggest editing your question to include your .htaccess. Jul 26 '14 at 15:21
1

If you have structured you htaccess like the htaccess example. ExpressionEngine will not be consulted when accessing folders or files on your server.

These two lines in the htaccess are important

    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d

These make sure that if you are accessing a folder or file (like your css files), then do not have ExpressionEngine parse it. This essentially means there is no limit to your segments.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.