Ön a következő verzió súgóját látja::
- 6.4
- 6.3
- 6.2
- Korábbi verziók
When editing pages in AEM, several modes are available, including Developer mode. This opens a side panel with several tabs that provide a developer with infomation about the current page. The three tabs are:
- Components for viewing sructure and performance information.
- Tests for running tests and analyzing the results.
- Errors to see any problems occuring.
These help a developer to:
- Discover: what pages are composed of.
- Debug: what is happening where and when, which in turn helps to resolve issues.
- Test: does the application behave as expected.
Figyelmeztetés:
Developer mode:
- Is only available in the touch-enabled UI (when editing pages).
- Is not available on mobile devices or small windows on desktop (due to space restrictions).
- This occurs when the width is less than 1024px.
- This occurs when the width is less than 1024px.
- Requires the appropriate permissions/privileges:
- Access to Developer Mode is given to users who have write access on /apps.
Figyelmeztetés:
Developer mode is only available on a standard author instance that is not using the nosamplecontent run-mode.
If required it can be configured for use:
- on an author instance using nosamplecontent run-mode
- a publish instance
It should be disabled again after use.
Megjegyzés:
See the:
- Knowledge Base article, Troubleshooting AEM TouchUI issues, for further tips and tools.
- AEM Gems session about AEM 6.0 Developer Mode.
Developer mode is implemented as a side panel to the page editor. To open the panel, select Developer from the mode selector in the toolbar of the page editor:
The panel is divided into two tabs:
- Components - This shows a component tree, similar to the content tree for authors
- Errors - When problems occur, details are shown for each component.
This shows a component tree that:
- Outlines the chain of components and templates rendered on the page (SLY, JSP, etc.). The tree can be expanded to show context within the hierarchy.
- Shows the server-side computational time needed to render the component.
- Allows you to expand the tree and select specific components within the tree. Selection provides access to component details; such as:
- Repository path
- Links to scripts (accessed in CRXDE Lite)
- Selected components (in the content flow, indicated by a blue border) will be highlighted in the content tree (and vice versa).
This can help to:
- Determine and compare the rendering time per component.
- See and understand the hierarchy.
- Understand, and then improve, the page loading time by finding slow components.
Figyelmeztetés:
Some links point to scripts under /libs. However, these are for reference only, you must not edit anything under /libs, as any changes you do make may be lost. This is due to the fact that this branch is liable to changes whenever you upgrade or apply a hotfix/feature pack. Any changes you require should be made under /apps, see Overlays and Overrides.
Hopefully the Errors tab will always be empty (as above), but when problems occur the following details are shown for each component:
- A warning if the component writes an entry to the error log, together with details of the error and direct links to the appropriate code within CRXDE Lite.
- A warning if the component opens an admin session.
For example, in a situation where a undefined method is called, the resulting error will be shown in the Errors tab:
The component entry in the tree of the Components tab will also be marked with an indicator when an error occurs.
Figyelmeztetés:
In AEM 6.2, the testing features of Developer mode was re-implemented as a standalone Tools application.
For full details see Testing Your UI.
A Twitter™ és Facebook közzétételeket a Creative Commons jogi feltételei nem szabályozzák.