Skip to content
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

Writeable parameter not set due to missing SettingsListener #406

Open
dlhck opened this issue Nov 27, 2023 · 3 comments
Open

Writeable parameter not set due to missing SettingsListener #406

dlhck opened this issue Nov 27, 2023 · 3 comments
Labels

Comments

@dlhck
Copy link
Contributor

dlhck commented Nov 27, 2023

Q A
Bug report? yes
Feature request? no
BC Break report? no
RFC? no
Branch? master

Description:

There appears to be an issue, specifically related to the handling of pimcore.settings['data-definitions-import-definition-writeable']. This parameter is crucial for adding new definitions in the admin UI, but it seems not to be set properly. The probable cause is the absence of an implementation of a SettingsListener which is essential for initializing and setting such parameters.

Steps to Reproduce

  • Install and configure the w-vision DataDefinitions module on a Pimcore instance.
  • Navigate to the import or export definition panel, attempting to add a new definition.
  • Observe the failure or inability to add new definitions.

Expected Behavior

The admin UI should allow the addition of new data definitions seamlessly, with the data-definitions-import-definition-writeable parameter being set correctly.

Actual Behavior

The data-definitions-import-definition-writeable parameter is not set, preventing the addition of new definitions in the admin UI.

Possible Solution

For reference on how other bundles integrate the SettingsListener, see this example in the Pimcore repository: Pimcore CustomReportsBundle SettingsListener Implementation. Implementing a similar SettingsListener in the DataDefinitions module could resolve this issue.

@twin-elements
Copy link

@davidhoeck How did you solve this problem?

@dlhck
Copy link
Contributor Author

dlhck commented Apr 8, 2024

@twin-elements added a custom settings listener in our app which sets the parameters to true. of course just a workaround, because there needs to be a check of the storage is writeable or not.

@twin-elements
Copy link

@davidhoeck Thank you for your quick response :)

@dkarlovi dkarlovi added the bug label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants