[bug] probably caching issue

[thomasrawiel]

There's probably some caching issue. I'm not sure whether it's in this extension or in the TYPO3 core.

evoweb/extender 10.1.1
TYPO3 12.4.28

I'm using evoweb/extender in EXT:powermailautocomplete.

When we clear the system cache (red bolt in Backend) the extended Domain Model isn't loaded but instead the original model is loaded - the attributes and getter functions of the extended model are missing

Powermail Field Model after clearing the system cache

However, after clearing the cache via installtool or cli the extended model is available again:

Do you have any idea where the problem could be?

(related)

[garbast]

It's just a wild guess, but somehow the red flash does not respect the additional spl class loaders which is needed to load the proxy file before instantiating the class.

Extender needs to spl_autoload_register the autoloader in RegisterAutoloaderEvent.php. This autoloader needs to be registered in front of every other class loader.

Once the autoloader is registered it searches for every class that needs to be loaded if a corresponding proxy is configured.

If a proxy is configured, the autoloader checks if a cached proxy file exists, if not the proxy file gets created. In either case it is then required.

For every class the autoloader doesn't find a config the loader is finished and the following loaders do their job.

Somehow between cache clear and autoloading the model, the config gets lost. And for now the reason is unclear. I don't know how to solve that. When ever i find this problem, my solution is the install toll, as i know, that after that it works.

If someone can hint me, i would gladly implement a solution for this bug.

[typoworx-de]

Having the same issue and just found this ticket. Same setup with powermail & traw/powermailautocomplete [EXT:powermailautocomplete] , but TYPO3 v13.

[thomasrawiel]

Having the same issue and just found this ticket. Same setup with powermail & traw/powermailautocomplete [EXT:powermailautocomplete] , but TYPO3 v13.

EXT:powermailautocomplete will be obsolete with probably the next major powermail update - I added all the functionality in this PR

[typoworx-de]

@thomasrawiel I just figured out how to fix/extend extender, to fix the issue right after TYPO3-caches have been flushed we also need to flush extbase_reflection cache. I had prototyped this on my local TYPO3 project inside the evoweb/extender code (\Evoweb\Extender\HooksClearCacheHook) and it works!

But there's one little bottle-neck. Due to the extbase-reflection caches being flushed (and not rebuild until new BE/FE request) the backend flash-message usually shown after the backend cache-flush menu-actions doesn't show up anymore. But at least there is no exception/error on this logged or shown.

I could provide this patch here as MR request?

[thomasrawiel]

I could provide this patch here as MR request?

Yea, I'm sure @garbast would like that

[typoworx-de]

@thomasrawiel sorry I thought I made it, but the initial PR turned out is not working yet. The problem is more complex due to the autoloader-override done inside extender.

[typoworx-de]

I invested some time today trying to get progress into the issue. Anybody wants to cross-test my possible patch? I've completely changed/updated my previous approach:
https://github.com/TYPOworx-GmbH/fork-evoweb-extender/tree/fix/issue-42

In my case this approach looks promising. Nevertheless while testing for 5 test-trials I had one try failing with the old error for some reason.

My test case:

1. clearing cache using Backend "flush all"
2. then load f.e. powermail form with powermailautocomplete (which uses evoweb extender to extend a powermail model)

Any feedback is welcome - just want to make shure it works this time :D

[thomasrawiel]

@typoworx-de

Tested with original from packagist: error is reproducible
I installed your PR from your repo - couldn't reproduce (yay)
Re-installed original (from your repo) - Error is reproducible
Again re-installed the patch - Error is still reproducible unfortunately

cleared cache via cli after every install.

Error occurs as soon as I flush all caches via backend and reload the form