-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TASK:T13] fix access restrictions stack #4161
Comments
51 tasks
dkd-kaehm
added a commit
to dkd-kaehm/ext-solr
that referenced
this issue
Sep 19, 2024
The tests are skipped temporary, to be able to recognize troubles due daily builds. The skipped tests within this commit must be fixed by issue: TYPO3-Solr#4160 Relates: TYPO3-Solr#4161, TYPO3-Solr#3995
dkd-kaehm
added a commit
to dkd-kaehm/ext-solr
that referenced
this issue
Sep 19, 2024
The tests are skipped temporary, to be able to recognize troubles due daily builds. The skipped tests within this commit must be fixed by issue: TYPO3-Solr#4160 Relates: TYPO3-Solr#4161, TYPO3-Solr#3995
dkd-kaehm
added a commit
that referenced
this issue
Sep 20, 2024
dkd-kaehm
added a commit
to dkd-kaehm/ext-solr
that referenced
this issue
Sep 30, 2024
This change fixes the access restrictions stack within TYPO3 13. There were multiple troubles in classes and in integration tests. The page indexer stack on live system runs in multiple isolated processes: 1. CLI 2. first FE request to get FE-groups 3. multiple FE requests to get real content from page for desired FE-groups combination unlike on integration test running the page indexer steps allways on single process. This requires to unset the produced state on each step of indexing process. The runtime cache was interfering between the steps and did things that had nothing to do withhin the own step. --- The main problem within access restriction stack on page indexing was the registration of Event-Listeners methods within `UserGroupDetector` with `#[AsEventListener]` on EXT:solr. Due of current troubles with circular dependencies the auto-wiring and auto-configuration was disabled in Servvices.yaml globally. It requires to enable this features manually for classes, which was done for `UserGroupDetector` class. Relates: TYPO3-Solr#3995 Fixes: TYPO3-Solr#4161
dkd-kaehm
added a commit
that referenced
this issue
Sep 30, 2024
This change fixes the access restrictions stack within TYPO3 13. There were multiple troubles in classes and in integration tests. The page indexer stack on live system runs in multiple isolated processes: 1. CLI 2. first FE request to get FE-groups 3. multiple FE requests to get real content from page for desired FE-groups combination unlike on integration test running the page indexer steps allways on single process. This requires to unset the produced state on each step of indexing process. The runtime cache was interfering between the steps and did things that had nothing to do withhin the own step. --- The main problem within access restriction stack on page indexing was the registration of Event-Listeners methods within `UserGroupDetector` with `#[AsEventListener]` on EXT:solr. Due of current troubles with circular dependencies the auto-wiring and auto-configuration was disabled in Servvices.yaml globally. It requires to enable this features manually for classes, which was done for `UserGroupDetector` class. Relates: #3995 Fixes: #4161
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PageIndexerTest::canIndexPageWithAccessProtectedContentIntoSolr
Current state:
#[AsEventListener]
are not called not only within integration tests.If it will not work like defined in Services.yaml within our tests, also without registering them by ListenerProvider in each test, all the
#[AsEventListener]
things must be duplicated in Services.yamlThe Autowire is disabled for classes using
#[AsEventListener]
.The text was updated successfully, but these errors were encountered: