- The access key on your machine may be ‘alt’. On a Mac it’s ‘ctrl’.
- Hover over the link or button and a tooltip will popup with the access key.
- The most useful access keys are for screen navigation, see below.
Global keys that are always available
The following access keys are available in every Silva screen.
t Jump to top of page
b Jump to bottom of page
/ Jump to top of Silva (Silva icon)
? Access keys and shortcuts
The tabs have numbered access keys, starting from one going up to five. You can navigate horizontally accross an item’s screens by using alt-1, alt-2, and so forth.
Each tab has a toplink, the tall tree on the left side. It takes you to the top of the current publication, within the same tab, or ‘vein’. The access key is the shift character of the corresponding number (on the English keyboard, sorry if you have an international one). Thus alt-!, alt-@, alt-#, alt-$, and alt-% (note that the characters resemble the number).
On the right of each tab is an uplink, a small tree that takes you up one level in the same vein. The access keys for the uplinks are the remaining numbers (add five to the access key for the tab). If you are in a screen with five tabs, the uplinks are alt-6, alt-7, alt-8, alt-9, and alt-0. If there are less than five tabs, you still add five to get the uplink key.
Footer page info row
: See public page
Footer user row
~ user settings
, request access
Contents screen (folder)
s select list for a new object
o Select list for position number
a select all
g paste as ghost
p publish now
Publish screen (folder)
a select all
c close (public version)
n create new versions
j reject (request for approval)
v revoke (request for approval)
l approve for later
u update timing
p publish now
e add and edit/enter
( kupu editor
) forms editor
; public preview
p publish now
b bold (won’t work in FF3)
# numbered list
* bulleted list
= definition list
h html source
e save and exit
i save and insert
tab Use your tab key to edit without using the mouse. Shift-tab goes backwards.
The Properties, Access, and Publish screens as well as their subscreens (such as Lookup, Import, and Export) have access keys for most buttons. Usually the first letter of the button is the access key. You can always hover over the button to see the tooltip.
If there are two buttons with the same name, the access key for the second is usually the first letter of the second word (e.g. for “get image reference” and “get link reference”, the access keys are ‘g’ and ‘l’). Sometimes there are multiples of the same button, in which case only the first has an access key.
- Some access keys can conflict with browser menus. However the key works if the focus is in the page (a form element is active or just click in the page).
- Mozilla and Internet Explorer handle access keys for hyperlinks differently. Mozilla initiates the action (same as clicking the link), whereas Explorer just highlights the link, and then you have to hit return to activate it. Both browsers treat form buttons the same, initiating the action immediately.
- Don’t forget that most browsers use alt-left arrow to go back, and alt-right arrow to go forward. On the Mac, command-left arrow and command-right arrow do this.
Someday browsers will automatically underline the access key of a link or button. In the meantime, send a mail and complain.
If you wish to create additional docs, the hyperlink of the Silva help link can be changed by altering the the ‘help_url’ property in the Silva root. See the properties tab in the Zope Management Interface.
One click editing
Thanks to ETH Zürich for this trick.
Tip for Firefox/Mozilla/Netscape users
Using the “Find As You Type” feature will make keyboard navigation to hyperlinks – such as item names – remarkably easy. See:
Change Access Keys in Windows Firefox 2
To avoid access keys collision with the browser’s keyboard shortcuts, Firefox 2.0 added an additional modifier key: Alt+Shift
To revert to the old behavior as in Firefox 1.5.x proceed as following:
- Type ‘about:config’ in the address bar
- Type ‘ui’ in the filter bar
- Doubleclick on ui.key.contentAccess and change the value to 4 (default value is 5).
See a screenshot on Marc Petitmermet’s site (thanks for the tip).