====== Box Plugin ====== ---- plugin ---- description: Highlight particularly important parts of your wiki in boxes that stand out author : Christopher Smith email : chris@jalakai.co.uk type : syntax lastupdate : 2022-08-16 compatible : Elenor of Tsort, Frusterick Manners, Greebo, Hogfather, Igor depends : conflicts : similar : note, wrap tags : style, boxes downloadurl: https://github.com/Chris--S/dokuwiki-plugin-box/zipball/master bugtracker : https://github.com/Chris--S/dokuwiki-plugin-box/issues sourcerepo : https://github.com/Chris--S/dokuwiki-plugin-box donationurl: ---- ** While this plugin still works just fine, its functionality is subsumed by the [[plugin:wrap|Wrap Plugin]]. ** This plugin brings boxes to [[:DokuWiki]] allowing you to highlight particularly important parts of your wiki in boxes that standout. The plugin comes with the ability to make ordinary square boxes, snazzyTM boxes with rounded corners, boxes with titles and boxes of varying widths. DokuWiki markup is allowed inside the box - where pretty well anything goes - and inside the title where only text markup, links, smileys and the like should be used. It is probably sensible to set the style of the box you will most commonly use to be the default box. For details refer to the [[#style.css]] ==== Notes ==== * 2010-01-30 Copied and pasted below code in style.css and syntax.php (./plugins/box/..). Works with latest 'Lemming' version. * 2025-03-03 Works with Kaos, but adding that to the list of compatible versions broke the this whole Wiki ===== Acknowledgment ===== The rounded corners are based on [[http://www.cssplay.co.uk/boxes/snazzy.html|snazzy borders]] by Stu Nicholls of [[http://www.cssplay.co.uk|CSS Play]] which in turn were inspired by Alessandro Fulciniti's [[http://pro.html.it/esempio/nifty/|nifty corners]]. ===== Syntax ===== A simple box: the box contents Some more complex boxes the box contents the box contents the box contents The full syntax: ''**** contents text ****'' * //width// --- any legal CSS width value * //classes// --- any number of classes which use the styles in your template or the plugin's own stylesheet to determine the look of the box. The box plugins comes with the following classes already defined: * //round// --- box will have rounded corners * //blue// --- blue colour scheme * //red// --- red colour scheme * //green// --- green colour scheme * //orange// --- orange colour scheme * //left// --- float the box left within the wiki page * //right// --- float the box right within the wiki page if no classes are specified the default styles will be used, that is square corners in a colour scheme based on the default DokuWiki colour scheme. * //colours// --- 1-4 colours in CSS hex or RGB notation, e.g. ''#F00 #fcab94 rgb(255,255,0)''. The colours are applied in order to: - content background - title background - outer box background - borders if less than four colours are specified, the first colour is used for the missing colours. * //title text// --- text (including DokuWiki markup) displayed above the box contents, with distinct style. * //caption text// --- text (no markup allowed) displayed below the box contents, with distinct style. The opening ''****'' including the title must all appear on one line. The box contents can appear over as many lines as are needed. See the plugin in action [[http://wiki.jalakai.co.uk/dokuwiki/doku.php/test/boxes|here]]. The sample page shows all the styles available with the plugin. FIXME ===== Configuration ===== The plugin has no configuration settings, although you may want to review the default colour scheme in [[#style.css]] to ensure it is appropriate for your wiki. ===== Installation ===== Search and install the plugin using the [[plugin:extension|Extension Manager]]. Alternatively, refer to [[:Plugins]] on how to install plugins manually. To install the plugin manually, download the source to your plugin folder, ''lib/plugins'' and extract its contents. That will create a new plugin folder, ''lib/plugins/box'', and install the plugin. ==== Sources: ==== * Current: * Please see download and git links above * Previous DokuWiki versions: * [[http://dokuwiki.jalakai.co.uk/plugin-box.zip|zip format (6k)]], [[http://dokuwiki.jalakai.co.uk/plugin-box.tar.gz|tar.gz format (5k)]] * for DokuWiki 2006-03-xx [[http://dokuwiki.jalakai.co.uk/plugin-box-2006-03-xx.zip|zip format (5k)]], [[http://dokuwiki.jalakai.co.uk/plugin-box-2006-03-xx.tar.gz|tar.gz format (4k)]] **REQUIRES [[#security fix 2]]** * for DokuWiki 2005-09-22 [[http://dokuwiki.jalakai.co.uk/plugin-box.2005-11-25.zip|zip format (4k)]], [[http://dokuwiki.jalakai.co.uk/plugin-box.2005-11-25.tar.gz|tar.gz format (3k)]] **REQUIRES [[#security fix]]** ===== Revision History ===== * 2008-11-11 --- Add print.css, change plugin URL + other minor alterations * 2008-03-03 --- Security fix + add support for specifying colours in box syntax * 2006-04-25 --- XSS vulnerability fixed * 2006-04-20 --- darcs update only * markup updated inline with DokuWiki fixes for PType block * corrections to syntax description * minor style changes for line-heights * 2006-03-11 --- 2006-01-24 patch applied to non-darcs package; * support for all CSS length units added * styles added to support box nesting * lists can now be included in boxes * 2006-01-24 --- darcs update only (package release held until after next DokuWiki update) * support nesting of boxes * default style now uses DokuWiki CSS substitutions * 2005-11-25 --- Added caption text (displayed below main box content). Added left & right styles. * 2005-10-25 --- Bug fix for merged paragraphs in boxes (thanks Matthias). * 2005-10-17 --- Bug fix for some windows PHP installations (thanks Pablo). * 2005-10-12 --- Released. ===== Security Fix ===== This fix is only applicable to those using older versions box plugin with DokuWiki versions prior to March 2006. Those running a Mar 2006 or later version of DokuWiki should update the plugin using the [[#sources]] lists above. Also apply Fix #2 detailed below. === Instructions === * locate the file ''lib/plugins/box/syntax.php'' * open it for editing in a text editor * replace the function _boxstyle($str) (around line #150) with the code given below. function _boxstyle($str) { if (!strlen($str)) return array(); $styles = array(); $tokens = preg_split('/\s+/', $str, 9); // limit is defensive foreach ($tokens as $token) { if (preg_match('/^\d*\.?\d+(%|px|em|ex|pt|cm|mm|pi|in)$/', $token)) { $styles['width'] = $token; continue; } // restrict token (class names) characters to prevent any malicious data if (preg_match('/[^A-Za-z0-9_-]/',$token)) continue; $styles['class'] = (isset($styles['class']) ? $styles['class'].' ' : '').$token; } return $styles; } * save the file This restricts the characters available for use in any custom style names to alphanumeric characters plus dash and underscore (e.g. A-Z, a-z, 0-9, _ -). It also updates box width detection to support any valid CSS length value. See syntax for details. ===== Security Fix 2 ===== This fix applies to all versions of the plugin prior to Mar 3, 2008. It is recommended that users of the plugin upgrade DW and this plugin to the most recent versions. For those interested who wish to fix the vulnerability with out updating. case 'box_close' : $renderer->doc .= "\n"; if ($data) { - $renderer->doc .= "

".$data."

\n"; + $renderer->doc .= "

".$renderer->_xmlEntities($data)."

\n"; } $renderer->doc .= $this->_xhtml_boxclose(); break; Thanks to Andy Webber of Oracle's Ethical Hacking Team for discovering this flaw. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008-03-03 17:46// ===== To Do ===== ===== Bugs ===== * Boxes can overlay TOC at top of the page. CSS fix needed. **Render bug with IE 6.0** - Running box plugin with roundbox template. Scrolling (or if box is big enough just page refreshes) sometimes causes lines/blocks of the box to not be updated leaving the background colour on display. Managed to replicate problem on box home DokuWiki [[http://wiki.jalakai.co.uk/dokuwiki/doku.php/tutorial/boxes|here]]. The bad region seems to be bigger if the box is larger (more text in it). --- //[[ja@vibtech.co.uk|Jonathan Alexander]] 2005-12-06 14:49// >Found a fix that seems to work for me from [[http://www.communitymx.com/content/article.cfm?page=2&cid=C37E0|communitymx]] (thanks to Google) just inserted the code below under the "div.box .box_content" declaration in the style.css above. /* Hides from IE5-mac \*/ * HTML .div.box.box_content {height: 1%;} /* End hide from IE5-mac */ * **Missing

s (lots of ugly [[http://validator.w3.org|W3C-warnings]]):** foo bar results in this HTML:

foo

bar

as you can see, there's one

missing. --- //[[bernd@bzed.de|Bernd Zeimetz]] 2007-03-03 02:39 CET// \\ **solution**: change two lines in function render (near case 'box_open'): --- syntax.php 2008-02-27 23:44:08.000000000 +0100 +++ syntax.php.new 2008-02-27 23:55:23.000000000 +0100 @@ -129,9 +129,9 @@ case 'box_open' : if ($this->title_mode) { $this->title_mode = false; - $renderer->doc .= "

\n

"; + $renderer->doc .= "

\n
"; } else { - $renderer->doc .= $this->_xhtml_boxopen($data)."

"; + $renderer->doc .= $this->_xhtml_boxopen($data)."

"; } break; lines beginning with "-" are the original lines, the "+"-lines are the new ones. --- //[[stefan@kuchling.de|Stefan Kuchling]]// This patch has been added to the latest plugin version. Thanks Bernd and Stefan for your efforts. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008-03-03 17:46// ===== Tips ===== ==== Alternate Syntax & Allowing markup in captions ==== Great plugin! I've modified my copy and thought others might be interested. [[http://robmeerman.co.uk/coding/file_renamer|See example]]. FIXME Changes: - Syntax changed: ''**%%<<<%%** width classes | title ::: //content// ::: caption **%%>>>%%**'' - Markup allowed in captions - Title and caption may be over multiple lines (i.e. multiple paragraphs) - Width may be specified in %, px, em or ex //(now included in release version)// Being able to place markup in the caption is nice for when you want to draw attention to a note about, say, an alternative version of some software --- it looks really nice having the download link in the caption. It works well on my site, and the only problem it seems to have is that I can't nest boxes (not sure why). For complete code please see: [[boxes_mod|Modifed Boxes]] --- //[[robert.meerman@gmail.com|Robert Meerman]] 2006/02/24 17:13// > Hi Robert, Have you tried your syntax with the nesting patch, I briefly looked at your code and didn't see anything that should prevent nesting. Cheers --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-02-24 19:26// ==== Backporting to 2005-07-13 ==== Here's what I did to backport this box plugin to the 2005-07-13 release. * Add style.css to the end of your template's ''design.css'' and ''print.css'': $ cd .../lib/plugins/box $ cat style.css >> ../../tpl/template_name/design.css $ cat style.css >> ../../tpl/template_name/print.css * Apply the following patch: --- box-orig/syntax.php 2005-11-24 13:28:17.000000000 -0800 +++ box/syntax.php 2005-12-16 14:52:48.000000000 -0800 @@ -45,6 +45,19 @@ function getType(){ return 'container';} function getAllowedTypes() { return array('container','substition','protected','disabled','formatting','paragraphs'); } + + function syntax_plugin_box(){ + global $PARSER_MODES; + $this->allowedModes = array_merge( + $PARSER_MODES['container'], + $PARSER_MODES['substition'], + $PARSER_MODES['protected'], + $PARSER_MODES['disabled'], + $PARSER_MODES['formatting'], + $PARSER_MODES['paragraphs'] + ); + } + function getPType(){ return 'normal';} // must return a number lower than returned by native 'code' mode (200) @@ -54,9 +67,9 @@ * Connect pattern to lexer */ function connectTo($mode) { - $this->Lexer->addEntryPattern('(?=.*?)',$mode,'plugin_box'); - $this->Lexer->addEntryPattern('(?=.*?)',$mode,'plugin_box'); - $this->Lexer->addEntryPattern('.*?)',$mode,'plugin_box'); + $this->Lexer->addEntryPattern('(?=.*?\x3C/box.*?\x3E)',$mode,'plugin_box'); + $this->Lexer->addEntryPattern('(?=.*?\x3C/box.*?\x3E)',$mode,'plugin_box'); + $this->Lexer->addEntryPattern('.*?\x3C/box.*?\x3E)',$mode,'plugin_box'); } function postConnect() { @@ -182,4 +195,4 @@ } ==== More Verbose CSS with More Color Options ==== This is a very handy plugin! I started to play with the CSS to do some custom things (I'm going to use this plugin in 3-4 DokuWiki installations), namely to hide the inner border and a couple other small color tweaks. I ended up with something that I think it a bit more flexible to modify (separate definitions for separate borders), commented more (I tried to note some of the sections a bit better), and possibly more IE friendly (I think I fixed a problem with one of the background colors not displaying in IE 6). I'm no expert when it comes to CSS, so I can't guarantee I've done this 100% efficiently, but it holds up with every browser browsershots.org supports. The CSS can be see here: http://wiki.ryanjacobs.name/public/tech/dokuwiki_box_plugin_css FIXME In case anyone is interested... Cheers! --- //[[ryan.jake@gmail.com|Ryan Jacobs]]// ==== Add support for ODT export ==== This adds very basic support for the [[plugin:odt|OpenOffice/ODT export plugin]]; no colours; no alignment, no fancy formatting; but basic content is emitted. $ diff -u syntax.php.dist syntax.php --- syntax.php.dist 2009-06-22 06:45:22.000000000 +0100 +++ syntax.php 2009-06-24 12:55:14.000000000 +0100 @@ -157,6 +157,45 @@ } return true; + } elseif($mode == 'odt'){ + switch ($instr) { + case 'title_open' : + $this->title_mode = true; + $renderer->table_open(1); + $renderer->tablerow_open(); + $renderer->tableheader_open(1, "left"); + break; + + case 'box_open' : + if ($this->title_mode) { + $this->title_mode = false; + $renderer->tableheader_close(); + $renderer->tablerow_close(); + $renderer->tablerow_open(); + $renderer->tablecell_open(); + } else { + $renderer->table_open(1); + $renderer->tablerow_open(); + $renderer->tablecell_open(); + } + break; + + case 'data' : + $renderer->doc .= $renderer->cdata($data); + break; + + case 'box_close' : + $renderer->tablecell_close(); + $renderer->tablerow_close(); + $renderer->table_close(); + if ($data) { + $renderer->p_open('legendcenter'); + $renderer->doc .= $renderer->cdata($data); + $renderer->p_close(); + } + break; + } + return true; } return false; } ===== Discussion ===== Thanks for the plugin. My question is if there is something I can do to preserve a blank line in the raw text without using the '\\ ' syntax or by any other edit of the raw text? Thx & Bye --- [[user>pronto|pronto]] //2014-07-30 11:31// ---- Thanks, for the plugin, it looks really great. However I want to use it to highlight different content. For example I'd like to use to highlight math. How would I have to modify the source to parse a different CSS class to ? > You need to change the base pattern (in connectTo and postConnect) to math from box. For each different exit pattern you need another plugin, so the plugin name needs to be changed and the references to it in connectTo and postConnect. A better approach maybe to use ... , ... and adjust/add style names so the appropriate colours and corners show for the particular name. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2005-10-29 10:07// ---- Rather than using lots of different predefined styles, how about using a syntax similar to the phpBB colour plugin, and allow the user to define their choice of colours exactly? --- //[[webmaster@lajzar.co.uk|ta' Lajzar]] 2005-10-30 02:16// > Maybe. I didn't want to define styles as colours. It would be better to choose style names semantically, e.g. error, warning, information, syntax, formulae, alert, etc. However the meaning of each box style is likely to change from wiki to wiki, so I gave them neutral but descriptive names. For all that, I'll look at adding an optional syntax for those that want it. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2005-10-30 10:39// >> But if people use boxes in a page that is ''included'', they can then have the semantic context just as easily, and this retains the extra flexibility of freely defined colours for the box syntax. --- //[[webmaster@lajzar.co.uk|ta' lajzar]] 2005-10-31 07:27// Individual colour specification has been added to the latest release. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008-03-03 17:46// ---- The code return by the plugin is not really standard XHTML, it's because all B tags are empty. In order to correct that, you must write   in all b tag in lines $html .=" \n"; //and $html .= " \n"; > To my knowledge the xhtml standard does't mind empty elements (refer [[http://www.w3.org/TR/xhtml1/#C_3]] and the w3c validator doesn't flag them either as an error or a warning. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2005-10-31 15:17// ---- Box plugin doesn't work for me. I'm running a fresh install of DokuWiki 2006-03-09 with no other edits, plugins, or templates installed. Box plugin was installed via the plugin manager. [[http://www.ssdonline.us/wiki/doku.php?id=wiki:playground]] --- //[[smouser@verizon.net|Scott Mouser]]// > Plugin is working, styles aren't being picked up. I've added a comment and some ideas on your playground page. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-03-24 01:22// >;;>Thank you. Clearing the cache is exactly what was needed to get things working. I didn't see that mentioned anywhere else. I will go ahead and file a bug report, because you are right, the .css should have been regenerated after the plugin install. --- //[[smouser@verizon.net|Scott Mouser]]// >>>DokuWiki and plugin manager have been patched to expire the cache and ensure a new CSS will be generated after any plugin is installed. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-04-19 03:14// >>>>Can someone post HERE how to clear the cache, because www.ssdonline.us seems to be down. >>>>I already sorted it out, and for everybody else, use the **[[plugin:cacherevisionseraser|Cache and Revisions Eraser]]** plugin! ---- This plugin has **XSS vulnerability**! Try this in IE: XSS test This fix works for me (lines 160-168): foreach ($tokens as $token) { if (preg_match('/^\d*\.?\d+(%|px|em|ex|pt|cm|mm|pi|in)$/', $token)) { $styles['width'] = $token; continue; } $token = trim(ereg_replace('[^a-zA-Z0-9_-]','',$token)); // <<-- this is new line $styles['class'] = (isset($styles['class']) ? $styles['class'].' ' : '').$token; } > Thanks Main script and plugin sources updated. Also see [[#security fix]]. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-04-25 18:17//. ---- Update of plugin silently overwrites style.css. Is there a solution preservingin localized style.css? E.g., a localization directory which overlays any CSS properties? Thanks. --- //[[burt@cs.miami.edu|Burt Rosenberg]] 2006-05-22 02:56// > How about [[devel:css|./conf/userstyle.css]]? That seems to work. Now, to figure out url() macro in .css file processing --- //[[burt@cs.miami.edu|Burt Rosenberg]] 2006-05-22 04:12// ---- I'd like to use ''===== Level 2 Headline ====='' inside of the ''...''. How can I do that? Thank you in advance. > At present you can't, at least not directly. It should be possible to use the [[plugin:include|include plugin]] syntax within a box. The included page will then display inside the box. \\ \\ Note: It would be best to use my [[http://wiki.jalakai.co.uk/dokuwiki/doku.php/tutorials/include|alternate include plugin]] as it doesn't try to merge the included page into the current page's section structure - which could give unexpected results. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-06-16 01:41// >>That's exactly what I did but I didn't know about your "alternate" version of the include plugin so I hacked the original one:) ---- Looks like the layer for the box obscures the TOC box if a ''%%%%'' is placed in the first paragraph or two (content depending of course). > Yes. I have added it to bugs. I would guess a CSS fix is required either to TOC or box. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-07-04 23:42// ---- I think you should mention that the plugin will only work if you have //‘Allow embedded HTML’// turned on in DokuWiki's config. I just spent ages wondering why I couldn't get it to work, until I realised this. :-\ --- //[[xxxmadraxxx@gmail.com|madra]] 2006-08-05// > It doesn't require "allow embedded HTML" turned on. However, editing your wiki configuration files will have expired all DokuWiki's caches forcing regeneration of pages and CSS. Both of which are required for boxes to appear. As mentioned above, its a known bug fixed in [[changes#release 2006-11-06]] & preceding release candidates. \\ ---- \\ \\ I have a small issue with boxes and I was wondering if someone could help me perhaps? When I put a box on a page and try to put some spacing for new lines after the box with the usual markup it doesn't seem to display correctly. The text always appears to the right of the box no matter what I try. \\ I also noticed that on this site that there seems to be no need to use the typical markup for a new line. Why is that? \\ > Boxes styled left or right are floated. A cleared element will need to appear after the box to stop subsequent content floating next to it. You maybe able to work something with the div/span plugin. I'm not sure what you mean your last sentence. You only need to use %%\\%% for a single line break in a paragraph or to add extra line breaks between paragraphs. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2006-08-15 09:33// Cheers for the update Chris but I'm not sure what you mean by a cleared element? So without the div/span plugin there is no way to resolve the issue? > You could also use the **clearfloat plugin** (search for it on [[:plugins]]). Others suggested doing it via [[entities]] (unfortunately I haven't found the suggestion anywhere). Just put something like this ~CL~
into ''conf/entities.conf'' and use ''~CL~'' after each relevant box. (Better to use update-proof ''conf/entities.local.conf'', and add strings like



--- [[user>Rainbow_Spike@derpy.ru|dr-yukon]] //2020-09-06 14:32//) What about a | before and after the text? ---- Thanks for the great plugin. I really enjoy the boxes :-) I have one suggestion/bug report. It seems that the current implementation of boxes do not like nested boxes. For example, I'd like to have something like this. {{xvdm:module:apdf:2d-apdf-overview-1.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-2.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-3.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-4.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-5.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-6.jpg?100|}} If I do that I get overlapping boxes. However, If I do:
{{xvdm:module:apdf:2d-apdf-overview-1.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-2.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-3.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-4.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-5.jpg?100|}} {{xvdm:module:apdf:2d-apdf-overview-6.jpg?100|}}
Then it produces something what one would expect. Most probably my work around produces a completely incorrect HTML code, thought Firefox shows quite nice results :-) ---- Please add a ''print.css''. I needs not very much content, just ''div.box.left{float:left}'' and such. Currently, a series of ''...'' looks pretty weird in print mode -- and takes up many papers -- without a float:left. --- //[[gviktor@gmail.com|Viktor Söderqvist]] 2007-02-28 05:06// > Added --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008/11/11 06:26// ---- A toggle to clear the floats would make a nice option as I normally do not prefer text to wrap around the box. The only time I let the text wrap is when my boxes are near the ToC. I hard coded some float clearing since I generally do not want text wrapping around the boxes, however, that can mess with the ToC Div. Hence a toggle would be great. ---- :!: This creates bad XHTML, apparently there are missing closing

in the box_content divs. FIXME\\ > fix? 143 $renderer->doc .= "

\n";

was missing ---- Hi - Thanks for a terrific plugin. I am having problems with boxes and captions when printing. I copied the plugins/box/style.css -> plugins/box/print.css and it works, but when I include a caption at the top an extra line is inserted between the box top and the caption. I'm using the monobook template. [[http://www.kabissa.org/wiki/doku.php?id=playground&rev=1178805954&mbdo=print|Click to see an example in my wiki playground]]. Would be most grateful for any suggestions. ---//[[http://www.saidia.org|Tobias]] (5/10/2007)// ---- Nice plugin. I'm wondering if it is possible to have the caption work like the title, where links can be embedded in it? ---- Hi, I have a lot of citation. I often copy and paste. Is it to possible to keep carriage return and avoid to add manually "%%\\%%" at the end of each new lines ?\\ Whereas good plugin. \\ \\ I noticed when I copy the code of the third box of [[http://wiki.jalakai.co.uk/dokuwiki/doku.php/test/boxes]] and paste here (or on my DokuWiki), the text box is on only one line. I don't include the caption \\ this is also boxed e.g. ** this is also boxed ** \\ \\ On your test page, the text box is on 3 lines. Why 1 line, me and you 3 lines on your page ? I copy and paste exactly the same source code. In your page, the carriage return is kept. \\ How can I have the same behavior ? So I will able to copy and paste keeping CR. > Yes. See the [[plugin:linebreak|linebreak plugin]] --- //[[chris@jalakai.co.uk|Christopher Smith]] 2007-07-26 13:08// >> Also see the [[plugin:xbr|linebreak renderer]] --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008/11/11 06:26// ---- Hi Chris, Very nice and useful effects. Any thoughts about adding an icon on the title bar ?\\ See for example http://www.headshift.com/\\ I just don't understand how they did that!\\ Cheers, Peter Chan 2007-10-02 ---- Hi -- I am trying to use boxes in the latest DokuWiki (2006-06-26b)but it doesn't seem to want to work. The only plug-in behavior that I've been able to identify is with markup in captions. If I bold the caption it displays the asterisks. If the plugin was just whiffing, wouldn't the markup work? Why would this not work? Thanks. Rick Reynolds 2008-01-16 > Formatting isn't currently supported in captions. However the modified boxes plugin, which uses a slightly different syntax does allow formatting in captions. See links above. --- //[[chris@jalakai.co.uk|Christopher Smith]] 2008-03-03 17:46// >>That is right, but box_mod is not updated to support DokuWiki 2008-05-05: little layout errors, especially when there are more than one boxes on the page... In my experience works far more smoothly. [[gijsh@sherpanet.nl|Gijs van Gemert]] ---- It started working for me when I changed to the dokucms template. With the default template it won't work for me. 2008-02-11 ---- Is it possible to add support for absolute (or minimum) height for the boxes? I've tried doing it myself, but both my knowledge of PHP and CSS is insufficient to implement this. > Yes, there is a height support now. Check my modified plugin: [[plugin:boxwh|boxwh plugin]] ---- Any chance of allowing the text colour to be altered (as black on dark colours is often unreadable)? Bob 4-Apr-08 ---- I noticed it was necessary to purge cache to allow new plugin's CSS instructions to be inserted: * I followed DokuWiki [[:devel:caching]] advices, * I touched conf/local.php, edited and saved it ... * I selected 'embedded HTML' in config form still, no div.box CSS instruction in my CSS sheet, and box wont display properly. I finally found a file permission issue: ls -l box/style.css -rwx------ 1 box/style.css should that be fixed in archive.tgz ? ---- Thanks for this plugin.\\ I made a little change on 3 lines in **syntax.php** to produce an XHTML compliant document. (It is just some space missing characters...) (line 133) $renderer->doc .= $this->_xhtml_boxopen($data)."

_title_colours}>"; ... (line 139) $renderer->doc .= "

\n
_content_colours}>"; ... (line 153) $renderer->doc .= "

_title_colours}>".$renderer->_xmlEntities($data)."

\n"; * Add a space character between **class='box_title'** and **{$this->_title_colours}** * Add a space character between **class='box_content'** and **{$this->_content_colours}** * Add a space character between **class='box_caption'** and **{$this->_title_colours}** //---[[http://www.cyclotronp.net|ZebulonT]] -- 2009-07-05 16:37// ---- I have new dokuwiki version (Anteater). Box plugin now puts one
more on the end of a box and kills all remaining layout and styles. Is it a bug of box plugin or dokuwiki itself? //Pletiplot -- 2010-12-20// ---- Please correct your CSS. The rule @CHARSET "UTF-8"; in your print.css is not valid. --- [[user>flam]] //2011/01/05 12:03// ---- Can we add a close button to it, so We can use it as notice? ---- :!: **Box** plugin not able to work correctly with **Include** plugin. Commonly **Box** hold any content in ''div.box div.xbox div.box_content''. But **Include** insertions drop down into ''div.box div.xbox''. Maybe it's due to incorrect state of //getType// or/and //getPType//. --- [[user>Rainbow_Spike@derpy.ru|dr-yukon]] //2019-01-03 13:26// ---- Basic Dokuwiki engine works with images only through pixel widths. This plugin can be used as the percent zoomer. Add div.box.img > .xbox > .box_content > a > img { width: 100%; width: -moz-available; width: -webkit-fill-available; width: stretch; } in ''/lib/plugins/box/style.css'' and syntax it as ''%%{{%%your image}}'' for inscreen zooming --- [[user>Rainbow_Spike@derpy.ru|dr-yukon]] //2020-09-06 14:37// ---- Works with DokuWiki version Kaos, but when I added that to the list of compatible versions the whole page went blank. So I took out the change and put this comment in instead. James Powell, March 3, 2025. ----