I was thinking:
If the extension does not exist or if the extension is disabled,
It would send a 303 See Other to the index.php or other significant place.
Anyway, If we may get a problem like that, I think it's better if we create a page for the extensions. Some place (not the index.php... ext.php, as an example) to where all the requests to extension pages go. That pages makes sure that the extension is there and activated and then includes the extension information for execution.
[RFC] New front pages in extensions
Re: [RFC] New front pages in extensions
I'm pro-front-controller. Having it just for extensions at first seems like a good idea. At some point we may want everything routed through one.
- imkingdavid
- Registered User
- Posts: 1050
- Joined: Thu Jul 30, 2009 12:06 pm
Re: [RFC] New front pages in extensions
Via index.php (which I think is best) or via something like ext.php (like brunoais suggested)?igorw wrote:I'm pro-front-controller. Having it just for extensions at first seems like a good idea. At some point we may want everything routed through one.