Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 75405a6

Browse files
authored
Grammar and formatting
1 parent 1b494c4 commit 75405a6

File tree

1 file changed

+9
-12
lines changed

1 file changed

+9
-12
lines changed

src/guides/v2.3/extension-dev-guide/cache/page-caching/private-content.md

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -99,15 +99,18 @@ The following example adds comments to [app/code/Magento/Catalog/etc/frontend/se
9999
</action>
100100
</config>
101101
```
102-
{:.bs-callout-warning}
103-
Currently we have some place in sections that allows to declare 'action' node without specifying any sections, like -
102+
103+
There are sections that allow you to declare an 'action' node without specifying a sections, for instance, when logging out:
104+
104105
```xml
105-
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
106-
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Customer:etc/sections.xsd">
107-
<action name="customer/account/logout"/>
106+
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
107+
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Customer:etc/sections.xsd">
108+
<action name="customer/account/logout"/>
108109
</config>
109110
```
110-
It suppose to tell our JS to invalidate all sections, but if you have declared sections for this action in other xml file, that will override it and only newly added section will be invalidated, so if you need to reload all sections on some action you should either just use `*` as section name or use empty action and ensure that they will not be overriden by any other rules, e.g. -
111+
112+
This tells Magento to invalidate all sections. But if you have declared sections for this action in another .xml file, it will override the initial sections and only newly added sections will be invalidated. If you need to reload all sections on some action, use `*` as section name or use an empty action and ensure that they will not be overriden by any other rules:
113+
111114
```xml
112115
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
113116
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Customer:etc/sections.xsd">
@@ -116,12 +119,6 @@ It suppose to tell our JS to invalidate all sections, but if you have declared s
116119
</action>
117120
</config>
118121
```
119-
Note: In future release action nodes without section name specification will be deprecated. and in case our SectionConfigConverter will recieve
120-
```xml
121-
<section name="*"/>
122-
```
123-
It will disregard any other rules
124-
125122
126123
{:.bs-callout-warning}
127124
Use only HTTP POST or PUT methods to change state (e.g., adding to a shopping cart, adding to a wishlist, etc.) and do not expect to see caching on these methods. Using GET or HEAD methods might trigger caching and prevent updates to private content. For more information about caching, see [RFC-2616 section 13](https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html){:target="_blank"}.

0 commit comments

Comments
 (0)