Forums / Developer / Conflict between custom binaryhandler and stale cache

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Conflict between custom binaryhandler and stale cache

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Holger Marx

Friday 29 May 2009 4:39:49 am

Since I activate Stale Cache in my Exponential installation I run into trouble with my custom binaryhandlers.

This is the situation:

- Exponential 4.1.2
- two of my activated extensions contain one respectively two binaryhandlers
- binaryhandlers are activated in override/file.ini.append.php:

[BinaryFileSettings]
Handler[]
Handler[]=extension1aHandler
Handler[]=extension2aHandler
Handler[]=extension2bHandler
Repositories[]=kernel/classes
ExtensionRepositories[]=extension1
ExtensionRepositories[]=extension2

- stale cache is activated in override/file.ini.append.php:

[ClusteringSettings]
FileHandler=eZFS2FileHandler

When using the "old" cluster file handler "eZFSFileHandler" the extension binaryhandlers work fine, but now "eZFS2FileHandler" is activated the handlers aren't working anymore!

Can somebody tell me if there is a connection/relation between the new cluster file handler and BinaryFileSettings?