Category: Theme: Look & feel, Styles, CSS, Theme Control Center
Theme: Look & feel, Style, CSS, Theme Control
Show subcategories objects
| Name | Type |
|---|---|
|
Legacy theme Akwa fails in 2.0
Legacy mod theme Akwa causes blank screen on 2.0. |
tracker item |
|
List GUI contrast issue
See: {img src="https://dev.tiki.org/tiki-download_item_attachment.php?attId=496&display" thumb="y"} |
tracker item |
|
Login box in middle column small
Gary knows about this already - it was caused by his attempt to make modules a certain size in the middle column. Fix o nthe way |
tracker item |
|
Login prompt alignment issues with coelesce theme in Firefox
{syntax type="tiki" editor="plain"} When using the coelesce theme on v4.1 and using Firefox 3.5.7 on Ubuntu 9.10. Screenshot -> http://i.imagehost.org/0558/RUR_screenshot.png (external link) The problem did not occur using Chrome. -- I also posted this in the forums.. |
tracker item |
|
Logo is fuzzy on nextdoc and nextdev
Look at nextdoc and nextdev, the logo on the top right is fuzzy, looks like because the url of the image is "http://nextdoc.tiki.org/preview909" and the preview image is fuzzy. On the other hand, http://nextdoc.tiki.org/display909 is much better. Why is it using preview instead of display? Shouldn't logo use display? |
tracker item |
|
Logo module and look and feel related preferences should be merged
We have actually the logo module with several preferences and parameters: http://doc.tiki.org/Module-logo We have also the look and feel related section (logo): http://doc.tiki.org/General-Layout-Options#contentlook_generallayout-1 We need to merge those: * On the look and feel section it says for years (before Tiki 12) that it will be merged. * Some parameters seems already used by both * Some parameters are here and not there (site icon which is needed for bootstrap layout - brand image) * ... I t is important as it is one of the first settings visited by new users. |
tracker item |
|
Look & Feel for suite.t.o is currently (14.x) worse than expected
Look & Feel for http://suite.tiki.org is currently (14.x) worse than expected. It seems as if no one could tweak the look and feel of that domain/perspective/whatever handles the suite.t.o layout/look&feel Even http://tikisuite.org displays an enormous logo in firefox for me, I don't know why. Maube it's a known temporary issue, but just in case, I'll drop an item here... |
tracker item |
|
Look and Feel; Fixed topbar offset changed to Fixed-top navbar height parameter with a non expected behaviour
On Tiki 24 on the Look and Feel control panel (tiki-admin.php?page=look) we have a parameter "Fixed topbar offset" and it allowed me in the bootstrap classic layout to control the space between the topbar and the main content (middle_outer), adding a padding-top style to the body. It wasn't modifying the height of the topbar. Tiki24: {mediaplayer src="display1881"} In Tiki 25 I understand the parameters was renamed to "Fixed-top navbar height" and is now applied not only to set the body padding-top style but also used in some calculation for the topbar (header) height. (may be by adding additional space to be filled, not necessarily changing the real height value) {mediaplayer src="display1882"} This is a very unexpected behaviour and change from Tiki24. Not using CSS but only the admin interface is not possible anymore and I need to write some CSS to override the actual behaviour. If we need a parameter for the navbar height, we should have a parameter for it. I think we still need the previous "Fixed topbar offset" parameter to work as previously. Else it is better not to have anything that interfere (only through css customisation) |
tracker item |
|
Look&Feel, Themes; Adding basic information about a the theme (Author, Documentation)
As discussed during the TRM January 2022: https://tiki.org/Roundtable-Meeting-2022-01 We would like to add an option for documentation link that comes with a theme (more and more theme need documentation). We discussed the idea to add a manifest; ^ Something human readable like author: blabla documentation: https://bla This can be edited by hand by a non coding themes author I'd say plain text but yaml is also OK. ^ |
tracker item |
|
luci luci
This should be migrated to the community site, and handled with ((doc:Organic groups)) and ((doc:User Trackers)) |
tracker item |
|
make plugin pivottable look and feel (3rd party css) adapt to currently chosen theme style
make plugin pivottable look and feel (3rd party css) adapt to currently chosen theme style See it explained in the following screencast: {mediaplayer src="https://seeds4c.org/tiki-download_file.php?fileId=465&display=y" type="webm"} |
tracker item |
|
Make print icon optional
We now need to fiddle in the templates to remove the print icon. In many cases, a print option is not useful. Need both a tiki_p style permission and a feature_print style feature for this. Need to document the actual names we used, too. One tiki-wide setting to deactivate all printable pages all links to these pages (with the little printer icon). This will also be useful for http://mobile.tikiwiki.org/ Let's try to do before 1.9.1 obs: waiting for cvs to unlock to commit |
tracker item |
|
Make RSS feeds page look nicer
Please see: http://themes.tikiwiki.org/tiki-forums_rss.php?ver=2 The logo should be the site logo, if available. Make sure of i18n Make more generic. ie : no "Tiki RSS feed for forums". It should be just RSS for forums. Test in various browsers. Especially IE6, IE7, and FF2 |
tracker item |
|
maketoc needs backlinks from headings to TOC, heading formatting options, outline numbering, etc.
A small collection of related issues with maketoc: ^{maketoc} -=Maketoc issues=-^ !!! ''TOC and heading type sizes'' * This is an issue that seems to crop up repeatedly on tw.o. Users would like to be able to easily control type size of both the TOC itself and headings created by maketoc. Type size for both seems to be theme-dependent now, with many themes using very large type size for headings, some with a type size for TOC entries that is too small for users with only slight vision loss. It would be a Good Thing if TOC and heading type sizes could easily be set globally, per object type, and by category, with switches available to vary those settings on a per page or object basis. !!! TOC and heading character attributes * It would help reduce inconsisistencies in TOC and heading character attributes (as in this tracker item) if the attributes could be set globally, per object type, and by category, with TOC switches available to vary those settings on a per page or object basis. However, the ability to manipulate emphasis within a single TOC/heading entry should be retained, so that for example, a single word could be italicized in a TOC/heading entry. !!! Vertical linespacing between headings and text * Under some themes, vertical linespacing between text and headings is too much for taste, or as in the theme affecting this tracker item, too small for taste. This is another setting that should be unleashed from the themes and made easily selectable by a Tiki admin through global, category, and object type settings, with switches for per page or object variation. !!! ''Backlinks from headings.'' * Links from the TOC to headings are now 1-way. For larger pages, maketoc would be much more user friendly for those viewing pages if clicking on a heading would take you back to the TOC. !!! Outline numbering. * TOC formatting and heading formatting would be friendlier to the eye if both could be assigned numbering schemes such as 1., 1.1, 1.1.1, 1.2 or I., A., 1., a., II, etc. Settings might be implemented as described for ''TOC and heading formatting.'' If developed, this might be implemented for lists as well. !!! Headings indentation. * Many power users in the word processing and outliners worlds expect headings to inherit the indentations of the corresponding TOC entry. This would help break up the visual clutter that happens when many headings are close together vertically as a result of short text elements separating them, as in this tracker item (but it is far worse when there are subtopics and corresponding subheadings). Settings might be implemented as described for ''TOC and heading formatting.'' !!! Text indentation * Many people used to word processors' outlining or stand-alone outliners expect text to be left-indented one tab more than its heading. Relevant settings might be implemented as described for ''TOC and heading formatting.'' !!! Associated features * Display current settings in editor, change current settings from editor. Make changes to settings made from the editor apply only to the object being edited, so that users do not accidentally apply per object settings to other objects. Admins should have option to disable deviations from admin-set settings. * maketoc is commonly used in conjunction with list features. Any changes to maketoc should not unintentionally impact the list feature and ''vice versa.'' * Need to ensure that all enhancements suggested render correctly when Tiki objects are exported as PDF. !!! Future options * Future options might be kept open by maintaining compatability between Tiki objects containing maketoc elements and various formats used by outliners such as OPML, XOXO, OML, or OpenDocument XML. (See corresponding Wikipedia articles.) E.g., it might be feasible at some point to directly export an outline file to Tiki where it is imported as a wiki or blog page and ''vice versa.'' |
tracker item |
|
Missing Tracker Item #649
This tracker item could not be found |
tracker item |
|
menus are not shown any more to anonymous, at least
Since some weeks ago, afaik (April 2008, or so), menus and menu options cannot be seen for anonymous on several sites that I admin, including edu.tikiwiki.org, if you select some themes. Example: moreneat.css On others, like http://moviments.net/ilp (using nornia.css), the menu on a module assigned to anonymous and registered, was shown when you logged in. Right now I've just assigned thatmodule to admins only, and used menupage module, which works fine. But I can re-set the previous config. is somebody wants to reproduce the missworking. |
tracker item |
|
Minify and cache js and css files, with an admin panel to refresh
Productization: Create admin preference to enable/disable minify https://bugzilla.mozilla.org/show_bug.cgi?id=502092 Implement Admin panel/setting to flush/rebuild Minify cache https://bugzilla.mozilla.org/show_bug.cgi?id=497703 [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=minify&product=support.mozilla.com&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=|All "minify" related] This cache should also be deletable http://code.google.com/p/minify/ |
tracker item |
|
Missing blueberry theme option in Fivealive-lite
I wanted to edit the CSS for themes/fivealive-lite/css/blueberry but there is nothing in that dir? |
tracker item |
|
mobile doesn't recognize theme style in Look & Feel admin panel.
{syntax type="tiki" editor="plain"} Using mobile mode, from a PC with Chrome (on GNU/Linux, in case it matters). I clicked on "Switch to mobile site" in nextdev.tiki.org, and then when you go to "Admin home > Look & Feel", the theme style shown there is "abse" and not fivealive, so that if you save any setting there in L&F, you are switching the theme for the non-mobile mode (and you will not notice since you as admin are still in mobile mode). |
tracker item |
|
Modals in Quartz theme are too narrow
The modals that popup when editing a tracker item are way too narrow. Could there be an option to make them wider in the next release? Or if you are in the know, what CSS setting can I change to make the modals bigger? |
tracker item |
|
Mods: broken install of Kubrick theme
When trying to install: {img src=images/code.png}%%% {CODE()} Warning: copy(mods/themes/kubrick/themes/kubrick/kubrickheader-original.jpg) [function.copy]: failed to open stream: No such file or directory in lib/mods/modslib.php on line 375 themes/kubrick/themes/kubrick/kubrickheader-original.jpg to templates/styles/kubrick/kubrickheader-original.jpg impossible to copy {CODE} |
tracker item |
|
Module "events" breaks themes
{syntax type="tiki" editor="plain"} Assign the module ''events'' on the left, and you get a weird looking of the left menu, and a disappering content on the right side. Assign it to the right side results just in wrong textcolors for the left menu. In both cases the bottom bar will be shown in the menu (on the corresponding side where the events module is assigned). Tested with all stadard themes, for all the same result. And it doesn't show a calendar with events, so it's useless at all. Tested with firefox 2 and 3 under linux. Btw: Module calendar also shows no calendar, but at least it doesn't break the themes. |
tracker item |
|
Mouseover plugin : Data & param should be inverted
Typically, mouseover is to show more text over a small snippet. To save screen real estate. So the data in the mouseover will typically be much large than the text. Plus, I may want wiki syntax parsing in the mouse over part. It is now: {img src=images/code.png}%%% {CODE()} {MOUSEOVER(text=text that goes to mouseover)} snippet that is moused-over {MOUSEOVER} {CODE} It should be : {img src=images/code.png}%%% {CODE()} {MOUSEOVER(label=snippet that is moused-over)} text that goes to mouseover {MOUSEOVER} {CODE} Plus, this is a very cool plugin. It should be in main code base, like the THUMB plugin. |
tracker item |
|
mozilla.css fullscreen requires Top Bar
The theme using mozilla.css places the full screen icon mostly behind the right-side modules unless the Top Bar is enabled. |
tracker item |
|
Dialog, Multilingual, CSS; Buttons choice and position are reversed in RTL
{syntax type="tiki" editor="plain"} Reload page button is yellow (warning) and placed left => Should be right Close dialog button... We have already an X to close this dialog not sure we need this button. Anyway, it shouldn't be a plain button with a lot of text. To be consistant with other "cancel" actions in Tiki it should just be close, a X and/or outlined. {img fileId="1894" thumb="box"} |
tracker item |