Conversation
Moving Migration into CoreBundle Starting to add Document class loader
# Conflicts: # .github/ci/files/config/bundles.php # bundles/AdminBundle/templates/admin/index/index.html.twig # bundles/CoreBundle/config/pimcore/default.yaml # bundles/CoreBundle/src/DependencyInjection/PimcoreCoreExtension.php # bundles/Web2PrintBundle/public/js/web2print.js # composer.json # models/DataObject/ClassDefinition/Data/AdvancedManyToManyObjectRelation.php # models/DataObject/ClassDefinition/Data/AdvancedManyToManyRelation.php # models/DataObject/ClassDefinition/Data/Classificationstore.php
Reverting routing changes to document controllers
Changed fixed document routes
Review Checklist
|
| $configs = $this->loadLegacyConfigs('web2print.php'); | ||
| if (count($configs) > 0) { | ||
| $web2PrintConfigs = Config::getWeb2PrintConfig(); | ||
| if (count($configs) > 0 && class_exists('Pimcore\Bundle\WebToPrintBundle\Config')) { |
There was a problem hiding this comment.
I am not to sure about changing this migration
There was a problem hiding this comment.
I'd wrap the entire function up() with a IF block that checks if it exists under the SettingStore and in case "skips" everything.
The down() is empty anyways.
Nevermind, i've misunderstood the issue.
There was a problem hiding this comment.
I am not sure how this check should look like. Do you have an example?
kingjia90
left a comment
There was a problem hiding this comment.
Found some minor issues after a quick check, but overall seems working fine
| $configs = $this->loadLegacyConfigs('web2print.php'); | ||
| if (count($configs) > 0) { | ||
| $web2PrintConfigs = Config::getWeb2PrintConfig(); | ||
| if (count($configs) > 0 && class_exists('Pimcore\Bundle\WebToPrintBundle\Config')) { |
There was a problem hiding this comment.
I'd wrap the entire function up() with a IF block that checks if it exists under the SettingStore and in case "skips" everything.
The down() is empty anyways.
Nevermind, i've misunderstood the issue.
|
One input but unrelated to the changes in the PR is: how should it behave when you remove/deactivate the web2print bundle and you still have printpage and printcontainers? What about a cleanup tool or a "archived/invalid documents" tree node and/or filter to hide them? And the generated PDFs and job file? Just wondering if uninstaller should take care of this or is up to the devs |
# Conflicts: # bundles/WebToPrintBundle/src/Controller/Document/PrintpageControllerBase.php
Adding missing translations Adding category to permissions in migration
|
I was wondering about this too, how we should handle those files, because with this PR we do not even have a fallback for the printpage or printcontainer in the core. @brusch wdyt? what should happen with printcontainer or printpage documents after the bundle gets uninstalled or disabled? |
# Conflicts: # .github/ci/files/config/bundles.php # doc/Development_Documentation/23_Installation_and_Upgrade/09_Upgrade_Notes/README.md
There was a problem hiding this comment.
Please remove this checkbox and related translation/docs
pimcore/bundles/WebToPrintBundle/public/js/settings.js
Lines 257 to 266 in 3eca81b
which was used to define if the web2print should be activated or not
Also in the migration needs to check wheter the checkbox was previously marked by that config
# Conflicts: # bundles/AdminBundle/src/Controller/Admin/SettingsController.php
Adding cleanup command Adjust migration to remove or add config Adjust installer to only remove permissions Updated documentation
kingjia90
left a comment
There was a problem hiding this comment.
found some other minor tweak to do while scanning through the last commit
# Conflicts: # bundles/WebToPrintBundle/src/Processor/HeadlessChrome.php
Only show enable bundle warning if bundle was marked as installed
Remove/add permissions in migration
doc/Development_Documentation/23_Installation_and_Upgrade/07_Updating_Pimcore/12_V10_to_V11.md
Outdated
Show resolved
Hide resolved
Adding deleting queries instead of doing it in the migration Adding consoleoutput on uninstall
kingjia90
left a comment
There was a problem hiding this comment.
I will commit these final suggestions and looks good to be merged
Changes in this pull request
Resolves #12525
Additional info
Moving web to print functionality into PimcoreWebToPrint
Able to install and uninstall via Installer. Permissions are in the Bundle
Moved translations into the bundle
Moved documents printabstract, printcontainer and printpage to bundle