Feature #3306

Flush routes cache automatically on class file modifications

Added by Robert Lemke about 4 years ago. Updated 14 days ago.

Status:Accepted Start date:2009-05-14
Priority:Should have Due date:
Assignee:Robert Lemke % Done:

0%
Category:MVC
Target version:-
PHP Version: Complexity:
Has patch:
Votes: 1 (View)

Description

If a class containing a route part handler is changed, we also need to flush the routes cache because other routes might match now.

Related issues

related to TYPO3.Flow - Task #2117: Clean up bootstrap Resolved 2008-11-11
related to TYPO3.Flow - Bug #2974: Aspect / Proxy Cache is not emptied automatically if an i... New 2009-03-25
related to TYPO3.Flow - Feature #5849: Rebuild proxy classes if security policy changes Resolved 2009-12-28
related to TYPO3.Flow - Bug #33811: Not all caches are flushed (automatically) if needed Resolved 2012-02-09

Associated revisions

Revision 98343cbb
Added by Robert Lemke almost 4 years ago

For the FLOW3 distribution added a sub route to the Welcome package subroutes. If the Welcome package is installed, its fallback route becomes active and displays a meaningful welcome screen.

  • FLOW3: (MVC) For now disabled the caching of routes because they can lead to confusion during development. We can enable caching again once the routes cache is automatically flushed. Refs #3306
  • FLOW3: (MVC) The Router will now produce a log entry if no route matched.

Revision e71e8481
Added by Robert Lemke almost 4 years ago

For the FLOW3 distribution added a sub route to the Welcome package subroutes. If the Welcome package is installed, its fallback route becomes active and displays a meaningful welcome screen.

  • FLOW3: (MVC) For now disabled the caching of routes because they can lead to confusion during development. We can enable caching again once the routes cache is automatically flushed. Refs #3306
  • FLOW3: (MVC) The Router will now produce a log entry if no route matched.

History

#1
Updated by Robert Lemke about 4 years ago

  • Target version set to 1.0 alpha 1

#2
Updated by Robert Lemke almost 5 years ago

  • Status changed from New to Accepted
  • Assignee set to Robert Lemke

#3
Updated by Robert Lemke almost 4 years ago

  • Priority changed from Must have to Should have

#4
Updated by Robert Lemke almost 4 years ago

  • Target version changed from 1.0 alpha 1 to 283

Since r2437 routes are now uncached until this issue is resolved.

#5
Updated by Robert Lemke almost 4 years ago

  • Target version deleted (283)

Also available in: Atom PDF