Placing subparts somewhere else

Help for integrating the Laravel package
Forum rules
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Yvler
Posts: 33
Joined: 04 Jun 2015, 10:15

Placing subparts somewhere else

Post by Yvler » 22 Jul 2015, 13:11

Hi Aimeos

At this moment we're trying to rearrange the layout.
For this, we would like to have the search bar next to some buttons (my cart, login) and the navigation under it with some buttons next to it.
Is there a way to rearrange this? Or do we have to put the html code for the buttons in the search layout?

User avatar
aimeos
Administrator
Posts: 7836
Joined: 01 Jan 1970, 00:00

Re: Placing subparts somewhere else

Post by aimeos » 22 Jul 2015, 13:41

Looks like it would be the easiest to add your buttons to the templates of the filter component if you don't need Laravel specific code there. If you need to rearrange the subparts of the component itself, you can do it by configuration.
It would be also possible to add the component twice and hide the parts that shouldn't be shown via CSS. You can also do a lot with CSS floating.

Yvler
Posts: 33
Joined: 04 Jun 2015, 10:15

Re: Placing subparts somewhere else

Post by Yvler » 22 Jul 2015, 14:22

Ok
So no other way to retrieve a part of the aimeos_nav, put it in another section and yield it? :)
We have a button displayed depending if the user is logged in or not. These buttons should come next to the search bar and are using the Laravel "url" principle

User avatar
aimeos
Administrator
Posts: 7836
Joined: 01 Jan 1970, 00:00

Re: Placing subparts somewhere else

Post by aimeos » 22 Jul 2015, 14:41

Yvler wrote:Ok
So no other way to retrieve a part of the aimeos_nav, put it in another section and yield it? :)
No, subparts are not viable on their own but you can put the "aimeos_nav" component twice in your template. The only downside in Laravel compared to e.g. TYPO3 is that you can't configure both instances independently, so the HTML code for the tree and attribute filter would be added twice as well even if you don't see it.
Yvler wrote:We have a button displayed depending if the user is logged in or not. These buttons should come next to the search bar and are using the Laravel "url" principle
Depending on the layout, I would try to float the search bar next to your buttons and display the categories in a normal way so they will be placed below. It's quite interesting how much you can do with CSS without touching the HTML code :-)

Post Reply