You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is not possible to add an accordion to the content navigation.
The reason is that "Wrapper start" / "Single element" has no headline. There is only a field Section headline. In general, it would definitely be very easy to use this field.
BUT: it is only a textfield. There is no possibility to define the headline level. That will result in different problems (start/stop level could not be recognized, where to add the entry in the netsted list of the output).
My current workaround is, to replace the Section headline for accordion "Wrapper start" / "Single element" with the headline field vvia DCA customization. The front end template ce_accordionStart has to be customzied as well.
Maybe this workaround is a good solution. But perhaps the is another idea.
The text was updated successfully, but these errors were encountered:
It would also be cool if the tool wouldn't be bound so hard to headlines. Not every section might have an own headline. You could solve this by adding an invisible div with an id set if no headline is present:
Currently it is not possible to add an accordion to the content navigation.
The reason is that "Wrapper start" / "Single element" has no
headline
. There is only a fieldSection headline
. In general, it would definitely be very easy to use this field.BUT: it is only a textfield. There is no possibility to define the headline level. That will result in different problems (start/stop level could not be recognized, where to add the entry in the netsted list of the output).
My current workaround is, to replace the
Section headline
for accordion "Wrapper start" / "Single element" with theheadline
field vvia DCA customization. The front end templatece_accordionStart
has to be customzied as well.Maybe this workaround is a good solution. But perhaps the is another idea.
The text was updated successfully, but these errors were encountered: