[Deprecation] parsing of terms not working with cached pages

[rr-it]

The parsing of terms is broken by commit https://github.com/featdd/dpn_glossary/commit/3907441377fc5ebb631fac40bcb5d2c381f7a1e4 .

On first page load terms are correctly parsed and replaced. On second page load - this time as cached page by TYPO3 - none of the terms are replaced.

TYPO3: v7.6.31 dpn_glossary: v2.7.5

[featdd]

There seems different beheviour in typo3 versions and setup, in 8.7.x it didn't.

Had fixed this for 9 compatibility, could you test if this is also valid for 7.6?

greetings Daniel

[rr-it]

I did a test with both "contentPostProc-cached" and "contentPostProc-output" combined (https://github.com/featdd/dpn_glossary/commit/5b1080c5b8d8cbe3c48d5c11f9f025593ad80ef3): it works!

---

As far as I see, TYPO3 7.6 behaves like this.

contentPostProc-all fires:

• on all and every page load
• NOT working for COA_INT etc. -> fires before COA_INT etc. gets replaced with content.

contentPostProc-cached fires:

• for page that gets cached: on newly generating content (not on loading from cache) - result gets cached.
• (NOT working for COA_INT etc. -> COA_INT is not cached / fires before COA_INT etc. gets replaced with content.)

contentPostProc-output fires:

• for page with "noCache", COA_INT etc.: on every page load (also reprocessing the parts of a page that are from cache)
• for page that gets cached: on newly generating the content (and not loading from cache) - result gets not cached.
• page that gets cached: on forced reload (e.g. logged-in be-user forces reload in fe via [Ctrl]+[Shift]+[R])

My conclusion is to use both "contentPostProc-cached" and "contentPostProc-output" combined.

Drawbacks - unsolvable with availible hooks:

• page that gets cached and contains COA_INT: the page-content is processed on caching ("...-cached") and the whole page-content is reprocessed again on each page-load ("...-output").
• page that gets cached - on newly generating content (not on loading from cache): the page-content is processed on caching ("...-cached") and the whole page-content is immediately reprocessed a second time ("...-output").

[featdd]

hi @rr-it thanks for testing, guess I'll cherry pick this and push this into the next update.

[featdd]

merged into master 27682036c7c40dc4e1ccab7bff8273d69c0a92f1