Improvement description

• Check github actions (static analysis, codeception, ...) for supported php versions

See pimcore/pimcore#12761 for details

Improvement description

Pimcore\Config\Config will be removed with this pr: pimcore/pimcore#12911

Adapt the changes in getConfiguration(), be aware: should still work with Pimcore 10.5 too

Improvement description

The available portlets are hardcoded:

Would be nice to be able to extend the list of available portlets, in case custom ones were added.

Improvement description

follow up #78

or add a specific permission to it

... maybe better write them into var directory

namespace should be Pimcore\Bundle\PerspectiveEditorBundle
Bundlename then PimcorePerspectiveEditorBundle

not 0/1

something like that:

then activate d&d to move between folders.

and allow other bundles to inject toolbar entries somehow.

Expected behavior

We should create views and be able to add them on the left or right panel in the perspective editor.

Actual behavior

I can only add documents, no asset, objects or custom views. Everytime I try, I get the message seen in the image.

Steps to reproduce

Env used : Pimcore 10.2.1
I installed the Perspective editor plugin (no other plugin installed, just present but not installed).
No complex code has been added.

I tried to install this pluging twice, I checked the files permissions.. can't find the issue... Is it a bug ? I never tried this plugin before...
I can't reproduce it on the demo.pimcore.com system as perspective configuration is read-only for the user superuser.

to indicate not-saved changes

Improvement description

...

Expected behavior

Not possible to add classes in perspectives editor

Actual behavior

Like mentioned here: pimcore/pimcore#10463

its currently not possible to add classes via perspectives editor, so we can not create a working perspective

Steps to reproduce

• Open Perspective Editor
• No option available to add classes

Expected behavior

Having multiple views of type object defined, selecting any of them sould display the view's settings without JS errors.
Also, settings must not be lost.

Actual behavior

Having a view of type object open, selecting another view from the list and going back to previous one, a JS error is thrown:
"Uncaught TypeError: classes.join is not a function"

Any selections in the MultiSelect menu "Allow Objects" are lost (no classes are selected).

The error happens here:

Logging the "classes" var at this point shows that on returning to a previously opened view classes parameter already is a string, as opposed to the first call where it was an array:

Steps to reproduce

• Set up at least two views, at least one of them of type object
• Select the object type view
• Select another view
• Select the same object view as before

JS error thrown in console, "Allowed Objects" select is empty.

Expected behavior

It's possible to open Perspectives Editor

Actual behavior

It's not possible to open Perspectives Editor.

Steps to reproduce

1. Go to demo.pimcore.com/admin
2. Try to open Perspectives Editor
3. Getting an Error: Attempted to call an undefined method named "getCustomViewConfig" of class "Pimcore\Tool".

same for dashboards

Improvement description

as soon as it is implemented for custom views and perspectives

see pimcore/pimcore#9330

Improvement description

...

... as with other places in pimcore like data object classes

Improvement description

challenge: make SQL-parts as Injection-proof as possible

Can you please add this bundle to Packagist so that one can install it via Composer without explicitly adding this repo in the repositories section of the composer.json?

generated structure looks like

            'extras' => [
                'hidden' => 0,
                'glossary' => 1,
                'redirects' => 1,
                'translations' => 1,
                'recyclebin' => 1,
                'plugins' => 1,
                'notesEvents' => 1,
                'applicationlog' => 1,
                'gdpr_data_extractor' => 1,
                'emails' => 1,
                'maintenance' => 1,
                'systemtools' => [
                    'hidden' => 1,
                    'phpinfo' => 1,
                    'opcache' => 1,
                    'requirements' => 1,
                    'serverinfo' => 1,
                    'database' => 1,
                    'fileexplorer' => 1
                ]
            ],

but it should be like

            'extras' => [
                'hidden' => 0,
                'items' => [
                    'glossary' => 1,
                    'redirects' => 1,
                    'translations' => 1,
                    'recyclebin' => 1,
                    'plugins' => 1,
                    'notesEvents' => 1,
                    'applicationlog' => 1,
                    'gdpr_data_extractor' => 1,
                    'emails' => 1,
                    'maintenance' => 1,
                    'systemtools' => [
                        'hidden' => 1,
                        'phpinfo' => 1,
                        'opcache' => 1,
                        'requirements' => 1,
                        'serverinfo' => 1,
                        'database' => 1,
                        'fileexplorer' => 1
                    ]
                ]

            ],

Improvement description

Use the same translations and icons as in the "Add Portlet-Menu" from the dashboard

to make names more unique...

• PerspectiveEditor
• ViewEditor
• PerspectiveViewHelper

... for better overview

@fashxp where would the final space for this plugin be?

Files -> perspectives -> Editor?
Tools -> Perspective Editor?

Expected behavior

File > Dashboard should be saving correctly and displaying only the existing and correct dashboard.
Forbidden Portlets should be saved and reloadable.

Actual behavior

In this case there's an hidden/unnamed dashboard as in the picture

The forbidden dashboards (which should be renamed forbidden Portlets?) is not saving/loading the checked value

Steps to reproduce

Just add some new dashboard and eventually flag some checkbox in the Forbidden Dashboards and save.

Then if you reopen the editor, you see that the dashboard name is changed to "Root" and in the "File > Dashboard" it appears wrongly as empty element. The forbidden dashboards is also not properly saved(?), so anything you flagged is not there anymore.

Improvement description

https://github.com/pimcore/pimcore/pull/12633/files#diff-736172470d63f25a8d80e1457a5f8ef0ce9af5d798239430886fe1a410842aa3

Replace pimcore.plugin.broker.fireEvent with dispatchEvent and make events compatible for plugins like:
#81

Change dependency from pimcore/pimcore to version 10.5

Improvement description

Since Piwik is now Matomo and the Matomo integration was removed, it shouldn't be possible to add "Piwik" to the forbidden dashboards:

check for unique element of "documents", "assets" and objects (allow multiple customviews) on save

support configs like:

        'toolbar' => [
            'file' => TRUE,
            'extras' => FALSE,
            'marketing' => 0,
            'settings' => 0,
            'search' => 1,
            'ecommerce' => 1
        ]

Improvement description

When clicking on the save button, every perspective or custom view is saved to the configured write target. Even if nothing has changed at all.

1. Save only changed perspectives or custom views to the configured write target
2. Adapt the GUI to reflect other configuration GUIs in pimcore, like Datahub / GraphQL
   2.1 e.g. add Tabs

Expected behavior

Having a checkbox "hidden" correspondaing to the yaml option hidding.

Actual behavior

The is no such checkbox on the GUI

Steps to reproduce

On the Pimcore demo, open the DAM perspective:

On the yaml config:

Thanks.

Expected behavior

When renaming a perspective, the file name gets updated.

Actual behavior

The file is deleted.

Steps to reproduce

Just renamed a perspective from Matomo to matomo, as I wanted to stick to naming conventions (based on the default perspective). This effectively deleted the file.

Task description

follow up #81

Check if addEventListenerCompatibilityForPlugins exist

https://github.com/pimcore/perspective-editor/blob/1.x/src/Resources/public/js/pimcore/perspective/events.js#L32

Improvement description

TODOs

• define what to test
• estimate efforts

1. Take a Database dump from Env 1
2. Import said database to Env 2 (and clear caches)
3. Adjust perspectives using this editor
4. Commit and deploy the updated configuration file in Env 1.

Result:
All perspectives and views are blank in Env 1.

Tested in Pimcore 6.8.11 and 6.9.1 on PHP 7.4

change to kernel.project_dir and make symfony 4.2 min requirement