WebCMS

Yeah, it's not applying the CSS and not signing out.

I just wanted to add 2 links and remove 1 link which cannot be done precisely. Is there any documentation on how to remove existing links? I suggested 10 footer link slots for any other sites' requirements who might need so many just in case as unused slots shouldn't be rendered anyway.

Please consider this at least for v5 and it would serve as a Value Proposition to sell more cloud subscriptions -

Currently, there is no way to precisely position new links or remove existing links in the footer without modifying templates because there are only 4 positions for newly added hooks (before/after opening tag and before/after closing tag). For instance, some sites incorporate Cookie Policy into Privacy Policy page and there is no need for the Cookies link in the footer and no way to remove it without modifying templates or using JS. Please add 10 slots to add links in the footer so admins can add/remove/position links in those slots that you could render in the footer. Most sites would 5-6 link slots.

It may be due to an old version you are using

You may be using self-hosted and not up-to-date? In my Dashboard on IC Cloud, it says "Invision Community v5.0.0 Beta 3"

When you select Hook Application dropdown > System, it is 4th item in the System dropdown -

You can create a template from Appearance > Themes > Theme Designer: Templates > Hook Select dropdown values -> System, front/global/footer, themes, after closing tag -> and add links (<li> for consistency but can be just <a> elements too) in the Content box, like so: <li><a href="/help/">Help</a></li> <li><a href="/terms/">Terms</a></li> The above will add the links after the Themes dropdown in the footer (no way to precisely position the links in the footer as there are only 4 fixed positions for the target -> before/after opening tag and before/after closing tag). These hooks will not get overwritten when we apply an update (unlike the template files in v4). However, I haven't found a way to remove/hide existing links like Cookies in the footer (maybe use nth-child CSS and JS). Also could not find parent-child hierarchy of themes (like it exists in v4) so we could create a parent CSS that gets shared across child themes. Please implement this in v5. Existing essential features in v4 cannot be taken away in v5. That would be a bummer.

Here is a suggestion I already made (will re-post it here) - https://preview.invisionalpha5.com/topic/232-mobile-menu-tabs-configuration

What hook to use that would render on both desktop and mobile layouts in the header (in between nav-menu and user-menu)? The HTML will have a div with an ID and so the div cannot be duplicated for desktop and mobile layouts.

For reporting issues, is this the right place? https://invisioncommunity.com/ic5bugs/bugs/ I reported some issues on alpha site Forum. Will they be considered?

https://preview.invisionalpha5.com/ https://preview.invisionalpha5.com/bugtracker/ https://preview.invisionalpha5.com/tags/suggestion/ These look like an afterthought but has more activity - https://invisioncommunity.com/forums/forum/539-beta-discussion/ https://invisioncommunity.com/ic5bugs/bugs/ https://invisioncommunity.com/ic5bugs/

Similar to how RESTful APIs are implemented using versioning for external clients, will there be an option for users to switch between v4 and v5 UIs pointing to the same database? For instance, the new v5 UI could be pointing to same the doc-root while the v4 UI could be relocated to /old. Users could still use /old for v4 UI until they get used to v5 UI for which /old is not required. Or more ideally, the /old could be stored in the session as a preference so both UIs can be pointed to doc-root. Site owners could set up an Announcement deadline by which the /old version will not be available to users and they should get used to the new version before that. Sites like Google offer such feature with an option to switch back-n-forth whenever they release new versions - New UI Switch to Classic UI That would make the transition seamless for site owners and users.