- Priority: 0
- Status: Closed
- Theme: Alysum
-
Assigned To:
Marek
- Private: No
- Open Date: 22.10.18, 17:03
- Opened by: Asier Iturralde
- Closed by: Marek
- Closed on: 28.12.18, 14:59
- Reason: Closed
- Comment: Glad to help!
Ticket #13111 - Issues removing social accounts from footer
Hi,
We are having some issues (actually we don´t know how to do it) removing some social accounts from the footer. What we tried is to disable the ones that we are not using from the Alysum Settings → Social Accounts section, but it did not work.
We even tried to edit the widget from the footer builder and delete the “#” from all those social accounts that we were not using but no success.
How do we proceed in order to delete them?
We using prestashop 1.7.4.3 and alysum version 5.2.5
webiste: https://perpetummobile.store
Kind regards,
Ibon
Comments
Hi,
The only way I found to remove them was to set display:none to all non-needed social icons…
Hi, Asier.
Go to Footer Builder and configure it as you need
Hi,
The only way I found to remove them was to set display:none to all non-needed social icons…
We did that. We edit the widget and remove the “#” symbol from all those social elements that we were not using.. Still they are appearing in the footer.
So it’s solved now?
We did that. We edit the widget and remove the “#” symbol from all those social elements that we were not using.. Still they are appearing in the footer.
It is solved only using this css:
#socialnetworks .rss {
}
Isn´t there any way to use the Asylum settings to enable/disable social accounts?
It works very easy, if there is no a link, the icon will not be displayed http://take.ms/hvkTA
It is solved only using this css:
#socialnetworks .rss {
}
Isn´t there any way to use the Asylum settings to enable/disable social accounts?
Please see attached the screenshots. Empty social icons still appear…
but I see only four icons there http://take.ms/hIpKH
Please see attached the screenshots. Empty social icons still appear…
Because we created add some css to remove the rest (check screenshot)
Ok, I see. We will check it out and make a fix in the next update