But sometimes you can / should use a different event instead of moving the existing one.
If you move an event to an unsuitable place, it may cause html errors (in source code). Html errors can also occur if you take a wrong / to the Ext. unsuitable event. Happens to me when placing the stylechanger of Kirk in the breadcrumbs. There are two events for placing in breadcrumbs and I had chosen the wrong one first. Which then resulted in a </x> (p or b forgotten) too much.
If an extension should only be displayed in a certain style at another event, the empty folder with the standard event name must be inserted in this style folder in the ext. Otherwise the extension will be displayed twice (unless you change it for prosilver). Then you have 3 instead of only 2 folders ( ext - extxy - styles - yourstyle - template - event)
renamed overall_header_navigation_append folder. Respective with exactly the same content.
(Now the stylechanger is displayed in prosilver in the navbar, but in my style in the breadcrumbs.)
If you want to replace the event in prosilver only, or for all your styles, the
folder has to be renamed into
in the above example (It then remains with the 2 folders).
(Now the stylechanger in all styles is displayed in the breadcrumbs instead of in the navbar as before.)
After moving (in html) or changing (in ext) an event the source code must be checked!