You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-Site Request Forgery (CSRF or XSRF) is a type of web attack that allows an attacker to send malicious requests to a web application on behalf of a legitimate user.
14
+
Cross-site request forgery (CSRF or XSRF) is a type of web attack that allows an attacker to send malicious requests to a web application on behalf of a legitimate user.
15
15
The attack works by tricking the user's web browser into sending a request to the web application that the user did not intentionally make.
16
16
This can allow an attacker to perform actions on the web application without the user's knowledge or consent.
@@ -181,7 +181,7 @@ tag = scale_util.scale("image", width=600, height=200)
181
181
182
182
### Using `image_scale` in templates
183
183
184
-
You could use the URL-variant from above, but that would be an uncached version.
184
+
You could use the URL-variant from above, but that version would not be cached.
185
185
To create a cached scale in a page template you can do the following:
186
186
187
187
```xml
@@ -215,7 +215,7 @@ You can also provide the following keyword arguments to set `title`, `alt`, or `
215
215
216
216
### Get `image_scale` by cached {term}`UID` name
217
217
218
-
If you only have the cached image name from an URL and need to get the image scale, unfortunately you can't use `restrictedTraverse()`, as this will not be able to resolve the scale.
218
+
If you only have the cached image name from a URL and need to get the image scale, unfortunately you can't use `restrictedTraverse()`, as this will not be able to resolve the scale.
219
219
But you can use this workaround, by calling the `publishTraverse` method in `ImageScaling` directly:
Copy file name to clipboardExpand all lines: docs/classic-ui/viewlets.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ You can order, hide, and unhide or show viewlets.
98
98
The next sections describe how to do so.
99
99
100
100
101
-
### Ordering viewlets
101
+
### Order viewlets
102
102
103
103
To set the order of a viewlet inside its viewlet manager, use the following `GenericSetup` configuration.
104
104
@@ -116,9 +116,9 @@ See {ref}`classic-ui-viewlets-registering-viewlet-zcml-label`.
116
116
```
117
117
118
118
119
-
### Hiding viewlets
119
+
### Hide viewlets
120
120
121
-
Hiding a viewlet is also done from the {file}`viewlets.xml` with the `<hidden />` node, which is at same level as `<order />`, and is done per skin selection.
121
+
You can hide a viewlet from the {file}`viewlets.xml` with the `<hidden />` node, which is at same level as `<order />`, and is done per skin selection.
122
122
123
123
For instance, if you need to remove the global sections for your skin, you'd have to add some declaration, such as the following one in {file}`viewlets.xml`:
124
124
@@ -129,7 +129,7 @@ For instance, if you need to remove the global sections for your skin, you'd hav
129
129
```
130
130
131
131
132
-
### Unhiding viewlets
132
+
### Unhide viewlets
133
133
134
134
If, for any reason, you need to unhide one or more viewlets for a given viewlet manager, you can make use of the `purge` and `remove` node parameters in your `<hidden />` declaration in {file}`viewlets.xml`.
135
135
@@ -915,7 +915,7 @@ Next, re-register some stock viewlets against your new viewlet manager in {file}
915
915
916
916
Next, we need to render our viewlet manager somehow.
917
917
One place to do it is in a {file}`main_template.pt`, but because we need to add this HTML output to a header section which is produced by _another_ viewlet manager, we need to create a new viewlet just for rendering our viewlet manager.
918
-
Yo, dawg, we put viewlets in your viewlets so you can render viewlets!
918
+
We put viewlets in your viewlets so you can render viewlets!
Copy file name to clipboardExpand all lines: docs/classic-ui/views.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -585,7 +585,7 @@ If you need to override templates in core Plone or in an existing add-on, you ca
585
585
After the file is in place, changes to the file are instantly picked up.
586
586
The template code is re-read on every HTTP request.
587
587
588
-
If you want to override an already overridden template, read [How can I override an already overridden template by jbot?](https://stackoverflow.com/questions/16209392/how-can-i-override-an-already-overridden-template-by-jbot).
588
+
If you want to override an already overridden template, read [How can I override an already overridden template by `jbot`?](https://stackoverflow.com/questions/16209392/how-can-i-override-an-already-overridden-template-by-jbot).
589
589
590
590
591
591
(classic-ui-override-a-view-class-label)=
@@ -1009,7 +1009,7 @@ views = [ view.factory for view in views if IBlocksView.implementedBy(view.facto
1009
1009
1010
1010
### Default view of a content item
1011
1011
1012
-
Objects have views for`default`, `view`, `edit`, and so on.
1012
+
Objects have views for`default`, `view`, `edit`, and other views.
1013
1013
1014
1014
The distinction between the `default` and `view` views are that, for files, the default can be `download`.
0 commit comments