From db5036420c0bdc7e59de281ff4cfb3730634612c Mon Sep 17 00:00:00 2001 From: Michael Telgmann Date: Fri, 25 Aug 2023 09:21:39 +0200 Subject: [PATCH 1/4] fix: Adjust links of shopware main repository, so they are directing to the new organisation --- exampleplugins/5.2/SeoExample/plugin.xml | 2 +- exampleplugins/5.2/SeoExample52/plugin.xml | 2 +- .../5.2/SwagAttributeSlider/plugin.xml | 2 +- exampleplugins/5.2/SwagBannerApi/plugin.xml | 2 +- .../5.2/SwagCustomDetailTheme/plugin.xml | 2 +- .../5.2/SwagCustomListingTheme/plugin.xml | 4 ++-- .../5.2/SwagCustomStatistics/plugin.xml | 2 +- .../SwagDigitalPublishingSample/plugin.xml | 2 +- exampleplugins/5.2/SwagESBlog/plugin.xml | 2 +- exampleplugins/5.2/SwagESProduct/plugin.xml | 2 +- .../5.2/SwagEmotionPresetExample/plugin.xml | 2 +- exampleplugins/5.2/SwagEvents/plugin.xml | 2 +- .../5.2/SwagExtendArticleResource/plugin.xml | 2 +- .../5.2/SwagExtendCustomProducts/plugin.xml | 2 +- .../5.2/SwagExtendCustomer/plugin.xml | 2 +- .../5.2/SwagGlobalVariables/plugin.xml | 2 +- .../SwagLastRegistrationsWidget/plugin.xml | 2 +- exampleplugins/5.2/SwagMd5Reversed/plugin.xml | 2 +- exampleplugins/5.2/SwagModel/plugin.xml | 2 +- .../5.2/SwagPaymentExample/plugin.xml | 2 +- .../5.2/SwagPluginSystem/plugin.xml | 2 +- .../5.2/SwagProductAssoc/Resources/menu.xml | 2 +- .../5.2/SwagProductAssoc/plugin.xml | 2 +- .../5.2/SwagProductBasic/Resources/menu.xml | 2 +- .../5.2/SwagProductBasic/plugin.xml | 2 +- .../5.2/SwagProductDetail/Resources/menu.xml | 2 +- .../5.2/SwagProductDetail/plugin.xml | 2 +- .../5.2/SwagProductListing/Resources/menu.xml | 2 +- .../5.2/SwagProductListing/plugin.xml | 2 +- .../Resources/menu.xml | 2 +- .../SwagProductListingExtension/plugin.xml | 2 +- .../5.2/SwagReCaptcha/Resources/config.xml | 2 +- exampleplugins/5.2/SwagReCaptcha/plugin.xml | 2 +- exampleplugins/5.2/SwagShoeSize/plugin.xml | 2 +- .../SwagSloganOfTheDay/Resources/config.xml | 2 +- exampleplugins/5.2/SwagTestExample/plugin.xml | 2 +- .../5.2/SwagTutorialTheme/plugin.xml | 2 +- .../5.2/SwagVimeoElement/plugin.xml | 2 +- source/_layouts/start.twig.html | 2 +- source/_partials/github_footer.twig | 4 ++-- .../blog/_posts/2015-01-28-phpbenelux-2015.md | 2 +- .../_posts/2016-01-26-shopware-environment.md | 4 ++-- .../_posts/2016-02-11-hackathon-2016-1.md | 3 +-- source/blog/_posts/2016-02-26-umask.md | 4 +--- .../_posts/2016-09-12-99-paper-cuts-status.md | 5 ++--- .../blog/_posts/2016-12-09-new-cart-bundle.md | 2 +- .../_posts/2017-07-24-seo-urls-in-plugins.md | 10 +++++----- .../blog/_posts/2017-10-23-meetnext-recap.md | 2 +- source/community/index.html | 2 +- source/designers-guide/datepicker/index.md | 4 ++-- .../index.md | 2 +- .../backend-components/basics/index.md | 2 +- .../implementing-your-own-captcha/index.md | 4 ++-- .../lightweight-backend-modules/index.md | 2 +- source/developers-guide/phpstorm/index.md | 3 +-- .../plugin-configuration/index.md | 8 ++++---- .../plugin-extension-by-plugin/index.md | 2 +- .../plugin-guidelines/index.md | 2 +- .../plugin-lastregistrations-widget/index.md | 3 +-- .../plugin-quick-start/index.md | 18 ++++++++--------- .../shopware-5-plugin-update-guide/index.md | 2 +- .../index.md | 20 +++++++++---------- .../vagrant-phpstorm/index.md | 6 +++--- .../installation-guide/index.md | 2 +- .../system-requirements/index.md | 2 +- 65 files changed, 97 insertions(+), 103 deletions(-) diff --git a/exampleplugins/5.2/SeoExample/plugin.xml b/exampleplugins/5.2/SeoExample/plugin.xml index b524b51932..f3bc5a212b 100644 --- a/exampleplugins/5.2/SeoExample/plugin.xml +++ b/exampleplugins/5.2/SeoExample/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SeoExample52/plugin.xml b/exampleplugins/5.2/SeoExample52/plugin.xml index 2f4a2589af..28e12e9d97 100644 --- a/exampleplugins/5.2/SeoExample52/plugin.xml +++ b/exampleplugins/5.2/SeoExample52/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.2/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagAttributeSlider/plugin.xml b/exampleplugins/5.2/SwagAttributeSlider/plugin.xml index 4cba763178..2e58d7836f 100644 --- a/exampleplugins/5.2/SwagAttributeSlider/plugin.xml +++ b/exampleplugins/5.2/SwagAttributeSlider/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagBannerApi/plugin.xml b/exampleplugins/5.2/SwagBannerApi/plugin.xml index c59d9de414..1607e5cc1b 100644 --- a/exampleplugins/5.2/SwagBannerApi/plugin.xml +++ b/exampleplugins/5.2/SwagBannerApi/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> 1.0.0 diff --git a/exampleplugins/5.2/SwagCustomDetailTheme/plugin.xml b/exampleplugins/5.2/SwagCustomDetailTheme/plugin.xml index e00902612b..0cff337701 100644 --- a/exampleplugins/5.2/SwagCustomDetailTheme/plugin.xml +++ b/exampleplugins/5.2/SwagCustomDetailTheme/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagCustomListingTheme/plugin.xml b/exampleplugins/5.2/SwagCustomListingTheme/plugin.xml index 91fc12bc64..38eb9108c0 100644 --- a/exampleplugins/5.2/SwagCustomListingTheme/plugin.xml +++ b/exampleplugins/5.2/SwagCustomListingTheme/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> @@ -18,4 +18,4 @@ Erstveröffentlichung First release - \ No newline at end of file + diff --git a/exampleplugins/5.2/SwagCustomStatistics/plugin.xml b/exampleplugins/5.2/SwagCustomStatistics/plugin.xml index 8acb25ba6f..ff9f9e8837 100644 --- a/exampleplugins/5.2/SwagCustomStatistics/plugin.xml +++ b/exampleplugins/5.2/SwagCustomStatistics/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagDigitalPublishingSample/plugin.xml b/exampleplugins/5.2/SwagDigitalPublishingSample/plugin.xml index 8ac7b93726..a0c43da619 100644 --- a/exampleplugins/5.2/SwagDigitalPublishingSample/plugin.xml +++ b/exampleplugins/5.2/SwagDigitalPublishingSample/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagESBlog/plugin.xml b/exampleplugins/5.2/SwagESBlog/plugin.xml index 44b4c42907..da2ab9343f 100644 --- a/exampleplugins/5.2/SwagESBlog/plugin.xml +++ b/exampleplugins/5.2/SwagESBlog/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagESProduct/plugin.xml b/exampleplugins/5.2/SwagESProduct/plugin.xml index 1bdb487d07..c063b90914 100644 --- a/exampleplugins/5.2/SwagESProduct/plugin.xml +++ b/exampleplugins/5.2/SwagESProduct/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagEmotionPresetExample/plugin.xml b/exampleplugins/5.2/SwagEmotionPresetExample/plugin.xml index 6040e217eb..16d22a0ef9 100644 --- a/exampleplugins/5.2/SwagEmotionPresetExample/plugin.xml +++ b/exampleplugins/5.2/SwagEmotionPresetExample/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagEvents/plugin.xml b/exampleplugins/5.2/SwagEvents/plugin.xml index 9fd1c67f76..ac708ca9c5 100644 --- a/exampleplugins/5.2/SwagEvents/plugin.xml +++ b/exampleplugins/5.2/SwagEvents/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagExtendArticleResource/plugin.xml b/exampleplugins/5.2/SwagExtendArticleResource/plugin.xml index 28894b1dca..a227141c05 100644 --- a/exampleplugins/5.2/SwagExtendArticleResource/plugin.xml +++ b/exampleplugins/5.2/SwagExtendArticleResource/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> 1.0.0 diff --git a/exampleplugins/5.2/SwagExtendCustomProducts/plugin.xml b/exampleplugins/5.2/SwagExtendCustomProducts/plugin.xml index a09a2223fe..b39a8c1692 100644 --- a/exampleplugins/5.2/SwagExtendCustomProducts/plugin.xml +++ b/exampleplugins/5.2/SwagExtendCustomProducts/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagExtendCustomer/plugin.xml b/exampleplugins/5.2/SwagExtendCustomer/plugin.xml index 2f1224901e..f821b8e455 100644 --- a/exampleplugins/5.2/SwagExtendCustomer/plugin.xml +++ b/exampleplugins/5.2/SwagExtendCustomer/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagGlobalVariables/plugin.xml b/exampleplugins/5.2/SwagGlobalVariables/plugin.xml index 1c338980db..c9334c1c09 100644 --- a/exampleplugins/5.2/SwagGlobalVariables/plugin.xml +++ b/exampleplugins/5.2/SwagGlobalVariables/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagLastRegistrationsWidget/plugin.xml b/exampleplugins/5.2/SwagLastRegistrationsWidget/plugin.xml index a472c1b817..48b0ea6ccc 100644 --- a/exampleplugins/5.2/SwagLastRegistrationsWidget/plugin.xml +++ b/exampleplugins/5.2/SwagLastRegistrationsWidget/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagMd5Reversed/plugin.xml b/exampleplugins/5.2/SwagMd5Reversed/plugin.xml index b4f1df6a73..9aa0423c8d 100644 --- a/exampleplugins/5.2/SwagMd5Reversed/plugin.xml +++ b/exampleplugins/5.2/SwagMd5Reversed/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagModel/plugin.xml b/exampleplugins/5.2/SwagModel/plugin.xml index 23487871d5..96a0329952 100644 --- a/exampleplugins/5.2/SwagModel/plugin.xml +++ b/exampleplugins/5.2/SwagModel/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagPaymentExample/plugin.xml b/exampleplugins/5.2/SwagPaymentExample/plugin.xml index 77d1c978bd..abb5c337d2 100644 --- a/exampleplugins/5.2/SwagPaymentExample/plugin.xml +++ b/exampleplugins/5.2/SwagPaymentExample/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagPluginSystem/plugin.xml b/exampleplugins/5.2/SwagPluginSystem/plugin.xml index 55164ae98f..e148e0d0b0 100644 --- a/exampleplugins/5.2/SwagPluginSystem/plugin.xml +++ b/exampleplugins/5.2/SwagPluginSystem/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagProductAssoc/Resources/menu.xml b/exampleplugins/5.2/SwagProductAssoc/Resources/menu.xml index 2add73b032..42db3e20f4 100644 --- a/exampleplugins/5.2/SwagProductAssoc/Resources/menu.xml +++ b/exampleplugins/5.2/SwagProductAssoc/Resources/menu.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/exampleplugins/5.2/SwagProductAssoc/plugin.xml b/exampleplugins/5.2/SwagProductAssoc/plugin.xml index 555e9fad43..0e09d08f78 100644 --- a/exampleplugins/5.2/SwagProductAssoc/plugin.xml +++ b/exampleplugins/5.2/SwagProductAssoc/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagProductBasic/Resources/menu.xml b/exampleplugins/5.2/SwagProductBasic/Resources/menu.xml index 41a34be057..89e8d60ae2 100644 --- a/exampleplugins/5.2/SwagProductBasic/Resources/menu.xml +++ b/exampleplugins/5.2/SwagProductBasic/Resources/menu.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/exampleplugins/5.2/SwagProductBasic/plugin.xml b/exampleplugins/5.2/SwagProductBasic/plugin.xml index 69bc40d759..74abf184b3 100644 --- a/exampleplugins/5.2/SwagProductBasic/plugin.xml +++ b/exampleplugins/5.2/SwagProductBasic/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagProductDetail/Resources/menu.xml b/exampleplugins/5.2/SwagProductDetail/Resources/menu.xml index a43651f085..03bf3dc3ea 100644 --- a/exampleplugins/5.2/SwagProductDetail/Resources/menu.xml +++ b/exampleplugins/5.2/SwagProductDetail/Resources/menu.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/exampleplugins/5.2/SwagProductDetail/plugin.xml b/exampleplugins/5.2/SwagProductDetail/plugin.xml index 722259f7b5..1bea942f49 100644 --- a/exampleplugins/5.2/SwagProductDetail/plugin.xml +++ b/exampleplugins/5.2/SwagProductDetail/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagProductListing/Resources/menu.xml b/exampleplugins/5.2/SwagProductListing/Resources/menu.xml index 41a190ad19..ca1f54641f 100644 --- a/exampleplugins/5.2/SwagProductListing/Resources/menu.xml +++ b/exampleplugins/5.2/SwagProductListing/Resources/menu.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/exampleplugins/5.2/SwagProductListing/plugin.xml b/exampleplugins/5.2/SwagProductListing/plugin.xml index 63177eac37..fa9f7652ea 100644 --- a/exampleplugins/5.2/SwagProductListing/plugin.xml +++ b/exampleplugins/5.2/SwagProductListing/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagProductListingExtension/Resources/menu.xml b/exampleplugins/5.2/SwagProductListingExtension/Resources/menu.xml index 7f9b5993a4..cb2397f6cb 100644 --- a/exampleplugins/5.2/SwagProductListingExtension/Resources/menu.xml +++ b/exampleplugins/5.2/SwagProductListingExtension/Resources/menu.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/exampleplugins/5.2/SwagProductListingExtension/plugin.xml b/exampleplugins/5.2/SwagProductListingExtension/plugin.xml index f12ee6402f..a56309d923 100644 --- a/exampleplugins/5.2/SwagProductListingExtension/plugin.xml +++ b/exampleplugins/5.2/SwagProductListingExtension/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagReCaptcha/Resources/config.xml b/exampleplugins/5.2/SwagReCaptcha/Resources/config.xml index 1773064724..20390ab5a6 100644 --- a/exampleplugins/5.2/SwagReCaptcha/Resources/config.xml +++ b/exampleplugins/5.2/SwagReCaptcha/Resources/config.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> sitekey diff --git a/exampleplugins/5.2/SwagReCaptcha/plugin.xml b/exampleplugins/5.2/SwagReCaptcha/plugin.xml index f1756a02b1..6a2ffe508c 100644 --- a/exampleplugins/5.2/SwagReCaptcha/plugin.xml +++ b/exampleplugins/5.2/SwagReCaptcha/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagShoeSize/plugin.xml b/exampleplugins/5.2/SwagShoeSize/plugin.xml index abeb093981..ad648a51ba 100644 --- a/exampleplugins/5.2/SwagShoeSize/plugin.xml +++ b/exampleplugins/5.2/SwagShoeSize/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagSloganOfTheDay/Resources/config.xml b/exampleplugins/5.2/SwagSloganOfTheDay/Resources/config.xml index 663ffa79ba..350c297d8f 100644 --- a/exampleplugins/5.2/SwagSloganOfTheDay/Resources/config.xml +++ b/exampleplugins/5.2/SwagSloganOfTheDay/Resources/config.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> swagSloganContent diff --git a/exampleplugins/5.2/SwagTestExample/plugin.xml b/exampleplugins/5.2/SwagTestExample/plugin.xml index e90951d6da..4ab03f1afd 100644 --- a/exampleplugins/5.2/SwagTestExample/plugin.xml +++ b/exampleplugins/5.2/SwagTestExample/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagTutorialTheme/plugin.xml b/exampleplugins/5.2/SwagTutorialTheme/plugin.xml index 96267d277a..e34bb59461 100644 --- a/exampleplugins/5.2/SwagTutorialTheme/plugin.xml +++ b/exampleplugins/5.2/SwagTutorialTheme/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.2/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/exampleplugins/5.2/SwagVimeoElement/plugin.xml b/exampleplugins/5.2/SwagVimeoElement/plugin.xml index 0ddbd93aa6..5d69af9c38 100644 --- a/exampleplugins/5.2/SwagVimeoElement/plugin.xml +++ b/exampleplugins/5.2/SwagVimeoElement/plugin.xml @@ -1,6 +1,6 @@ + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/source/_layouts/start.twig.html b/source/_layouts/start.twig.html index 6e4d6a0ab5..bd5ccde62a 100644 --- a/source/_layouts/start.twig.html +++ b/source/_layouts/start.twig.html @@ -239,7 +239,7 @@
Style tile
- +
GitHub
 diff --git a/source/_partials/github_footer.twig b/source/_partials/github_footer.twig index c574f1d400..77ce7dce6d 100644 --- a/source/_partials/github_footer.twig +++ b/source/_partials/github_footer.twig @@ -8,7 +8,7 @@ Now it's your turn to check out the current development state. We published a branch on GitHub which contains all the changes regarding our research topics.

- + @@ -24,4 +24,4 @@

- \ No newline at end of file + diff --git a/source/blog/_posts/2015-01-28-phpbenelux-2015.md b/source/blog/_posts/2015-01-28-phpbenelux-2015.md index d74ecc4cb0..f314048cbb 100644 --- a/source/blog/_posts/2015-01-28-phpbenelux-2015.md +++ b/source/blog/_posts/2015-01-28-phpbenelux-2015.md @@ -36,7 +36,7 @@ After his talk I felt temped to rewrite my json API endpoints in go. Decorating Applications with Stack by Beau D. Simensen: -Beau explained the ideas behind composing HttpKernelInterface middlewares and the stack project. Shopware is HttpKernelInterface compatible since version 4.2. +Beau explained the ideas behind composing HttpKernelInterface middlewares and the stack project. Shopware is HttpKernelInterface compatible since version 4.2. Say What? Ubiquitous Language and You!, also by Beau: diff --git a/source/blog/_posts/2016-01-26-shopware-environment.md b/source/blog/_posts/2016-01-26-shopware-environment.md index 45952bac59..74a607de5f 100644 --- a/source/blog/_posts/2016-01-26-shopware-environment.md +++ b/source/blog/_posts/2016-01-26-shopware-environment.md @@ -17,7 +17,7 @@ This can be used to load different config files and to separate cache files. ## How the environment is handled -This environment variable is picked by [`shopware.php`](https://github.com/shopware/shopware/blob/5.2/shopware.php#L92) and [`bin/console`](https://github.com/shopware/shopware/blob/5.2/bin/console#L34) and then propagated to the kernel: +This environment variable is picked by [`shopware.php`](https://github.com/shopware5/shopware/blob/5.2/shopware.php#L92) and [`bin/console`](https://github.com/shopware5/shopware/blob/5.2/bin/console#L34) and then propagated to the kernel: ```php $environment = getenv('SHOPWARE_ENV') ?: 'production'; @@ -51,7 +51,7 @@ var ## Config loading -The config loading order is defined in [engine/Shopware/Configs/Default.php](https://github.com/shopware/shopware/blob/cbafdd378de2bf5afab7504a90a2bc184ebbd681/engine/Shopware/Configs/Default.php#L3). +The config loading order is defined in [engine/Shopware/Configs/Default.php](https://github.com/shopware5/shopware/blob/cbafdd378de2bf5afab7504a90a2bc184ebbd681/engine/Shopware/Configs/Default.php#L3). The config loader looks for a file named `config_[ENVIRONMENT].php` first. If that file does not exists it falls back to `config.php`. On my development machine all my installations contain a file named `config_dev.php`. diff --git a/source/blog/_posts/2016-02-11-hackathon-2016-1.md b/source/blog/_posts/2016-02-11-hackathon-2016-1.md index 96fe2202a0..e569ea324f 100644 --- a/source/blog/_posts/2016-02-11-hackathon-2016-1.md +++ b/source/blog/_posts/2016-02-11-hackathon-2016-1.md @@ -226,7 +226,7 @@ your complex shopware project can now have a dependency to the `shopware/shopwar To archive this, a few changes in the Shopware core had to be made as no files should be created and modified inside the vendor/shopware/shopware directory. So all user generated files, like plugins, user themes, downloads etc. had to be -moved up the the project level. +moved up the project level.
@@ -257,4 +257,3 @@ there is little control over password quality and change intervals. In this proj to have a secure and unified login, that doesn't need further password changes on the machines itself.
- diff --git a/source/blog/_posts/2016-02-26-umask.md b/source/blog/_posts/2016-02-26-umask.md index ddbc3f408e..44b895af95 100644 --- a/source/blog/_posts/2016-02-26-umask.md +++ b/source/blog/_posts/2016-02-26-umask.md @@ -163,7 +163,7 @@ Also the permissions of cache files are now using the umask instead of hard code ] ``` -You can find all the changes in the [Github Pull Request](https://github.com/shopware/shopware/pull/410). +You can find all the changes in the [Github Pull Request](https://github.com/shopware5/shopware/pull/410). This changes will be included in the upcoming Shopware 5.1.4 release. @@ -172,5 +172,3 @@ This changes will be included in the upcoming Shopware 5.1.4 release. Now that Shopware respects the umask for all cache files there no need to configure individual file creation permissions anymore. Just set the umask and Shopware will create files accordingly. The umask can be set in your Apache or PHP-FPM configuration, or by calling `umask(0077);` in you projects `config.php`. - - diff --git a/source/blog/_posts/2016-09-12-99-paper-cuts-status.md b/source/blog/_posts/2016-09-12-99-paper-cuts-status.md index 0fa7251ea3..f0ca0c1643 100644 --- a/source/blog/_posts/2016-09-12-99-paper-cuts-status.md +++ b/source/blog/_posts/2016-09-12-99-paper-cuts-status.md @@ -8,10 +8,10 @@ We are now on day 8 of our project 99 Papercuts, with 7 days to go. From now until Monday, 19th September, you can participate in our 99 Papercuts Project and make Shopware better - one papercut at a time. -The feedback so far has been pretty good; we've already received several contributions and [merged](https://github.com/shopware/shopware/pulls?q=is%3Apr+%5BPapercut%5D+is%3Aclosed) a good amount of pull requests. +The feedback so far has been pretty good; we've already received several contributions and [merged](https://github.com/shopware5/shopware/pulls?q=is%3Apr+%5BPapercut%5D+is%3Aclosed) a good amount of pull requests. We also noticed increased activity in our [IRC Channel](/community/irc/), where you can get in touch with the Community. -You can help by reviewing the [open](https://github.com/shopware/shopware/pulls?utf8=%E2%9C%93&q=%3Apr%20is%3Aopen%20%5BPapercut%5D) pull requests and providing feedback. +You can help by reviewing the [open](https://github.com/shopware5/shopware/pulls?utf8=%E2%9C%93&q=%3Apr%20is%3Aopen%20%5BPapercut%5D) pull requests and providing feedback. ## New Pull Request Workflow @@ -38,4 +38,3 @@ Tickets have already been created in our Issue Tracker, and we have no schedulin Now it's your turn. Find a papercut bug that bothers you and try to fix it. - diff --git a/source/blog/_posts/2016-12-09-new-cart-bundle.md b/source/blog/_posts/2016-12-09-new-cart-bundle.md index 3abe5331af..80237ec6b4 100644 --- a/source/blog/_posts/2016-12-09-new-cart-bundle.md +++ b/source/blog/_posts/2016-12-09-new-cart-bundle.md @@ -16,7 +16,7 @@ Since the last Community Day, we've received several questions about Shopware's - *How far are you with the development* - *Which new features come with the new shopping cart?* -At the Community Day, we also announced that we are striving for open development in the refactoring process in order to get as much feedback as possible and to be able to work more closely with other developers and partners. We want to realize this now by sharing the first concept of the new shopping cart. You can see the development process on Github, where we created a new repository which allows the Community to create pull requests and issues. The new repository contains a new bundle in `/engine/Shopware/Bundle/CartBundle`, which contains a first proof of concept for a new cart process. This first concept can change steadily due to growing requirements and that refactoring will be an ongoing process. The first features we implemented are the following: +At the Community Day, we also announced that we are striving for open development in the refactoring process in order to get as much feedback as possible and to be able to work more closely with other developers and partners. We want to realize this now by sharing the first concept of the new shopping cart. You can see the development process on Github, where we created a new repository which allows the Community to create pull requests and issues. The new repository contains a new bundle in `/engine/Shopware/Bundle/CartBundle`, which contains a first proof of concept for a new cart process. This first concept can change steadily due to growing requirements and that refactoring will be an ongoing process. The first features we implemented are the following: - Add, delete and change quantity of product line items - Add and delete percentage-based vouchers - First concept for partial delivery diff --git a/source/blog/_posts/2017-07-24-seo-urls-in-plugins.md b/source/blog/_posts/2017-07-24-seo-urls-in-plugins.md index 32485d2bce..e342eaff03 100644 --- a/source/blog/_posts/2017-07-24-seo-urls-in-plugins.md +++ b/source/blog/_posts/2017-07-24-seo-urls-in-plugins.md @@ -79,7 +79,7 @@ As each of the options mentioned above requires slightly different plugin logic, In **Shopware 5.3** we implemented a new event to SEO URL generation using the cronjob.
-Everytime the cronjob `RefreshSeoIndex` is triggered, the method `onRefreshSeoIndex` in [engine/Shopware/Plugins/Default/Core/RebuildIndex/Bootstrap.php](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Plugins/Default/Core/RebuildIndex/Bootstrap.php#L134) is called.
+Everytime the cronjob `RefreshSeoIndex` is triggered, the method `onRefreshSeoIndex` in [engine/Shopware/Plugins/Default/Core/RebuildIndex/Bootstrap.php](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Plugins/Default/Core/RebuildIndex/Bootstrap.php#L134) is called.
It now contains a new notify event called `Shopware_CronJob_RefreshSeoIndex_CreateRewriteTable`, which we will use to add our own SEO URL generation process. The event is called once for each shop after every other SEO URL (e.g. Products, Categories, ...) has been generated for this shop. @@ -110,7 +110,7 @@ This option does **not** mean, that with each and every request the SEO URLs are You can configure the refresh interval in the backend under `Configuration > Cache/performance > Settings > SEO > Refresh strategy`. Basically, whenever a request is sent to the shop and the response is about to be sent back, Shopware checks if it's time to re-generate the SEO URLs. -In only that case (refresh strategy is 'live' AND the interval has passed), the method `sCreateRewriteTable` from our core module [sRewriteTable](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Core/sRewriteTable.php#L220) is called. +In only that case (refresh strategy is 'live' AND the interval has passed), the method `sCreateRewriteTable` from our core module [sRewriteTable](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Core/sRewriteTable.php#L220) is called. This method only generates the SEO URLs for the **currently** active shop. @@ -153,7 +153,7 @@ You can choose a batch size, which defines how many URLs should be generated wit We want to have our own progress bar at the bottom of the window now to generate our SEO URLs for the currently selected shop in batch mode. -First of all we have to extend the file [themes/Backend/ExtJs/backend/performance/view/main/multi_request_tasks.js](https://github.com/shopware/shopware/blob/5.3/themes/Backend/ExtJs/backend/performance/view/main/multi_request_tasks.js#L83). +First of all we have to extend the file [themes/Backend/ExtJs/backend/performance/view/main/multi_request_tasks.js](https://github.com/shopware5/shopware/blob/5.3/themes/Backend/ExtJs/backend/performance/view/main/multi_request_tasks.js#L83). We have to extend the property 'seo', which contains all progress bars, their snippets and, most important, the request URL to be called for each batch call to generate the SEO URLs. So, let's overwrite the ExtJs window. @@ -254,7 +254,7 @@ Now there's one more thing missing. Once we select a shop in the backend SEO module, an AJAX call is sent to collect the total counts of URLs to be created with each progress bar. Our glossary URLs are not collected yet, so the module can't handle our glossary URLs properly yet. -To collect the URLs, the `getCountAction` of the [SEO controller](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Plugins/Default/Core/RebuildIndex/Controllers/Seo.php#L72) is called. +To collect the URLs, the `getCountAction` of the [SEO controller](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Plugins/Default/Core/RebuildIndex/Controllers/Seo.php#L72) is called. Thankfully it provides a filter event `Shopware_Controllers_Seo_filterCounts` to properly add our own counts. For this we need to use the name we used earlier for the progress bar. ``` @@ -377,7 +377,7 @@ While this already looks good, there's one more thing to do. Shopware needs to know our custom parameter "**wordId**" first. Otherwise our parameter would just get stripped and our SEO URL wouldn't work. -The possible cases for parameters are handled in the [RewriteGenerator](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Components/Routing/Generators/RewriteGenerator.php#L166). +The possible cases for parameters are handled in the [RewriteGenerator](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Components/Routing/Generators/RewriteGenerator.php#L166). It has a whole lot of cases, e.g. the parameter "**sArticle**" is only allowed when used with the **detail** controller. Thankfully, since Shopware 5.2, this method provides an event to add custom parameters. diff --git a/source/blog/_posts/2017-10-23-meetnext-recap.md b/source/blog/_posts/2017-10-23-meetnext-recap.md index af7302dcb8..28fd4114f8 100644 --- a/source/blog/_posts/2017-10-23-meetnext-recap.md +++ b/source/blog/_posts/2017-10-23-meetnext-recap.md @@ -42,7 +42,7 @@ So the main reason is: We want to continue to make Shopware better, faster, read All that said, we want to create a second version of Shopware which only carries the good part of our legacy. We don't want to do this in the dark, doing the jack-in-the-box at some time and presenting the new and shiny brother of Shopware 5. We want to have you aboard as soon as possible. We want to hear from you if the things we are planning and implementing are what you need in the end. We want to hear what you think is a mistake, what we forgot and what is even more awesome than before. -The #MeetNext was the first feedback event and it was, marketing speak aside, a huge success. Before we dive in, always remember you can see for yourself what is happening, either on [github](https://github.com/shopware/shopware/tree/labs) or in the [documentation](https://developers.shopware.com/labs/). +The #MeetNext was the first feedback event and it was, marketing speak aside, a huge success. Before we dive in, always remember you can see for yourself what is happening, either on [github](https://github.com/shopware5/shopware/tree/labs) or in the [documentation](https://developers.shopware.com/labs/). # A brief summary diff --git a/source/community/index.html b/source/community/index.html index be56ae39e5..1cfd499214 100644 --- a/source/community/index.html +++ b/source/community/index.html @@ -43,7 +43,7 @@

Contributing

Sources

    -
  • Shopware
    • +
  • Shopware
  • Developers Documentation
  • Shopware 5 organisation (miscellaneous open source projects, related to Shopware 5)
  • Crowdin (localization and translation platform)
    • diff --git a/source/designers-guide/datepicker/index.md b/source/designers-guide/datepicker/index.md index 07828174bc..374ea4b474 100644 --- a/source/designers-guide/datepicker/index.md +++ b/source/designers-guide/datepicker/index.md @@ -49,7 +49,7 @@ Like most of our jQuery plugins, the datepicker may be configured through data a data-enabledDates="2017-05-01, 2017-04-24, 2017-06-15" /> ``` -Every data attribute overwrites one of the default values in [`themes/Frontend/Responsive/frontend/_public/src/js/jQuery.datepicker.js`](https://github.com/shopware/shopware/blob/5.3/themes/Frontend/Responsive/frontend/_public/src/js/jquery.datepicker.js), which alter the behaviour of the datepicker plugin. +Every data attribute overwrites one of the default values in [`themes/Frontend/Responsive/frontend/_public/src/js/jQuery.datepicker.js`](https://github.com/shopware5/shopware/blob/5.3/themes/Frontend/Responsive/frontend/_public/src/js/jquery.datepicker.js), which alter the behaviour of the datepicker plugin. Option | Default value | Possible values | Explanation --- | --- | --- | --- @@ -81,7 +81,7 @@ Option | Default value | Possible values | Explanation ### Global -Apart from the element-specific configuration, theres also a global configuration file: [`themes/Frontend/Bare/frontend/index/datepicker-config.tpl`](https://github.com/shopware/shopware/blob/5.3/themes/Frontend/Bare/frontend/index/datepicker-config.tpl). The values in this file are set via Smarty snippets, so you may easily edit them in the Shopware Backend. +Apart from the element-specific configuration, theres also a global configuration file: [`themes/Frontend/Bare/frontend/index/datepicker-config.tpl`](https://github.com/shopware5/shopware/blob/5.3/themes/Frontend/Bare/frontend/index/datepicker-config.tpl). The values in this file are set via Smarty snippets, so you may easily edit them in the Shopware Backend. ## Structure diff --git a/source/designers-guide/preparing-themes-for-the-community-store/index.md b/source/designers-guide/preparing-themes-for-the-community-store/index.md index fdbb3fbd1d..9852aea46f 100644 --- a/source/designers-guide/preparing-themes-for-the-community-store/index.md +++ b/source/designers-guide/preparing-themes-for-the-community-store/index.md @@ -66,7 +66,7 @@ You need to create a `plugin.xml` file in the same directory, which defines the ##### plugin.xml ```xml - + 1.0.0 diff --git a/source/developers-guide/backend-components/basics/index.md b/source/developers-guide/backend-components/basics/index.md index 6b9d8d4526..328f1e101d 100644 --- a/source/developers-guide/backend-components/basics/index.md +++ b/source/developers-guide/backend-components/basics/index.md @@ -109,7 +109,7 @@ Create a `/../SwagProductBasic/Resources/menu.xml` file. ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> diff --git a/source/developers-guide/implementing-your-own-captcha/index.md b/source/developers-guide/implementing-your-own-captcha/index.md index 389c93927f..2f8318505f 100644 --- a/source/developers-guide/implementing-your-own-captcha/index.md +++ b/source/developers-guide/implementing-your-own-captcha/index.md @@ -94,7 +94,7 @@ class SwagReCaptcha extends Plugin ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> @@ -229,7 +229,7 @@ With the new plugin system, creating a plugin configuration is fairly simple: In ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> sitekey diff --git a/source/developers-guide/lightweight-backend-modules/index.md b/source/developers-guide/lightweight-backend-modules/index.md index bfadc09790..857f1e2bb1 100644 --- a/source/developers-guide/lightweight-backend-modules/index.md +++ b/source/developers-guide/lightweight-backend-modules/index.md @@ -84,7 +84,7 @@ Basically you just have to create a new menu entry in the Shopware administratio ```xml diff --git a/source/developers-guide/phpstorm/index.md b/source/developers-guide/phpstorm/index.md index 78d5698bfb..38d3e776c2 100644 --- a/source/developers-guide/phpstorm/index.md +++ b/source/developers-guide/phpstorm/index.md @@ -21,7 +21,7 @@ You can find installation instructions on the official [PhpStorm Website](https: ### Requirements for developing -First of all you need a working Shopware installation. Just visit our [Github Repository](https://github.com/shopware/shopware) +First of all you need a working Shopware installation. Just visit our [Github Repository](https://github.com/shopware5/shopware) and follow the `README.md` installation instructions. You do not want to worry about a local webserver or database server? Then take a look at our [Vagrant and PHPStorm](/developers-guide/vagrant-phpstorm/) guide to set up a virtual machine, ready to develop with Shopware. If you want to contribute to the Shopware repository also check out our @@ -96,4 +96,3 @@ From the context menu `Mark directory as` -> `Excluded` - `tests/Unit/` - `tests/Functional/` - diff --git a/source/developers-guide/plugin-configuration/index.md b/source/developers-guide/plugin-configuration/index.md index d0a94c053b..2f41a8ee6f 100644 --- a/source/developers-guide/plugin-configuration/index.md +++ b/source/developers-guide/plugin-configuration/index.md @@ -30,7 +30,7 @@ A plugin configuration can be created with a Resources/config.xml file. ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> @@ -44,7 +44,7 @@ A textfield would be defined as followed: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> simpleTextField @@ -341,7 +341,7 @@ reachable via the basic settings under the "Additional settings" entry: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> simpleTextField @@ -364,7 +364,7 @@ we write a little plugin which replaces the Shopware logo with random text. ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> show diff --git a/source/developers-guide/plugin-extension-by-plugin/index.md b/source/developers-guide/plugin-extension-by-plugin/index.md index a2407e34ab..115e44f0d6 100644 --- a/source/developers-guide/plugin-extension-by-plugin/index.md +++ b/source/developers-guide/plugin-extension-by-plugin/index.md @@ -43,7 +43,7 @@ contains the base information about the plugin, the label in English and German, ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> diff --git a/source/developers-guide/plugin-guidelines/index.md b/source/developers-guide/plugin-guidelines/index.md index 46285eec1b..182a6c214c 100644 --- a/source/developers-guide/plugin-guidelines/index.md +++ b/source/developers-guide/plugin-guidelines/index.md @@ -137,7 +137,7 @@ this is the plugin's name in `snake_case`) and `.logger`. So for a plugin called `SwagExample`, the service-ID of the plugin-specific logger would be `swag_example.logger`. You can read more about the plugin-specific logger in the corresponding -[upgrade document](https://github.com/shopware/shopware/blob/5.6/UPGRADE-5.6.md#plugin-specific-logger). +[upgrade document](https://github.com/shopware5/shopware/blob/5.6/UPGRADE-5.6.md#plugin-specific-logger). ## Plugin installation routine diff --git a/source/developers-guide/plugin-lastregistrations-widget/index.md b/source/developers-guide/plugin-lastregistrations-widget/index.md index 1422a96ca0..95803cdea1 100644 --- a/source/developers-guide/plugin-lastregistrations-widget/index.md +++ b/source/developers-guide/plugin-lastregistrations-widget/index.md @@ -27,7 +27,7 @@ As always in the new plugin system we set our metadata in the `plugin.xml` ``` + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> @@ -350,4 +350,3 @@ Ext.define('Shopware.apps.Index.swagLastRegistrationsWidget.model.Account', { ## Download plugin ## The whole plugin can be downloaded here. - diff --git a/source/developers-guide/plugin-quick-start/index.md b/source/developers-guide/plugin-quick-start/index.md index 5045e730ad..111dfd5b9f 100644 --- a/source/developers-guide/plugin-quick-start/index.md +++ b/source/developers-guide/plugin-quick-start/index.md @@ -366,7 +366,7 @@ In order to create the plugin configuration, we will need to implement the `Reso ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> swagSloganContent @@ -948,7 +948,7 @@ Example `plugin.xml`: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> @@ -1032,7 +1032,7 @@ If you need other plugins to be installed, then you are able to define them in y ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/plugin.xsd"> ... ... @@ -1050,7 +1050,7 @@ Backend plugin configuration can be extended by `Resources/config.xml` file. ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> slogan @@ -1086,7 +1086,7 @@ A custom config store is defined like this: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> selectArray @@ -1137,7 +1137,7 @@ Example: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> readOnlyText @@ -1159,7 +1159,7 @@ Example: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> buttonTest @@ -1191,7 +1191,7 @@ Example `Resources/menu.xml`: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/menu.xsd"> SloganOfTheDay @@ -1238,7 +1238,7 @@ Example `Resources/cronjob.xml`: ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/cronjob.xsd"> Send birthday email diff --git a/source/developers-guide/shopware-5-plugin-update-guide/index.md b/source/developers-guide/shopware-5-plugin-update-guide/index.md index 52c63c5a35..517dcec49b 100644 --- a/source/developers-guide/shopware-5-plugin-update-guide/index.md +++ b/source/developers-guide/shopware-5-plugin-update-guide/index.md @@ -171,7 +171,7 @@ For adding plugin configuration you add a new xml file to the Resources director ```xml + xsi:noNamespaceSchemaLocation="https://raw.githubusercontent.com/shopware5/shopware/5.3/engine/Shopware/Components/Plugin/schema/config.xsd"> diff --git a/source/developers-guide/shopware-5-upgrade-guide-for-developers/index.md b/source/developers-guide/shopware-5-upgrade-guide-for-developers/index.md index e5749be37b..8229671529 100644 --- a/source/developers-guide/shopware-5-upgrade-guide-for-developers/index.md +++ b/source/developers-guide/shopware-5-upgrade-guide-for-developers/index.md @@ -37,14 +37,14 @@ plugins do not rely on this behaviour. #### Deprecations -We've [removed](https://github.com/shopware/shopware/commit/b2709e5fd57432e92f6921dddddb76a2f7f5d0b2) all deprecations +We've [removed](https://github.com/shopware5/shopware/commit/b2709e5fd57432e92f6921dddddb76a2f7f5d0b2) all deprecations marked for removal with v5.7.0. #### Development tools You may use composer v2 now, support has been added with this version. Furthermore we've removed the `psh.phar` tool for Shopware development, it has been replaced by a -[Makefile](https://github.com/shopware/shopware/blob/5.7/Makefile) which may now be used for development tasks like +[Makefile](https://github.com/shopware5/shopware/blob/5.7/Makefile) which may now be used for development tasks like starting the testsuite. #### Snippets @@ -348,8 +348,8 @@ You can see the autocompletion in action in the mail templates of Shopware 5.6: variables and tags like `if` or `foreach`. This might be extended to other areas as well in future releases. If you are interested in implementing this functionality in your own plugin, you'll first have to -[register a `completer`-callback](https://github.com/shopware/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L107) function. -This [`callback`](https://github.com/shopware/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L193) determines if an autocompletion could be possible (by performing some [sanity checks](https://github.com/shopware/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L197)) and doing an AJAX-request containing the relevant text portion of the editor. +[register a `completer`-callback](https://github.com/shopware5/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L107) function. +This [`callback`](https://github.com/shopware5/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L193) determines if an autocompletion could be possible (by performing some [sanity checks](https://github.com/shopware5/shopware/blob/83b7f50837b134050a8d882cde1dbb3e66c61df9/themes/Backend/ExtJs/backend/mail/view/main/content_editor.js#L197)) and doing an AJAX-request containing the relevant text portion of the editor. The backend now can respond with a data structure containing the relevant autocompletion suggestions. How these are to be determined depends on your use case and underlying data structures. The `MailBundle` uses an @@ -503,7 +503,7 @@ on upgrade until Shopware 5.6, but they won't be kept in sync anymore. - Old conversion classes got removed: `Shopware_Components_Convert_Csv`, `Shopware_Components_Convert_Excel` and `Shopware_Components_Convert_Xml` - The action `\Shopware_Controllers_Widgets_Listing::ajaxListingAction` was removed. Use `Shopware_Controllers_Widgets_Listing::listingCountAction` instead. -For a complete overview check the **Removals** part of the Upgrade.md. +For a complete overview check the **Removals** part of the Upgrade.md. ### MySQL 8 workaround @@ -983,10 +983,10 @@ Version 5.3 does not support IE10 anymore. #### Security mode We have activated the Smarty security mode globally with 5.3: -[https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Components/DependencyInjection/Bridge/Template.php#L57](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Components/DependencyInjection/Bridge/Template.php#L57) +[https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Components/DependencyInjection/Bridge/Template.php#L57](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Components/DependencyInjection/Bridge/Template.php#L57) This means that certain PHP functions can no longer be used in Smarty. The available Smarty functions are stored in the following configuration file: -[https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Configs/smarty_functions.php](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Configs/smarty_functions.php) +[https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Configs/smarty_functions.php](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Configs/smarty_functions.php) This can be extended via the config.php as follows: @@ -1895,7 +1895,7 @@ The account section and registration have been refactored to continue the refact * Uses the new service `shopware_account.register_service` * Methods of core class `\sAdmin` regarding the registration have been removed without substitution. * Templates may have been rewritten - * For a complete list of template and event changes, refer to the [UPGRADE.md](https://github.com/shopware/shopware/blob/5.3/UPGRADE-5.2.md). + * For a complete list of template and event changes, refer to the [UPGRADE.md](https://github.com/shopware5/shopware/blob/5.3/UPGRADE-5.2.md). ### Address management @@ -1913,7 +1913,7 @@ The address management allows a customer to manage more than only one address wh * Selecting another address in the checkout results in a change of the session key `checkoutBillingAddressId` or `checkoutShippingAddressId` with the corresponding address id. After the order has been saved, the session keys will be reset. * The customer api endpoint now uses the structure of the address model, instead of the billing or shipping model * The checkout templates have been rewritten which results in changed and removed blocks. - * For a complete list of template changes, refer to the [UPGRADE.md](https://github.com/shopware/shopware/blob/5.3/UPGRADE-5.2.md). + * For a complete list of template changes, refer to the [UPGRADE.md](https://github.com/shopware5/shopware/blob/5.3/UPGRADE-5.2.md). To learn more about the new address service, refer to the [Address Management Guide](/developers-guide/address-management-guide). @@ -2030,7 +2030,7 @@ attributeForm.saveAttribute(record.get('id'), function (successful) { This call will send a new request which saves all attributes for this item. -To learn more about the new attribute management, refer to the [README.md](https://github.com/shopware/shopware/blob/5.3/engine/Shopware/Bundle/AttributeBundle/README.md) file in the source code. +To learn more about the new attribute management, refer to the [README.md](https://github.com/shopware5/shopware/blob/5.3/engine/Shopware/Bundle/AttributeBundle/README.md) file in the source code. ### Library updates diff --git a/source/developers-guide/vagrant-phpstorm/index.md b/source/developers-guide/vagrant-phpstorm/index.md index 38118ce370..951640255d 100644 --- a/source/developers-guide/vagrant-phpstorm/index.md +++ b/source/developers-guide/vagrant-phpstorm/index.md @@ -111,14 +111,14 @@ These directories will be marked red in your project and might not be visible an ### Coding Style -As mentioned in our [CONTRIBUTING.md](https://github.com/shopware/shopware/blob/5.3/CONTRIBUTING.md), you should follow the [PSR-1](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) and [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) coding standards. PhpStorm provides you with predefined settings in `Editor` -> `PHP` -> `CodeStyling`. +As mentioned in our [CONTRIBUTING.md](https://github.com/shopware5/shopware/blob/5.3/CONTRIBUTING.md), you should follow the [PSR-1](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md) and [PSR-2](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) coding standards. PhpStorm provides you with predefined settings in `Editor` -> `PHP` -> `CodeStyling`. ### Deploy with PhpStorm -To deploy a locally installed project to the Vagrant server, you need to configure auto deployment in PhpStorm. Make sure you are using the developer version of Shopware which can be downloaded from [GitHub](https://github.com/shopware/shopware). +To deploy a locally installed project to the Vagrant server, you need to configure auto deployment in PhpStorm. Make sure you are using the developer version of Shopware which can be downloaded from [GitHub](https://github.com/shopware5/shopware). -`git clone https://github.com/shopware/shopware.git` +`git clone git@github.com:shopware5/shopware.git` #### Step 1 Open your Shopware project in PhpStorm. diff --git a/source/sysadmins-guide/installation-guide/index.md b/source/sysadmins-guide/installation-guide/index.md index 28a3af4a14..6754edaa8e 100644 --- a/source/sysadmins-guide/installation-guide/index.md +++ b/source/sysadmins-guide/installation-guide/index.md @@ -14,7 +14,7 @@ Welcome to the Shopware developer community! Follow these steps for a successful Before you start, you should check if your environment meets the requirements. ### Installation -Simply follow the instructions on our README.md file for installing the Shopware developer version. +Simply follow the instructions on our README.md file for installing the Shopware developer version. If you want to install the latest stable release of Shopware, download it here and follow these instructions. diff --git a/source/sysadmins-guide/system-requirements/index.md b/source/sysadmins-guide/system-requirements/index.md index 8b3e25fe21..4f3a088aa3 100644 --- a/source/sysadmins-guide/system-requirements/index.md +++ b/source/sysadmins-guide/system-requirements/index.md @@ -50,7 +50,7 @@ It's strongly recommended that you verify the documentation - and the Shopware [Composer project](https://github.com/shopware/composer-project). + and the Shopware [Composer project](https://github.com/shopware5/composer-project). #### Shopware Version @@ -927,7 +927,7 @@ To be compatible with most versions of Shopware, please use the `config` service Several paths have been added to the DIC: - `shopware.plugin_directories.projectplugins` - Path to project specific plugins, see [Composer project](https://github.com/shopware/composer-project) + Path to project specific plugins, see [Composer project](https://github.com/shopware5/composer-project) - `shopware.template.templatedir` Path to the themes folder - `shopware.app.rootdir` diff --git a/source/developers-guide/shopware-composer/index.md b/source/developers-guide/shopware-composer/index.md index 3b0311da3f..4dad8694fd 100644 --- a/source/developers-guide/shopware-composer/index.md +++ b/source/developers-guide/shopware-composer/index.md @@ -13,7 +13,7 @@ menu_order: 32 ## Introduction -Starting with v5.4 Shopware supports installing a shop as a [Composer dependency](https://github.com/shopware/composer-project) +Starting with v5.4 Shopware supports installing a shop as a [Composer dependency](https://github.com/shopware5/composer-project) out of the box. This helps you to professionalize development and deployments of Shopware shops by providing a reliable versioning of Shopware itself and all the plugins required by your project. diff --git a/source/sysadmins-guide/professional-deployments/index.md b/source/sysadmins-guide/professional-deployments/index.md index e56646b02d..cd970c79c0 100644 --- a/source/sysadmins-guide/professional-deployments/index.md +++ b/source/sysadmins-guide/professional-deployments/index.md @@ -21,7 +21,7 @@ You should be using a version control system (VCS), preferably [git](https://git on local machines while integrating these parts in a central point. See the developers guide. If you find yourself reusing plugins, themes or configuration, think about using [Composer](https://getcomposer.org/) and -the [Shopware Composer Project](https://github.com/shopware/composer-project) for your new projects. It will help you +the [Shopware Composer Project](https://github.com/shopware5/composer-project) for your new projects. It will help you to require plugins or libraries you repeatedly use. ### Development, staging and production systems @@ -67,7 +67,7 @@ applied in a v5.7 and so on. ### Best practices Try to not store credentials on disk to minimize the information an attacker might gain in case of file system access. -Rather use environment variable set e.g. in the webserver. The [Shopware Composer Project](https://github.com/shopware/composer-project) +Rather use environment variable set e.g. in the webserver. The [Shopware Composer Project](https://github.com/shopware5/composer-project) supports environment variable for the setup of e.g. the database out of the box. You could start your automated deployments with some simple shell scripts to e.g. checkout a specific tag on the From 3c4211d6d819907c417494ec69b944fa9a52c9ac Mon Sep 17 00:00:00 2001 From: Michael Telgmann Date: Fri, 25 Aug 2023 09:33:26 +0200 Subject: [PATCH 3/4] fix: Adjust link of PayPal plus repository, so it is directing to the new organisation --- source/blog/_posts/2015-11-11-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/blog/_posts/2015-11-11-best-practices.md b/source/blog/_posts/2015-11-11-best-practices.md index 29af395bf9..4607224e2d 100644 --- a/source/blog/_posts/2015-11-11-best-practices.md +++ b/source/blog/_posts/2015-11-11-best-practices.md @@ -427,7 +427,7 @@ This is not only good for testability - but also for the code quality. ## plugin.json Some time ago, we started to move all the meta data from the plugin's `Boostrap.php` to a file called `plugin.json`. -An example can be found in the [Paypal plugin on github](https://github.com/shopwareLabs/SwagPaymentPaypalPlus/blob/master/plugin.json). +An example can be found in the [Paypal plugin on github](https://github.com/shopware5/SwagPaymentPaypalPlus/blob/master/plugin.json). I find it very convenient to use this file - it will give you a good overview regarding Shopware version compatibility, change logs and other relevant information. If we release our Shopware account API at some point in the future, the From 4ba5811064d838f6f25343fcbd5f57d283b3024c Mon Sep 17 00:00:00 2001 From: Michael Telgmann Date: Fri, 25 Aug 2023 09:43:13 +0200 Subject: [PATCH 4/4] fix: Adjust link of cart POC repository, so it is directing to the new organisation --- .../blog/_posts/2016-12-09-new-cart-bundle.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/source/blog/_posts/2016-12-09-new-cart-bundle.md b/source/blog/_posts/2016-12-09-new-cart-bundle.md index 80237ec6b4..1bdc5333d4 100644 --- a/source/blog/_posts/2016-12-09-new-cart-bundle.md +++ b/source/blog/_posts/2016-12-09-new-cart-bundle.md @@ -16,16 +16,27 @@ Since the last Community Day, we've received several questions about Shopware's - *How far are you with the development* - *Which new features come with the new shopping cart?* -At the Community Day, we also announced that we are striving for open development in the refactoring process in order to get as much feedback as possible and to be able to work more closely with other developers and partners. We want to realize this now by sharing the first concept of the new shopping cart. You can see the development process on Github, where we created a new repository which allows the Community to create pull requests and issues. The new repository contains a new bundle in `/engine/Shopware/Bundle/CartBundle`, which contains a first proof of concept for a new cart process. This first concept can change steadily due to growing requirements and that refactoring will be an ongoing process. The first features we implemented are the following: +At the Community Day, we also announced that we are striving for open development in the refactoring process in order to get as much feedback as possible and to be able to work more closely with other developers and partners. +We want to realize this now by sharing the first concept of the new shopping cart. +You can see the development process on Github, +where we created a new repository which allows the Community to create pull requests and issues. +The new repository contains a new bundle in `/engine/Shopware/Bundle/CartBundle`, which contains a first proof of concept for a new cart process. +This first concept can change steadily due to growing requirements and that refactoring will be an ongoing process. +The first features we implemented are the following: - Add, delete and change quantity of product line items - Add and delete percentage-based vouchers - First concept for partial delivery -There's currently no storefront integration. A view layer will follow after all calculation processes are tested. For that reason, the classes are only used inside unit tests. From a technical perspective, the cart already contains the following concepts/features: +There's currently no storefront integration. A view layer will follow after all calculation processes are tested. +For that reason, the classes are only used inside unit tests. +From a technical perspective, the cart already contains the following concepts/features: - Percentage price calculation - Gross and net price calculation - Proportional tax calculation - Exchangeable gateway for product prices and delivery information - First proof of concept for a partial delivery to different addresses and delivery dates -If you want to get more information about the technical concept and current implementation, take a look at our new developers guide article. This article is created to document the current state of the implementation and will contain more content regarding progressive refactoring. Due to the complexity and importance of the shopping cart inside Shopware, this will be a long-term project. Short-term integration into the core product is therefore not to be expected. +If you want to get more information about the technical concept and current implementation, take a look at our new developers guide article. +This article is created to document the current state of the implementation and will contain more content regarding progressive refactoring. +Due to the complexity and importance of the shopping cart inside Shopware, this will be a long-term project. +Short-term integration into the core product is therefore not to be expected.