PayBas wrote:I'd try to move away from using: <img src="{T_EXT_THEME_PATH}/images/portal/portal_user.png" width="16" height="16" alt="" />
First of all so that it's easier to replace icons without having to edit all the templates (simply assign a CSS class instead, and define the icons in portal.css
Secondly, because {T_EXT_THEME_PATH}
doesn't really like template inheritance. If a style inherits from proSilver, it will try to look for files with {T_EXT_THEME_PATH}
in the path inside the child's path. This is "good", but having to copy a single .css file to another ext style folder is easier than having to copy all the icons etc. as well.
I think this mainly still exists due to issues with theme paths we had in earlier versions of 3.1.
I'll try to get rid of this.
Peter77sx wrote:I think in responsive mode it could look more cleaner with 1 column and not more.
Derky has mentioned something similar here:
https://github.com/board3/Board3-Portal/issues/243
I'll be glad to get more input though.
watisnf.nl wrote:Marc, my 3.0 Board3 Portal is saying that it's outdated and that there is a new version available. It's redirecting to this extension (announcement on your board) please keep in mind that not every user knows that a extension isn't a modification. They might want to try and update it...

Thanks. I forgot that the this would change while updating the version check file. Anyway, more reasons to move to the new json format for RC1.
Mess wrote:Great to see this will be ported aswell. Any hope for portalview in this new version

I first tried to get the portal up and running. There has been no final decision on portalview. I might be able to add it once the portal gets closer to a stable release. However, it might be another extension that requires this one.