-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: #670, Fix:typos, Fix: reST #789
Conversation
@@ -80,6 +80,6 @@ All in all, this allows sophisticated setups, where some content items just foll | |||
|
|||
**Defining your own workflows** | |||
|
|||
It is no problem to define your own workflows. By default, however, that involves a trip to the :doc:`ZMI Management Interface <management-interface>` which is not incredibly userfriendly, and defining new workflows is a task best left for your Site Administrator or other specialist. | |||
It is no problem to define your own workflows. By default, however, that involves a trip to the :doc:`Management Interface <management-interface>` which is not incredibly userfriendly, and defining new workflows is a task best left for your Site Administrator or other specialist. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"user friendly" should be two words
.. note:: ZMI > portal_view_customizations is an handy way to find the template path. | ||
.. note:: | ||
|
||
Management Interface > portal_view_customizations is an handy way to find the template path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
..."is a handy way"
appendices/glossary.rst
Outdated
as appending ``/manage`` to your URL, for example: | ||
The *Management Interface*. | ||
A Management Interface that is accessible through the web. | ||
Accessing is as simple as appending ``/manage`` to your URL, for example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Accessing it is as simple" (missing "it")
@@ -29,7 +29,7 @@ GenericSetup XML files are usually in a ``profiles/default`` folder inside the a | |||
All run-time through-the-web (:term:`TTW`) configurable items, like viewlets order through ``/@@manage-viewlets`` page, are made repeatable using GenericSetup profile files. | |||
|
|||
You do not need to hand-edit GenericSetup profile files. | |||
You can always change the configuration options through Plone or using the Zope Management Interface, and then you export the resulting profile as an XML file, using the *Export* tab in the ``portal_setup`` ZMI tool. | |||
You can always change the configuration options through Plone or using the Management Interface, and then you export the resulting profile as an XML file, using the *Export* tab in the ``portal_setup`` Management Interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"in portal_setup
, accessible from the Management Interface"
@@ -837,7 +837,7 @@ Note that you are always allowed to use the ``plone`` domain, but if the xml fil | |||
... | |||
</object> | |||
|
|||
Note that when you go to the portal_actions tools in the ZMI, you will see an i18n domain specified for each action. | |||
Note that when you go to the portal_actions tools in the Management Interface, you will see an i18n domain specified for each action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"tool" should be singular
different subsystems. They provide a more consistent and declarative | ||
way to define bridges between two different things, when duck-typing | ||
Plone extensively uses interfaces to define APIs between different subsystems. | ||
They provide a more consistent and declarative way to define bridges between two different things, when duck-typing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is duck-typing?
@@ -512,20 +512,17 @@ Example (mfabrik/rstpage/archetypes/fields.py):: | |||
Automatically generating description based on body text | |||
-------------------------------------------------------- | |||
|
|||
Below is a sample through-the-web Python Script which | |||
you can drop to any Plone through Zope Management Interface. | |||
Below is a through-the-web (ttw) Python Script which you can drop to any Plone through the Management Interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"TTW" (should be capitalized)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"you can drop into"
by taking the first three sentences. | ||
|
||
The script will provide logging output to standard Plone log | ||
(var/log and stdout if Plone is run in the debug mode). | ||
The script will provide logging output to standard Plone log (var/log and stdout if Plone is run in the debug mode). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"in debug mode"
@@ -309,10 +309,9 @@ Register the view against a marker interface: | |||
template="view.pt" | |||
/> | |||
|
|||
* Assign this marker interface to a content item using the Zope Management Interface | |||
(:term:`ZMI`, via the Interfaces tab) | |||
* Assign this marker interface to a content item using the Management Interface, via the Interfaces tab |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Python" should be capitalized
for all folders to another type. You can execute the script through | ||
the :term:`ZMI` as a Python Script. | ||
for all folders to another type. | ||
You can execute the script through the Management Interface as a Python Script. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Script" should not be capitalized (unless you're referring to a "Script (Python)")
@@ -37,7 +37,7 @@ To export objects from a site to another, do the following: | |||
|
|||
* Zope .zexp to *youranothersite*/var/instance/import folder | |||
|
|||
* Go to ZMI root of your another site | |||
* Go to the Management Interface root of your another site |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"your another" should either be "your other" or just "another" (not sure of the context)
Welcome in the world of 'old documentation' ! |
@@ -23,7 +23,7 @@ For more information, see | |||
Creating workflows | |||
------------------ | |||
|
|||
The recommended method is to use the portal_workflow user interface in the Zope Management Interface | |||
The recommended method is to use the portal_workflow user interface in the Management Interface |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"use portal_workflow in the Management Interface"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for replacing "ZMI"! I found some minor tweaks to make.
@@ -102,7 +102,7 @@ Disabling workflow for a content type | |||
If a content type doesn't have a workflow it uses its parent container security settings. | |||
By default, content types Image and File have no workflow. | |||
|
|||
Workflows can be disabled by setting the workflow setting empty in portal_workflow in ZMI. | |||
Workflows can be disabled by setting the workflow setting empty in portal_workflow in the Management Interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"by leaving the workflow setting empty"
@@ -9,11 +9,15 @@ PloneFormGen | |||
Introduction | |||
------------ | |||
|
|||
*PloneFormGen* is a Plone add-on Product that provides a generic Plone form generator using fields, widgets and validators from Archetypes. Use it to build simple, one-of-a-kind, web forms that save or mail form input. | |||
*PloneFormGen* is a Plone add-on Product that provides a generic Plone form generator using fields, widgets and validators from Archetypes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"is a Plone add-on that"
|
||
|
||
Introduction | ||
------------ | ||
|
||
Plone has concept of actions which refer the end user functionality associated with site | ||
or content objects: | ||
Plone has concept of actions which refer the end user functionality associated with site or content objects: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of "refer", maybe "connect"?
@@ -62,7 +62,7 @@ features like localization and user-friendly titles. | |||
|
|||
New criteria can be created through-the-web in Site setup -> Collection section. Click "All fields" to see unenabled portal_catalog criteria. Later the edited settings can be exported to GenericSetup XML profile using portal_setup tool (no need to create profile XMl files by hand). | |||
|
|||
portal_catalog indices can be added through-the-web on ZMI portal_catalog tool tabs. | |||
portal_catalog indices can be added through-the-web on (ttw) through the Management Interface portal_catalog tool tabs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove "on" and capitalize "TTW"
|
||
Goto your site's portal_setup in ZMI, select your registered profile and import | ||
Goto your site's portal_setup in Management Interface, select your registered profile and import |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Go to"
|
||
|
||
Accesing the ``portal_catalog`` tool | ||
==================================== | ||
|
||
Plone queries are performed using ``portal_catalog`` persistent tool which | ||
is available as an persistent object at the site root. | ||
Plone queries are performed using ``portal_catalog`` persistent tool which is available as an persistent object at the site root. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
curious why we have to say it's persistent, and I think generally appending "tool" to portal_* is unnecessary
@@ -650,7 +651,7 @@ To get all catalog brains of certain content type on the whole site:: | |||
|
|||
campaign_brains = self.context.portal_catalog(portal_type="News Item") | |||
|
|||
To see available type names, visit in portal_types tool in ZMI. | |||
To see available type names, visit in portal_types tool in Management Interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"in the Management Interface"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the first "in" and "tool", so "visit portal_types in the Management Interface"
@@ -1064,7 +1065,7 @@ site objects. | |||
Here is an example how to crawl through Plone content to search HTML | |||
snippets. This can be done by rendering every content object and check | |||
whether certain substrings exists the output HTML This snippet can be | |||
executed through-the-web in Zope Management Interface. | |||
executed through-the-web in Management Interface. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"the Management Interface"
@@ -15,7 +15,7 @@ for a folder and its children. | |||
|
|||
By default Plone has roles like ``Contributor``, ``Reader``, ``Editor``, etc. | |||
and you can view these on the :guilabel:`Sharing` tab | |||
and in :term:`ZMI` :guilabel:`Security` tab. | |||
and in Management Interface :guilabel:`Security` tab. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"the Management Interface"
@@ -75,7 +83,9 @@ modules | |||
Using a Python script | |||
===================== | |||
|
|||
You'll be frustrated fast if you try to do anything smart in a single TALES expression. If you need to do something more complicated, add a Python Script to your form folder and call it via TALES. For example, if you added a script with the id includesSpam, you could call it with the expression:: | |||
You'll be frustrated fast if you try to do anything smart in a single TALES expression. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"frustrated fast" should be "quickly frustrated"
Fixes: #670
Improves: reST
Changes proposed in this pull request:
Change
ZMI
toManagement Interface
Change
Zope Management Interface
toManagement Interface
Fix various reST syntax errors
Fix typo
This is for 5.1 only, please do not cherry-pick into 4.x !
This is supposed to be released with 5.1, not before !
@tkimnguyen since you opened this issue, I added you as reviewer, thanks !