Switches between Frontend / Backend and work environments on your TYPO3 projects. Preserves page path and base url.
What does it do?
Simple yet advanced
This extension adds button to the Chrome's toolbar that opens a tab with TYPO3 Backend of current site (base href-based),
or a Frontend, if detects it is in Backend.
Second thing is you can quickly jump between project live/dev/staging instances (contexts) keeping current url path, also you can
add set of project's helper links like its task manager, wiki, etc. to quick navigate between all of them. Also jump
to install tool and a very handy menu with all projects with all contexts.
All of this within one right-click.
It displays info badge and favicon overlay of chosen color to visually distinguish between a number of open instances during
Project configurations may be exported (all or separately) to share with your team. Easy json importing.
(in current development is a project-repository functionality, to make the exchange much faster)
Note, that you may disable all environment-related functionality, to use only BE/FE switching and keep the ext more
lightweight. But why give up all these wonderful features?!
Switching to Frontend opens last selected page in backend page tree (works similar as View webpage button in backend,
but works even if currently some module without page tree /or such button/ is open).
(tested in versions 6.2, 7.6, 8.7, 9.5. any between should work as well)
(Also, I would like to make it expand the pagetree and select current page, best will be basing on url, when switching
to backend - but current TYPO3 architecture doesn't allow such trick. I hope to achieve this state one day. It would be
excellent productivity boost. Have to push some change requests to TYPO3 source...)
Some time ago there was an extension for switching to backend, but it was only opening current domain + /typo3/ segment - I've used it
for a long time though. Thanks to the author of original ext, Patrick Lischka, for inspirations to improve this idea.
- My ext goes further and it can open back the Frontend from Backend, also it can not only add a path to a domain, but
tries to extract the <base> tag from a page source, then uses it for a backend url (or just a domain, if not found).
So it works as expected when running TYPO3 project in subdirectory, ie. on your dev environment.
(For this, it needs that you set <base href="[url]"> in <head>)
Please write me any problems, suggestions or ideas.
wolo.pl '.' studio
TYPO3 and its logo are trademarks of the TYPO3 Association.
Icons based on: