Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
M2 content provisioning
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TechDivision Public
M2 content provisioning
Commits
34ab47fd
Commit
34ab47fd
authored
6 years ago
by
Vadim Justus
Browse files
Options
Downloads
Patches
Plain Diff
Update documentation
parent
53630a68
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!14
Introduce logic for handling with media files
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+7
-0
7 additions, 0 deletions
README.md
with
7 additions
and
0 deletions
README.md
+
7
−
0
View file @
34ab47fd
...
...
@@ -59,6 +59,7 @@ After installing this module you can create own `content_provisioning.xml` in ea
<page
key=
"your-module.page.an-identifier.german"
identifier=
"an-identifier"
maintained=
"true"
active=
"true"
>
<title>
Page Title
</title>
<content
heading=
"New Page Heading"
type=
"file"
>
Your_Module::path/to/content.html
</content>
<media_directory>
Your_Module::path/to/media
</media_directory>
<stores>
<store
code=
"germany_german"
/>
<store
code=
"swiss_german"
/>
...
...
@@ -103,6 +104,7 @@ After installing this module you can create own `content_provisioning.xml` in ea
<block
key=
"your-module.block.lorem-ipsum-2.german"
identifier=
"lorem-ipsum-2"
maintained=
"false"
active=
"true"
>
<title>
Test Block 2
</title>
<content
type=
"file"
>
Your_Module::path/to/content.html
</content>
<media_directory>
Your_Module::path/to/media
</media_directory>
<stores>
<store
code=
"germany_german"
/>
<store
code=
"swiss_german"
/>
...
...
@@ -136,6 +138,11 @@ This node is optional. If it is not defined, the block or page will be applied t
will also be applied to stores, which will be created in the future after re-running
`setup:upgrade`
command.
You can also use the 'wildcard'
`*`
in order to define that the content should be applied to all stores.
### `media_directory`-Node (since version 1.2.0)
Specifies the directory for media files. Each used media file in the content and present in media source directory
will be copied to Magento's
`pub/media`
directory. Sub-directory structure should be same like inspected it to be
in
`pub/media`
. Only existing and used media files will be copied.
## Executing integration tests on local environment
```
bash
# Create a new Magento instance
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment