[TYPO3-dev] Better working fronend editing for TemplaVoila - done for 1.0
Tapio Markula
tapio.markula at dnainternet.net
Fri Apr 7 14:20:29 CEST 2006
Hi
I tested the newest version of TemplaVoila (1.0)
and made some changes to tm_contentaccess to work with that versions.
Even if some of the worst bugs has been fixed, TemplaVoila 1.0 doesn't
have very good frontend editing without tm_contentaccess or hacking
source code and making the same changes.
1) the wizard has path problem (wizard in admin panel or in EDITPANEL
objects, if allow = toolbar,... has been set). Path is incorrect if
Typo3 has been installed into subfolder. Made a hack to use
'typo3conf/ext/templavoila/mod1/' is TemplaVoila is installed and enabled.
2) Using the content element wizard
(typo3conf/ext/templavoila/mod1/db_new_content_el.php) works bad because
you set the content into the *same* content area. The order *must* be
the BE view (typo3conf/ext/templavoila/mod1/index.php) and then
selecting new content using
typo3conf/ext/templavoila/mod1/db_new_content_el.php,
because in the 'toolbar' typo can't know where the user wants to put the
new content element. It is extremely annoying immediately move the
content to another place. In order to avoid annoying situations
typo3conf/ext/templavoila/mod1/index.php is the only reasonable place to
start creating new content element using the wizard in frontend. The
entire BE view is quite big as wizard - but
TemplaVoila just doesnt' have a compact content area wizard like the
standard page module - compact wizard would be the best in FE but the
using index.php file is quite ok.
Requirements to work:
1) frontend editing has been enabled so that admin panels are available
and frontend editing works in pop-up-windows
2) TS template has place for object 'editPanel', which has been
predefined or admin panel enabled
3) TemplaVoila has been installed and enabled using enable options
I admit that tm_contentaccess has just some hacks to fix serious bugs
but it is better than nothing. There is really much work to make that
better.
More information about the TYPO3-dev
mailing list