-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error after cache warmup: [] operator not supported for strings #107
Comments
Have you got any other extensions installed? The |
yes, a few:
|
Honestly I don't think error is coming from my extension. There must be a different extension that modifies the |
I think the error is caused by your extension. The error message says that the selector is wrong. The selector must be an array and the index should be a string. So you can fix the error by doing this: |
The selector already is an array: https://github.com/codefog/contao-events_subscriptions/blob/master/dca/tl_member.php#L26 The key is not relevant, as you can see in any Contao core file: https://github.com/contao/contao/blob/5.x/core-bundle/contao/dca/tl_member.php#L85 |
To dump what's causing an error, you could try to dump the selector in file dd($GLOBALS['TL_DCA']['tl_member']['palettes']['__selector__']); |
I've discovered the following warning:
The relevant line (2nd line) is:
Can you recognize anything from this? |
sorry, @qzminski |
Dann stammt das doch aus meiner Erweiterung. In der Master besteht der Fehler nicht, nur im Branch der 4.13, da hier noch nicht mit dem PaletteManipulator gearbeitet wurde. Hab gerade nen neues Release veröffentlich 1.0.12 (ist exakt der Stand aus der Master). Probier das mal aus @rustykowski |
ja, sehr gut, kein warmup-Fehler mehr. |
Contao 4.13.49
contao-events_subscriptions 2.16.4
Exception in file var/cache/prod/contao/dca/tl_member.php on line 224[] operator not supported for strings
The content of line 224 is:
$GLOBALS['TL_DCA']['tl_member']['palettes']['__selector__'][] = 'subscription_enableLimit';
stacktrace:
The text was updated successfully, but these errors were encountered: