Help / Site Specific Markup
Help.SiteSpecificMarkup HistoryHide minor edits - Show changes to markup Added lines 736-737:
To have a button instead of a text only link set button=1 instead of button=0. Added line 736:
Changed line 735 from:
to:
This is an example with init=hide, to have the section visible rather by default use leave out the init=hide bit. The Added line 735:
Changed line 744 from:
to:
>><< Added lines 746-748:
For more on this see http://www.pmwiki.org/wiki/Cookbook/Toggle Added lines 729-744:
Collapsible TOC
%rfloat% (:toggle toc init=hide hide="hide table of contents" show="show table of contents" button=0:) [[<<]] >>id=toc rframe font-size:smaller<< !!Contents (:num:) (:toc:) (:indent:) >><< Changed line 3 from:
(:toggle toc hide="hide table of contents" show="show table of contents" button=0:) to:
(:toggle toc init=hide hide="hide table of contents" show="show table of contents" button=0:) Changed line 3 from:
(:toggle menu hide="hide table of contents" show="show table of contents" button=0:) to:
(:toggle toc hide="hide table of contents" show="show table of contents" button=0:) Changed line 5 from:
to:
Changed line 3 from:
%rfloat(:toggle menu hide="hide table of contents" show="show table of contents" button=0:) to:
(:toggle menu hide="hide table of contents" show="show table of contents" button=0:) Added line 3:
%rfloat(:toggle menu hide="hide table of contents" show="show table of contents" button=0:) Deleted lines 8-10:
(:toggle menu hide="hide contents" show="show contents" button=0:) Changed line 10 from:
(:toggle menu hide="hide contents" show="show contents" button=1:) to:
(:toggle menu hide="hide contents" show="show contents" button=0:) Changed line 10 from:
(:toggle menu hide="hide menu" show="show menu" button=1:) to:
(:toggle menu hide="hide contents" show="show contents" button=1:) Deleted lines 2-4:
(:toggle menu hide="hide menu" show="show menu" button=1:) Added lines 8-10:
(:toggle menu hide="hide menu" show="show menu" button=1:) Changed line 3 from:
(:toggle hide="hide menu" show="show menu" button=1:) to:
(:toggle menu hide="hide menu" show="show menu" button=1:) Changed line 3 from:
(:toggle hide=hide menu show=show menu menu button=1:) to:
(:toggle hide="hide menu" show="show menu" button=1:) Changed line 3 from:
(:toggle hide menu button=1:) to:
(:toggle hide=hide menu show=show menu menu button=1:) Added line 3:
(:toggle hide box1 button=1:) Deleted line 5:
(:toggle hide box1 button=1:) Deleted lines 631-637:
Deleted lines 528-530:
Added lines 534-672:
Changed line 539 from:
Some more to be typed over are @ http://www.utexas.edu/learn/html/spchar.html & http://www.nobledesktop.com/html-special-characters/ maybe to:
Some more to be typed over are @ http://www.w3schools.com/tags/ref_symbols.asp, http://www.utexas.edu/learn/html/spchar.html & http://www.nobledesktop.com/html-special-characters/ maybe Changed lines 525-530 from:
to:
Added lines 582-589:
Changed line 572 from:
These mods needed a change in AuthPhpbb2SO to check for the ] and generate the alternate format. to:
These mods needed a change in AuthPhpbb2so to check for the ] and generate the alternate format. Changed lines 570-572 from:
where text would have a ] in it. This needed a change in AuthPhpbb2SO to check for the ] and generate the alternate format. to:
where text would have a ] in it. These mods needed a change in AuthPhpbb2SO to check for the ] and generate the alternate format. Changed line 554 from:
Aditional author markup
to:
Additional author markup
Added lines 571-578:
And when your user name has a ] please sign with
instead of
Changed lines 556-569 from:
User names with brackets were not handled properly, so made some alternatives for it.
can be used to sign a message, it will be translated into ??~Author?? instead of [[~Author]] likewise
will do the same and it will add a time stamp to:
User names with brackets were not handled properly, so made and alternative for it. Changed lines 560-571 from:
can be used directly as well, of course. to:
can be used for Author names with a ] in it. Also introduced ??link | text?? as an alternative for [[link | text]] where text would have a ] in it. This needed a change in AuthPhpbb2SO to check for the ] and generate the alternate format. Changed line 168 from:
to:
Changed lines 557-558 from:
to:
Changed lines 561-562 from:
??~Author?? to:
??~Author?? instead of [[~Author]] Changed line 565 from:
to:
Changed lines 555-556 from:
[@%@][@%@][@%@] to:
Changed line 563 from:
[@%@][@%@][@%@][@%@] to:
Changed lines 555-556 from:
??~Blue Hell?? to:
[@%@][@%@][@%@] Changed lines 563-566 from:
??~Blue Hell?? 2013-03-31 18:18 [UTC-7] will do the same and it will add a timestamp to:
[@%@][@%@][@%@][@%@] will do the same and it will add a time stamp Changed line 569 from:
can be used directly as well, of course to:
can be used directly as well, of course. Added lines 550-571:
Aditional author markup
User names with brackets were not handled properly, so made some alternatives for it. ??~Blue Hell?? can be used to sign a message, it will be translated into ??~Author?? likewise ??~Blue Hell?? 2013-03-31 18:18 [UTC-7] will do the same and it will add a timestamp ??~Author?? can be used directly as well, of course Changed lines 542-549 from:
This is the markup you need to place on a new page to create a new Menu. ===Name of New Menu=== (:include Site.MenuXXX:) For instance for the radio menu use to:
This is the markup you need to place on a new page to create a new Radio Menu. Changed lines 498-502 from:
(:pagelist trail=Site.MenuContents fmt=dyntrailmenu:) to get a collapsible menu, see Site.MenuContents? for an example of how to create the menu. to:
(:pagelist trail=Site.MenuRadio fmt=dyntrailmenu:) to get a collapsible menu, see Site.MenuRadio for an example of how to create the menu. Changed lines 534-535 from:
To add, remove, move or rename a page or menu.. it requires a modification on the Site.MenuContents? page. to:
To add, remove, move or rename a page or menu.. it requires a modification on a Site.MenuXXX? page (Site.MenuRadio for instance). Changed lines 544-551 from:
(:include Site.MenuContents:) to:
(:include Site.MenuXXX:) @] For instance for the radio menu use [@ Name of New Menu(:include Site.MenuRadio:) Added lines 532-547:
Radio Menu
To add, remove, move or rename a page or menu.. it requires a modification on the Site.MenuContents? page. This is the format for a new Page or Menu. Add or remove * to adjust the level you want the Page or Menu on. **[[Radio.Temp | Name of New Page or Menu]] This is the markup you need to place on a new page to create a new Menu. ===Name of New Menu=== (:include Site.MenuContents:) Changed line 530 from:
Some more to be typed over are @ http://www.utexas.edu/learn/html/spchar.html to:
Some more to be typed over are @ http://www.utexas.edu/learn/html/spchar.html & http://www.nobledesktop.com/html-special-characters/ maybe Changed line 397 from:
The system can not support timezone specs like [AST] as such specifications are ambiguous (African Standard Time, Asian, Australian?). to:
The system can not support timezone specs like [AST] as such specifications are ambiguous (African Standard Time, Asian, Australian?, summer time?). Changed lines 521-524 from:
to:
Changed lines 521-524 from:
to:
Changed lines 521-527 from:
(:data:)
"code" , "effect"
" to:
Changed lines 521-524 from:
to:
(:data:)
"code" , "effect"
" Changed lines 521-522 from:
to:
Changed line 526 from:
to:
Some more to be typed over are @ http://www.utexas.edu/learn/html/spchar.html Changed line 509 from:
Which is the calendar entry used in the sidebar with a 1 - 2 moth look ahead to:
Which is the calendar entry used in the sidebar with a 1 - 2 month look ahead Changed line 173 from:
to:
Changed lines 519-520 from:
These are not really site specific .. but well .. to:
These are not really site specific .. a list is handy anyway: Changed lines 521-522 from:
to:
Changed lines 520-521 from:
to:
Changed lines 519-526 from:
These are not really site specific .. but well .. ™ %copy; ® to:
These are not really site specific .. but well ..
Added lines 515-519:
Special characters
These are not really site specific .. but well .. ™ %copy; ® Added lines 502-513:
Calendar special markup
In addition to the standard calendar markup there now is (:wikilogsidebar:) Which is the calendar entry used in the sidebar with a 1 - 2 moth look ahead (:wikilogoverview:) Which basically is the same thing with 11-12 months of look ahead Added lines 125-130:
embed a website
For an example see the NM Classic Archive. This works by first making a special page in the JavaScript section, in this case JavaScript.NordModularArchive and then including that page in the page that is to show the embedded site, i.e. that NM Classic Archive article mentioned before. The special page builds an iFrame that is automatically resized depending on the contents of the frame. This special page can only be made by a wiki admin - so if you want something like this please ask an admin for support. Changed lines 209-212 from:
to get in an iframe with the radio live schedule. There are no parameters currently. to:
to get in a table with the radio live schedule. There are no parameters currently. Changed line 218 from:
to get in an iframe with the radio playlist schedule. There are no parameters currently. to:
to get in a table with the radio playlist schedule. There are no parameters currently. Changed line 283 from:
Chat Room, a link to the chat room ... to:
Chat Room, a link to the chat room ... the actual link is set in local/config.php - it might point to a wiki chatroom page later to have all chat information in one place. Added lines 273-283:
Added lines 474-483:
Collapsible menus
In the SideBar you can now enter markup like (:pagelist trail=Site.MenuContents fmt=dyntrailmenu:) to get a collapsible menu, see Site.MenuContents? for an example of how to create the menu. Added line 177:
Deleted lines 14-15:
This page was last modified on 2013-04-14 21:12 [UTC-7]. Changed line 16 from:
This page was last modified on 2013-04-14 21:12 [UTC-7]. to:
This page was last modified on 2013-04-14 21:12 [UTC-7]. Changed line 375 from:
Specifically this will make it possible to use UTC times in the wiki and have to presented to readers in their local time (use a notation like 2013-01-01 00:00 [UTC] to get 2013-01-01 00:00 [UTC]). to:
Specifically this will make it possible to use UTC times in the wiki and have them presented to readers in their local time (use a notation like 2013-01-01 00:00 [UTC] to get 2013-01-01 00:00 [UTC]). Added lines 364-382:
Timestamp specs can now be specified with a time zone offset. The Wiki generated time stamps are in server time which is [UTC-7], but the replacement code will see other offsets from UTC as well. The technical (regular expression) specification is : \d\d\d\d-\d\d-\d\d\s\d\d:\d\d\s\[UTC[+-]?\d{0,2}\] or more informally: dddd-dd-dd dd:dd [UTCspec] where UTC spec is an optional + or - followed by zero to two digits. Which is a standard date and time specified like yyyy-mm-dd hh:mm followed by an UTC offset spec, the spec must start with [UTC then an optional + or - and then zero, one or two digits. For example [UTC] is valid and specifies a zero offset from UTC; [UTC+1] is valid and it specifies central european time. Specifically this will make it possible to use UTC times in the wiki and have to presented to readers in their local time (use a notation like 2013-01-01 00:00 [UTC] to get 2013-01-01 00:00 [UTC]). To prevent automatic translations you can add an extra space between date and time or between time and timezone offset. Note that this rule will also accept [UTC+] or [UTC99] which are not too useful. The system can not support timezone specs like [AST] as such specifications are ambiguous (African Standard Time, Asian, Australian?). Changed line 411 from:
There is some special stuff in this in that thes tables can be used as lookup tables. The column header values can be used to set the class of the table elements in each column. There is some special markup like 'port=Radio.PortData' which causes a translation of the port column values from definitions in Radio.PortData (in this example). to:
There is some special stuff in this in that these tables can be used as data lookup tables. The column header values can be used to set a class for the table elements in each column. There is some special markup like 'port=Radio.PortData' which causes a translation of the port column values from definitions in Radio.PortData (in this example). Changed lines 392-393 from:
I've made a new table markup based on comma separated lists. The notation is like to:
I've made a new table markup based on comma separated (CSV) lists. The notation is like Changed line 411 from:
There is some special stuff in this. The column header values can be used to set the class of the table elements in each column. Also there is some special markup like 'port=Radio.PortData' which tries to translate the port column from definitions in Radio.PortData (in this example). to:
There is some special stuff in this in that thes tables can be used as lookup tables. The column header values can be used to set the class of the table elements in each column. There is some special markup like 'port=Radio.PortData' which causes a translation of the port column values from definitions in Radio.PortData (in this example). Changed lines 411-412 from:
There is some special stuff in this, the column header values will be used to set the class of the table elements in each column. Also there is a special word 'port' which tries to translate radio port numbers when it is used in a header. like : to:
There is some special stuff in this. The column header values can be used to set the class of the table elements in each column. Also there is some special markup like 'port=Radio.PortData' which tries to translate the port column from definitions in Radio.PortData (in this example). Like : Changed line 416 from:
"the" , "port=Radio.PortList" to:
"the" , "port=Radio.PortData" Changed lines 424-425 from:
"the" , "port=Radio.PortList" "and" , "8052" to:
"the" , "port=Radio.PortData" "and" , "p8052" Changed line 427 from:
"thing", "8056" to:
"thing", "p8056" Changed lines 435-436 from:
"the" , "port=Radio.PortList" "and" , "8052" to:
"the" , "port=Radio.PortData" "and" , "p8052" Changed line 439 from:
"thing", "8056" to:
"thing", "p8056" Changed lines 446-450 from:
"the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; to:
"the" , "port=Radio.PortData" "and" , "p8052" "for" , "public_1" "thing", "p8056" Changed lines 395-398 from:
"the", "headers"; "and", "data"; "for", "the"; "thing", "."; to:
"the", "headers" "and", "data" "for", "the" "thing", "." Changed lines 405-408 from:
"the", "headers"; "and", "data"; "for", "the"; "thing", "."; to:
"the", "headers" "and", "data" "for", "the" "thing", "." Changed lines 414-417 from:
"the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; to:
"the" , "port=Radio.PortList" "and" , "p8052" "for" , "public_1" "thing", "8056" Changed lines 424-427 from:
"the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; to:
"the" , "port=Radio.PortList" "and" , "8052" "for" , "public_1" "thing", "8056" Changed lines 435-439 from:
"the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; to:
"the" , "port=Radio.PortList" "and" , "8052" "for" , "public_1" "thing", "8056" Changed line 273 from:
This needs JavaScript to be enabled on the reader's computer. to:
This needs JavaScript to be enabled on the reader's computer. If you want to change the looks .. it looks like you'll have to change JavaScript.StreamInfo (you need be a WikiAdmin for that). Added lines 259-271:
This needs JavaScript to be enabled on the reader's computer. Now on the radio
use {_now_playing_} to get waiting for song title ...Changed line 300 from:
jQuery JavaScript Library v1.9.1 is available already as http://electro-music.com/wiki/pub/jquery-1.9.1.js for the uncompressed (debug) version and http://electro-music.com/wiki/pub/jquery-1.9.1.min.js for the compressed (production) version. Not sure how well this combines with the GMT / local clock, we'll see. to:
jQuery JavaScript Library v1.9.1 is available already as http://electro-music.com/wiki/pub/jquery-1.9.1.js for the uncompressed (debug) version and http://electro-music.com/wiki/pub/jquery-1.9.1.min.js for the compressed (production) version. Not sure how well this combines with the GMT / local clock, we'll see. Cooperation between various JavaScript includes seems to be working ok now. Added lines 418-439:
Oh, and it will do row separators too: (:data:) "the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; (:dataend:) makes: (:data:) "the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; (:dataend:) Changed line 163 from:
to:
Changed lines 398-408 from:
There is some special stuff in this, the column header values will be used to set the class of the table elements in each column. Also there is a special word 'port' which tries to translate radio port numbers when it is used in a header. to:
There is some special stuff in this, the column header values will be used to set the class of the table elements in each column. Also there is a special word 'port' which tries to translate radio port numbers when it is used in a header. like : (:data:) "the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; (:dataend:) makes: Changed lines 401-404 from:
"the", "port"; "and", "8050"; "for", "8130"; "thing", "."; to:
"the" , "port" ; "and" , "8052" ; "for" , "public_1"; "thing", "8056" ; Added lines 398-405:
There is some special stuff in this, the column header values will be used to set the class of the table elements in each column. Also there is a special word 'port' which tries to translate radio port numbers when it is used in a header. (:data:) "the", "port"; "and", "8050"; "for", "8130"; "thing", "."; (:dataend:) Changed lines 381-383 from:
[= (:data:) to:
(:data:) Deleted line 382:
Deleted line 383:
Deleted line 384:
Changed lines 386-388 from:
(:dataend:) ]to:
(:dataend:) Added line 383:
Added line 385:
Added line 387:
Added line 389:
Added line 391:
Added lines 382-391:
(:data:) "the", "headers"; "and", "data"; "for", "the"; "thing", "."; (:dataend:) ]it then makes : Changed lines 393-396 from:
"the", "headers"; "and", "data"; "for", "the"; "thing", "."; to:
"the", "headers"; "and", "data"; "for", "the"; "thing", "."; Changed lines 398-400 from:
]to:
Added lines 375-388:
Easier tables
I've made a new table markup based on comma separated lists. The notation is like (:data:) "the", "headers"; "and", "data"; "for", "the"; "thing", "."; (:dataend:) Added line 178:
Changed lines 360-372 from:
The complete set of defined smileys is
to:
The complete set of defined smileys is: :-) ;-) :-( :p :o :D {cool} {confused} {eek} {angry} {rolleyes} Changed lines 360-363 from:
The complete set of defined smileys is:
to:
The complete set of defined smileys is Changed lines 364-369 from:
to:
Changed lines 363-369 from:
to:
Added lines 355-374:
Smileys
The complete set of defined smileys is:
Changed line 331 from:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. to:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, you can find examples through the Stub List. Changed lines 331-337 from:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe after all There now is a {_stubs_} macro as well, it points to the Stub List without opening a new browser window. to:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. There is a {_stubs_} macro as well, it points to the Stub List without opening a new browser window. Changed lines 283-284 from:
(:html:) to:
(:html:) Changed lines 287-288 from:
(:htmlend:) to:
(:htmlend:) Changed lines 293-297 from:
{script: common.js} The library will have to be uploaded to the server before being able to do this - only admins can perform the upload. This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. to:
{script: common.js} The library will have to be uploaded to the server before being able to do this - only admins can perform the upload. This way the Wiki software will keep track of the included files and will include them only once. This one just supports multiple "onPageLoad" callbacks to be present in a page and some helper stuff for date and time translations, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Changed line 175 from:
to:
Changed lines 291-293 from:
{script: common.js} - the library will have to be uploaded to the server before being able to do this - only admins can perform the upload. to:
{script: common.js} The library will have to be uploaded to the server before being able to do this - only admins can perform the upload. Changed line 291 from:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'></script>. to:
{script: common.js} - the library will have to be uploaded to the server before being able to do this - only admins can perform the upload. Changed line 333 from:
Blue Hell 2013-03-01 18:58 [UTC-7] There is a {_stubs_} macro too now which points to the Stub List (without opening a new browser window) to:
There now is a {_stubs_} macro as well, it points to the Stub List without opening a new browser window. Added lines 332-333:
Blue Hell 2013-03-01 18:58 [UTC-7] There is a {_stubs_} macro too now which points to the Stub List (without opening a new browser window) Added lines 351-354:
Page views
Use {_page_views_} to get a list of page views for the whole site, see Site.PageViews for an example. Changed line 349 from:
When a user has JavaScript enabled all time stamps should be in user local time, when JavaScript is not enabled they are in server time. This was made to work on Blue Hell's versions of FF, IE, Chrome and Safari. to:
When a user has JavaScript enabled all time stamps should be in user local time, when JavaScript is not enabled they are in server time. This was made to work on Blue Hell's versions of FF, IE, Chrome and Safari. This works by changing all server supplied time stamps on the client side with some JavaScript, for pages with many timestamps this may take some time. Changed line 337 from:
Simple image gallery - done
to:
Simple image gallery
Added lines 345-349:
Time stamps
When a user has JavaScript enabled all time stamps should be in user local time, when JavaScript is not enabled they are in server time. This was made to work on Blue Hell's versions of FF, IE, Chrome and Safari. Changed line 42 from:
This currently does not work properly for user names having brackets in them, the underlying [[~user name]] markup breaks on that. to:
This currently does not work properly for user names having brackets in them, the underlying [[~user name]] markup breaks on that (this is an item in the Todo list already). Changed lines 22-31 from:
Anyways here is the howto: erm .. real soon now ... ah I see ... ah, there it is! hmm .. use that table at the right for a better swim. to:
Changed line 352 from:
To get a working layout you probably will want to place the uploaded images into a different page than the one you but the Mini:* in, otherwise the Attachments will show outside the gallery as well. For Site.Icons this was not needed. to:
To get a good looking layout you probably will want to place the uploaded images into a different page than the one you put the Mini:* in, otherwise the Attachments will show outside the gallery as well. For Site.Icons this was not needed. Added lines 351-352:
To get a working layout you probably will want to place the uploaded images into a different page than the one you but the Mini:* in, otherwise the Attachments will show outside the gallery as well. For Site.Icons this was not needed. Changed line 338 from:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe this is a to:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe Changed lines 338-342 from:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe this is a This article is a Stub, you can help this Wiki grow by expanding on it. after all ... to:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe this is a after all Added line 188:
Added lines 338-346:
Simple image gallery - done
I mainly needed this to get an overview of the images in Site.Icons, but it may be useful elsewhere too. Help about this can be found at http://www.pmwiki.org/wiki/Cookbook/Mini. In it's most basic form just use Mini:* to get a thumbnail view of all image attachments present on the page - when the images should not be downloadable apparently mini:* (lowercase M) can be used; I did not test this, and it may need some other changes too. When you change thumbnail settings the cached thumbnails need be purged with an action like PageName?action=purgethumbs. Changed line 337 from:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. to:
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Oh well .. maybe this is a This article is a Stub, you can help this Wiki grow by expanding on it. after all ... Added lines 334-337:
stubs - done
Something along these lines ... added {_stub_} markup ... I will not add that as an example here as I do not see this page as a stub, but there is an example in Main.Chatter. Added lines 324-327:
or with the large icon Attach:Site.Icons/feed-icon-28x28.png [[Help.SiteSpecificMarkup?action=rss | RSS]] Changed lines 330-334 from:
to:
Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the Category / DIY page for instance (which has automatically generated contents and an RSS feed on those contents). to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the Category / DIY page for instance (which has automatically generated contents and an RSS feed on those contents). Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the Subject page for instance (which has automatically generated contents and an RSS feed on those contents). to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the Category / DIY page for instance (which has automatically generated contents and an RSS feed on those contents). Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the {Category.DIY} Subject page for instance (which has automatically generated contents and an RSS feed on those contents). to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the Subject page for instance (which has automatically generated contents and an RSS feed on those contents). Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the {Category.DIY} page for instance (which has automatically generated contents and an RSS feed on those contents). to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the {Category.DIY} Subject page for instance (which has automatically generated contents and an RSS feed on those contents). Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see for instance. to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see the {Category.DIY} page for instance (which has automatically generated contents and an RSS feed on those contents). Changed line 332 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see DIY for instance. to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see for instance. Changed lines 332-334 from:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds and RSS links work on Category pages too, see DIY for instance. Changed line 320 from:
or when you want to specify some details to:
or when you want to specify some details 8 Added lines 318-321:
{_rss_} or when you want to specify some details Added lines 325-328:
or Changed lines 324-328 from:
Not that RSS is too useful for this specific page, but an example see Articles, which uses an unnumbered list. Wiki trails can also be used, for help on this see PmWiki.WebFeeds to:
Not that RSS is too useful for this specific page, but for an example see Articles, which uses an unnumbered list. Wiki trails can also be used as an RSS source, for help on this see PmWiki.WebFeeds Changed lines 320-324 from:
which the looks like : RSS to:
which then looks like Not that RSS is too useful for this specific page, but an example see Articles, which uses an unnumbered list. Wiki trails can also be used, for help on this see PmWiki.WebFeeds Changed lines 316-319 from:
can be used to indicate an RSS feed
to:
can be used to indicate an RSS feed. RSS feeds can be made for every page by making an action=rss link for it. To get an RSS feed on this page use markup like
Attach:Site.Icons/feed-icon-14x14.png [[Help.SiteSpecificMarkup?action=rss | RSS]] Changed line 10 from:
Howtos, keep that body moving, or freeze, a dream of productivity, sollified illusions. to:
Howtos, keep that body moving, or freeze, a dream of productivity, frozen illusions. Changed line 18 from:
For bug reports or security issues please use the Discuss link (top right), for feature requests please use Help.Todo, feel free to add items, either in the talk page here or there. to:
Changed line 10 from:
Howtos, keep that body moving, or freeze, a dream of productivity. to:
Howtos, keep that body moving, or freeze, a dream of productivity, sollified illusions. Changed line 31 from:
hmm .. use that table at the right! to:
hmm .. use that table at the right for a better swim. Changed lines 31-33 from:
. :-) to:
hmm .. use that table at the right! Changed line 10 from:
Howtos, keep that body moving, or freeze to:
Howtos, keep that body moving, or freeze, a dream of productivity. Added lines 21-27:
erm .. real soon now ... ah I see ... ah, there it is! Changed line 12 from:
Also keep an eye on The dreams, the info is spread a bit over two places. to:
Also keep an eye on The Dreams, the info is spread a bit over two places. Changed line 12 from:
Also keep an eye on Help.Todo } The dreams?, the info is spread a bit over two places. to:
Also keep an eye on The dreams, the info is spread a bit over two places. Changed line 12 from:
Also have a look at Help.Todo, the info is spread a bit over two places. to:
Also keep an eye on Help.Todo } The dreams?, the info is spread a bit over two places. Changed line 16 from:
The idea is to mostly have a manual for working stuff here and a manual there as good as it goes ... to:
The idea is to mostly have a manual for working stuff here and a wish list there as good as it goes ... Changed lines 14-18 from:
For bug reports or security issues please use the Discuss link (top right), for feature requests please use Help.Todo, feel free to add items there. to:
For bug reports or security issues please use the Discuss link (top right), for feature requests please use Help.Todo, feel free to add items, either in the talk page here or there. The idea is to mostly have a manual for working stuff here and a manual there as good as it goes ... Anyways here is the howto: Changed line 14 from:
to:
Added lines 13-15:
Deleted lines 18-19:
Added lines 16-18:
Changed lines 135-137 from:
So, for instance, to make a bit of text electro_blue you can use %class=electro_blue%a bit of text electro_blue%% to:
So, for instance, to make a bit of text electro_hover you can use %class=electro_hover%a bit of text electro_hover%% Changed lines 266-267 from:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right (oh how nicely it floats there ...). This, of course, needs javaScript to be enabled on the client computer. to:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right (oh how nicely it floats there ...). This, of course, needs javaScript to be enabled on the client computer. Anyway ... you can draw and you can animate Changed line 282 from:
This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Anyway ... you can draw and you can animate to:
This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Changed line 282 from:
This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. to:
This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Anyway ... you can draw and you can animate Added line 166:
Changed line 263 from:
Please note that it is still possible for admin leveled users to write HTML and JavaScript into almost every wiki page, it is just that as soon a less privileged user will edit and save such a page the code will be broken (it is easy to fix, but still). to:
Please note that it is still possible for admin leveled users to write HTML and JavaScript into almost every wiki page, it is just that as soon as a less privileged user will edit and save such a page the code will be broken (it is easy to fix, but still). Changed line 255 from:
When regular users will enter HTML markup it will be broken into something innocent on save. So this leaves the problem that when there is direct HTML markup on a user editable page the page will get broken after an edit. To avoid this I made a new group called JavaScript which is world readable but editable by WikiAdmins and forum admins only. To get the contents on a user editable page the wiki include mechanism can be used: to:
When regular users will enter HTML markup it will be broken into something innocent on save. So this leaves the problem that when there is direct HTML markup on a user editable page the page will get broken after an edit. To avoid this problem I made a new group called JavaScript which is world readable but editable by WikiAdmins and forum admins only. To get the contents on a user editable page the wiki include mechanism can be used: Changed line 263 from:
Please note that is still possible for admin leveled users to put HTML and JavaScript inyo almost every wiki page, it is just that as soon a less privileged user will edit and save such a page the code will be broken. to:
Please note that it is still possible for admin leveled users to write HTML and JavaScript into almost every wiki page, it is just that as soon a less privileged user will edit and save such a page the code will be broken (it is easy to fix, but still). Added lines 262-263:
Please note that is still possible for admin leveled users to put HTML and JavaScript inyo almost every wiki page, it is just that as soon a less privileged user will edit and save such a page the code will be broken. Changed line 261 from:
The group name JavaScript may be confusing, as it will allow for HTML to be used directly in a wiki page ... however the primary reason for this was to allow for user defined JavaScript to present in wiki pages. to:
The group name JavaScript may be confusing, as it will allow for HTML to be used directly in a wiki page ... however the primary reason for this was to allow for user defined JavaScript to be present in wiki pages. Changed line 279 from:
This one just supports multiple onPageLoad things to be present in a page, probably something more elaborate will be needed later on. When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. to:
This one just supports multiple "onPageLoad" callbacks to be present in a page, something more elaborate will be needed later on (see next pargraph). When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Changed line 261 from:
The name JavaScript may be confusing, but it will allow for HTML (which includes JavaScript) to be used directly in a wiki page. to:
The group name JavaScript may be confusing, as it will allow for HTML to be used directly in a wiki page ... however the primary reason for this was to allow for user defined JavaScript to present in wiki pages. Added lines 280-281:
jQuery JavaScript Library v1.9.1 is available already as http://electro-music.com/wiki/pub/jquery-1.9.1.js for the uncompressed (debug) version and http://electro-music.com/wiki/pub/jquery-1.9.1.min.js for the compressed (production) version. Not sure how well this combines with the GMT / local clock, we'll see. Changed line 277 from:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'>no script text</script>. to:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'></script>. Changed lines 261-263 from:
The name JavaScript may be confusing, but it will allow for HTML (which includes JavaScript) to be used directly in a wiki page. I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right (oh how nicely it floats there ...). to:
The name JavaScript may be confusing, but it will allow for HTML (which includes JavaScript) to be used directly in a wiki page. I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right (oh how nicely it floats there ...). This, of course, needs javaScript to be enabled on the client computer. Changed line 273 from:
and in between goes arbitrary HTML code including <script> elements. to:
and in between goes arbitrary HTML code including <script> elements; edit the test page to see an example. Changed lines 265-268 from:
One starts a HTML code section with (:html:) and ends it with (:htmlend:) - in between goes arbitrary HTML code including <script> elements. Some help on canvas stuff can be found here to:
One starts a HTML code section with (:html:) and ends it with (:htmlend:) and in between goes arbitrary HTML code including <script> elements. Added lines 280-283:
Some help on canvas stuff can be found here Changed lines 269-271 from:
When a JavaScript code library is needed it can be included with code like <script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'>no script text</script>. This one just supports multiple onPageLoad things to be present in a page, probably something more elaborate will be needed later on. When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. to:
When a JavaScript code library is needed it can be included with code like <script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'>no script text</script>. This one just supports multiple onPageLoad things to be present in a page, probably something more elaborate will be needed later on. When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Changed lines 269-272 from:
When a JavaScript code library is needed it can be included with code like <script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'> </script> to:
When a JavaScript code library is needed it can be included with code like <script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'>no script text</script>. This one just supports multiple onPageLoad things to be present in a page, probably something more elaborate will be needed later on. Changed line 263 from:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right. to:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right (oh how nicely it floats there ...). Changed line 261 from:
The name JavaScript may be confusing, but it will allow for direct HTML which includes JavaScript. to:
The name JavaScript may be confusing, but it will allow for HTML (which includes JavaScript) to be used directly in a wiki page. Changed line 274 from:
When you need code to be uploaded to the server please ask Blue Hell to:
When you need code to be uploaded to the server please ask Blue Hell - it is preferred to not link to external scripts, but to have them uploaded to the server rather. Added lines 259-260:
(:include JavaScript.TestPage:) Changed lines 263-265 from:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get: (:include JavaScript.TestPage:) to:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get the image on the right. Added lines 273-274:
When you need code to be uploaded to the server please ask Blue Hell Changed lines 271-276 from:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js' ></script> to:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js'> </script> Changed lines 272-275 from:
<script type='text/javascript' src='http://electro-music.com/wiki/pub/common.js'></script> to:
<script type = 'text/javascript' src = 'http://electro-music.com/wiki/pub/common.js' ></script> Added lines 268-273:
When a JavaScript code library is needed it can be included with code like <script type='text/javascript' src='http://electro-music.com/wiki/pub/common.js'></script> Changed line 251 from:
Include HTML and JavaScript
to:
Include HTML and JavaScript
Added line 165:
Added lines 263-264:
One starts a HTML code section with (:html:) and ends it with (:htmlend:) - in between goes arbitrary HTML code including <script> elements. Changed lines 260-262 from:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get: (:include JavaScript.TestPage:) to:
I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get: (:include JavaScript.TestPage:) Changed line 254 from:
When regular users will enter HTML markup it will be broken into something innocent on save. So this leaves the problem that when there is direct HTML markup on a user editable page the page will get broken after an edit. To avoid such problens I made a new group called JavaScript which is world readable but editable by WikiAdmins and forum admins only. To get the contents on a user editable page the wiki include mechanism can be used: to:
When regular users will enter HTML markup it will be broken into something innocent on save. So this leaves the problem that when there is direct HTML markup on a user editable page the page will get broken after an edit. To avoid this I made a new group called JavaScript which is world readable but editable by WikiAdmins and forum admins only. To get the contents on a user editable page the wiki include mechanism can be used: Added lines 247-260:
Include HTML and JavaScript
HTML and JavaScript are restricted to be used by WikiAdmins and forum admins only. When regular users will enter HTML markup it will be broken into something innocent on save. So this leaves the problem that when there is direct HTML markup on a user editable page the page will get broken after an edit. To avoid such problens I made a new group called JavaScript which is world readable but editable by WikiAdmins and forum admins only. To get the contents on a user editable page the wiki include mechanism can be used: (:include JavaScript.SomePageWithHtml:) The name JavaScript may be confusing, but it will allow for direct HTML which includes JavaScript. I made an example page JavaScript.TestPage that has a canvas element with some basic drawing on it. This page can be included in other pages with (:include JavaScript:TestPage:) to get: (:include JavaScript.TestPage:) Added lines 9-10:
Also have a look at Help.Todo, the info is spread a bit over two places. Added lines 243-244:
This needs JavaScript to be enabled on the reader's computer. Added line 191:
Added line 193:
Added lines 196-197:
Added line 200:
Added line 202:
Added lines 205-206:
Added line 209:
Added line 211:
Added lines 214-215:
Added line 218:
Added line 220:
Added lines 223-224:
Added line 227:
Added line 229:
Added lines 232-233:
Added line 235:
Added line 237:
Added line 239:
Changed lines 189-203 from:
Radio live schedule
use {_live_schedule_} to get in an iframe with the radio live schedule. There are no parameters currently. Radio playlist schedule
use {_playlist_schedule_} to get in an iframe with the radio playlist schedule. There are no parameters currently. Paypal donation form
use {_donate_} to get in the paypal donation form. User group list
use{_group_list_} to get a comma separated list of groups the user is a member of User group info
use {_user_info_} to type some user info to:
radio live schedule
use {_live_schedule_} to get in an iframe with the radio live schedule. There are no parameters currently. radio playlist schedule
use {_playlist_schedule_} to get in an iframe with the radio playlist schedule. There are no parameters currently. paypal donation form
use {_donate_} to get in the paypal donation form. user group list
use {_group_list_} to get a comma separated list of groups the user is a member of user group info
use {_user_info_} to type some user info Changed lines 215-217 from:
use {_clock_} to display . | . to:
use {_clock_} to display . | . Changed lines 189-194 from:
to:
Radio live schedule
use {_live_schedule_} to get in an iframe with the radio live schedule. There are no parameters currently. Radio playlist schedule
use {_playlist_schedule_} to get in an iframe with the radio playlist schedule. There are no parameters currently. Paypal donation form
use {_donate_} to get in the paypal donation form. User group list
use{_group_list_} to get a comma separated list of groups the user is a member of User group info
use {_user_info_} to type some user info GMT-local time clock
use {_clock_} to display . | . Changed lines 192-193 from:
to:
Changed line 2 from:
Contents
to:
Contents
Changed lines 14-15 from:
Creole
to:
Creole
Changed lines 20-21 from:
Talk pages
to:
Talk pages
Changed lines 31-32 from:
Embedding
to:
Embedding
Changed lines 36-37 from:
icons
to:
icons
Changed lines 50-51 from:
embed forum music
to:
embed forum music
Changed lines 73-74 from:
embed non forum (uploaded) audio
to:
embed non forum (uploaded) audio
Changed lines 109-110 from:
embed video
to:
embed video
Changed lines 117-118 from:
forum colors
to:
forum colors
Changed lines 144-145 from:
Extensions
to:
Extensions
Changed lines 170-171 from:
to break rfloat and lfloat thingies
to:
to break rfloat and lfloat thingies
Changed lines 178-179 from:
use a random page
to:
use a random page
Changed line 187 from:
some special stuff
to:
some special stuff
Changed lines 40-44 from:
To include a site wide icon use markup like Attach:Site.Icons/download.gif to get to:
To include a site wide icon use markup like Attach:Site.Icons/download.gif to get Changed lines 38-40 from:
site wide icons are to be found in Site.Icons to include a site wide icon use markup like Attach:Site.Icons/download.gif to get to:
Site wide icons are to be found in Site.Icons To include a site wide icon use markup like Attach:Site.Icons/download.gif to get Deleted lines 82-83:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% Changed line 28 from:
This currently does not work properly for user names having brackets in them. to:
This currently does not work properly for user names having brackets in them, the underlying [[~user name]] markup breaks on that. Added line 28:
This currently does not work properly for user names having brackets in them. Changed line 53 from:
{track: 33479 | Muied Lumens - music for walkmen} to:
{track: 33479 | Muied Lumens - music for walkmen} Deleted lines 140-155:
to break rfloat and lfloat thingies
use [[<<]] or <br>
use a random page
look here, the config stuff needed is in place. Note that the Random Page link in the sidebar works differently (see here).
Added lines 165-180:
to break rfloat and lfloat thingies
use [[<<]] or <br>
use a random page
look here, the config stuff needed is in place. Note that the Random Page link in the sidebar works differently (see here).
Changed lines 1-5 from:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. This page was last modified on 2013-04-14 21:12 [UTC-7]. to:
Added lines 7-13:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. This page was last modified on 2013-04-14 21:12 [UTC-7].
Small text Changed lines 129-131 from:
So, for instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% to:
So, for instance, to make a bit of text electro_blue you can use %class=electro_blue%a bit of text electro_blue%% Changed lines 115-116 from:
forum color example to:
forum color example The following CSS styles have been added to the main style sheet: Changed line 128 from:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use to:
So, for instance, to make a bit of text electro_blue you can use Changed lines 115-116 from:
forum color example to:
forum color example Changed lines 29-30 from:
icons
to:
Embedding
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% icons
Changed lines 42-47 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% Embedding
to:
Changed lines 5-6 from:
Creole cheat sheet to:
Added line 12:
Creole cheat sheet Changed line 146 from:
look here, the config stuff needed is in place. Note that the *Random Page* link in the sidebar works differently (see here). to:
look here, the config stuff needed is in place. Note that the Random Page link in the sidebar works differently (see here). Changed lines 3-4 from:
This page was last modified on 2013-04-14 21:12 [UTC-7].
to:
This page was last modified on 2013-04-14 21:12 [UTC-7]. Changed lines 14-17 from:
The Creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right.
to:
The Creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right. Changed lines 20-27 from:
Every wiki page has an associated talk page which is meant to discuss the actual page. You can reach the talk page by using the Discuss link from the page menu in the top right corner of each page.
Talk pages can be edited by registered and logged-in forum members only. To make a link to a talk page just append -Talk to the page name. For instance use [[Help.SiteSpecificMarkup-Talk | this]] to get this.
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row (
~ ~ ~ ) which will be expanded to your forum user name when the page is saved. To get a timestamped sign you can use four tildes instead (~ ~ ~ ~ ).
to:
Every wiki page has an associated talk page which is meant to discuss the actual page. You can reach the talk page by using the Discuss link from the page menu in the top right corner of each page. Talk pages can be edited by registered and logged-in forum members only. To make a link to a talk page just append -Talk to the page name. For instance use [[Help.SiteSpecificMarkup-Talk | this]] to get this. It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row ( Changed lines 30-40 from:
site wide icons are to be found in Site.Icons
to include a site wide icon use markup like Attach:Site.Icons/download.gif to get
Please upload icon like images to be used on many pages to Site.Icons
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
to:
site wide icons are to be found in Site.Icons to include a site wide icon use markup like Attach:Site.Icons/download.gif to get Please upload icon like images to be used on many pages to Site.Icons Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% Changed lines 45-65 from:
Use {track: xxxxx | track title} to link to music posted on the forums, xxxxx being the track ID.
For example the forum track http://electro-music.com/forum/download.php?id=33479 (from this page) has track ID 33479 and is called Muied Lumens - music for walkmen.
To get a listen and download link for this track use the markup
{track: 33479 | Muied Lumens - music for walkmen}
which results in
https://electro-music.com/wiki/uploads/Site/Icons/listen.gif https://electro-music.com/wiki/uploads/Site/Icons/download.gif %class=track_item%Muied Lumens - music for walkmen%%
Where the first icon is a direct listen and the second a download - the direct listen seems to not work in chrome.
You can look up track IDs in the forum's media page by hovering your mouse over the track title or the speaker symbol in front of it.
By using links this way the listen counts on the forum will be maintained.
to:
Use {track: xxxxx | track title} to link to music posted on the forums, xxxxx being the track ID. For example the forum track http://electro-music.com/forum/download.php?id=33479 (from this page) has track ID 33479 and is called Muied Lumens - music for walkmen. To get a listen and download link for this track use the markup {track: 33479 | Muied Lumens - music for walkmen} which results in https://electro-music.com/wiki/uploads/Site/Icons/listen.gif https://electro-music.com/wiki/uploads/Site/Icons/download.gif %class=track_item%Muied Lumens - music for walkmen%% Where the first icon is a direct listen and the second a download - the direct listen seems to not work in chrome. You can look up track IDs in the forum's media page by hovering your mouse over the track title or the speaker symbol in front of it. By using links this way the listen counts on the forum will be maintained. Changed lines 68-103 from:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags
(:audio myaudio.mp3:) or
(:audio myaudio.ogg:)
(where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Wav files should work too btw ... but they are getting large quickly ...
You can also not specify a file extension in the the argument, like
(:audio myaudio:)
and then upload both an mp3 and an ogg file, the user's browser will then select what it likes best.
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
For extra options have a look at http://www.pmwiki.org/wiki/Cookbook/Audio5 , please do not use auto starting audio.
the following setup is in confg.php:
$AudioPreload = 'auto'; // (auto|metadata|none)
$AudioAutoplay = 0;
$AudioControls = 1;
$AudioLoop = 0;
Audio uploaded to the wiki is not shared with the forum.
An example:
(:audio test07.ogg:) - Blue Hell - test07
gives: (:audio test07.ogg:) - Blue Hell - test07
to:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags (:audio myaudio.mp3:) or (:audio myaudio.ogg:) (where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Wav files should work too btw ... but they are getting large quickly ... You can also not specify a file extension in the the argument, like (:audio myaudio:) and then upload both an mp3 and an ogg file, the user's browser will then select what it likes best. Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% For extra options have a look at http://www.pmwiki.org/wiki/Cookbook/Audio5 , please do not use auto starting audio. the following setup is in confg.php: $AudioPreload = 'auto'; // (auto|metadata|none) $AudioAutoplay = 0; $AudioControls = 1; $AudioLoop = 0; Audio uploaded to the wiki is not shared with the forum. An example: (:audio test07.ogg:) - Blue Hell - test07 gives: (:audio test07.ogg:) - Blue Hell - test07 Changed lines 106-111 from:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. For an example see http://electro-music.com/wiki/pmwiki.php?n=Articles.FeedbackOrNoInputMixing - scroll down a bit.
to:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. For an example see http://electro-music.com/wiki/pmwiki.php?n=Articles.FeedbackOrNoInputMixing - scroll down a bit. Changed line 114 from:
to:
Changed lines 116-131 from:
forum color example
* electro_blue is #255293 or rgb( 37, 82, 147) dark blue site color
* electro_back is #ffffff or rgb( 255, 255, 255) white
* electro_light is #efefef or rgb( 239, 239, 239) lightest table cell color
* electro_mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells
* electro_dark is #d2d6df or rgb( 210, 214, 223) the darker table cell color
* electro_hover is #eb6f6f or rgb( 204, 111, 111) sort of red, link hover color
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use
%class=electro_blue%electro_blue%%
for the markup.
to:
forum color example * electro_blue is #255293 or rgb( 37, 82, 147) dark blue site color * electro_back is #ffffff or rgb( 255, 255, 255) white * electro_light is #efefef or rgb( 239, 239, 239) lightest table cell color * electro_mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells * electro_dark is #d2d6df or rgb( 210, 214, 223) the darker table cell color * electro_hover is #eb6f6f or rgb( 204, 111, 111) sort of red, link hover color These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% for the markup. Changed lines 138-139 from:
use [[<<]] or <br>
to:
use [[<<]] or <br> Changed line 146 from:
look here, the config stuff needed is in place. Note that the *Random Page* link in the sidebar works differently (see here).
to:
look here, the config stuff needed is in place. Note that the *Random Page* link in the sidebar works differently (see here). Added lines 3-4:
This page was last modified on 2013-04-14 21:12 [UTC-7].
Changed lines 7-8 from:
This page was last modified on 2013-04-14 21:12 [UTC-7].
to:
Deleted lines 9-11:
Changed lines 40-43 from:
Embedding
embed forum music
to:
Embedding
embed forum music
Changed lines 65-66 from:
embed non forum (uploaded) audio
to:
embed non forum (uploaded) audio
Changed line 103 from:
embed video
to:
embed video
Deleted lines 6-7:
Added lines 9-10:
Changed lines 15-16 from:
to:
Changed lines 25-26 from:
to:
Changed lines 37-38 from:
to:
Embedding
Changed lines 62-63 from:
to:
Changed lines 100-101 from:
to:
Changed lines 107-108 from:
to:
Changed lines 133-134 from:
to:
Changed lines 141-142 from:
to:
Changed lines 149-150 from:
to:
Changed lines 176-177 from:
to:
Changed line 184 from:
to:
Added line 8:
Changed lines 11-12 from:
Creole:
to:
Creole
Changed lines 17-18 from:
-Talk pages:
to:
-Talk pages
Changed lines 27-28 from:
icons:
to:
icons
Changed lines 39-40 from:
embed forum music:
to:
embed forum music
Changed lines 61-62 from:
embed non forum (uploaded) audio:
to:
embed non forum (uploaded) audio
Changed lines 98-99 from:
embed video:
to:
embed video
Changed lines 104-105 from:
forum colors:
to:
forum colors
Changed lines 136-137 from:
to include a random page:
to:
use a random page
Changed lines 144-146 from:
The following extensions were installed 10 :
to:
Added line 157:
Changed line 156 from:
to:
Changed line 156 from:
to:
Added line 156:
Changed line 10 from:
The Creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right. to:
The Creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right.
Changed lines 6-7 from:
creole cheat sheet to:
Creole cheat sheet Changed line 10 from:
The creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right. to:
The Creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right. Changed lines 8-10 from:
The creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet. to:
Creole:
The creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet on the right. Added lines 4-8:
The creole markup extensions have been switched on, this allows for some easier markup in places. See the cheat sheet. Changed line 138 from:
to:
Changed line 134 from:
The following extensions were installed 14 :
to:
The following extensions were installed 15 :
Deleted lines 28-35:
use:
Added lines 154-161:
use:
Changed line 13 from:
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row ( to:
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row (
~ ~ ~ ) which will be expanded to your forum user name when the page is saved. To get a timestamped sign you can use four tildes instead (~ ~ ~ ~ ).
Changed line 13 from:
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row [[~Blue Hell]] which will be expanded to your forum user name when the page is saved. To get a timestamped sign you can use four tildes instead [[~Blue Hell]] 2013-02-17 05:44 [UTC-7]. to:
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row ( Added lines 12-13:
It is considered to be polite to sign your messages on a Talk page. To sign a message you can just use three tildes in row [[~Blue Hell]] which will be expanded to your forum user name when the page is saved. To get a timestamped sign you can use four tildes instead [[~Blue Hell]] 2013-02-17 05:44 [UTC-7]. Added lines 10-11:
Talk pages can be edited by registered and logged-in forum members only. To make a link to a talk page just append -Talk to the page name. For instance use [[Help.SiteSpecificMarkup-Talk | this]] to get this.
Added lines 4-9:
-Talk pages:
Every wiki page has an associated talk page which is meant to discuss the actual page. You can reach the talk page by using the Discuss link from the page menu in the top right corner of each page.
Changed line 126 from:
to:
look here, the config stuff needed is in place. Note that the *Random Page* link in the sidebar works differently (see here).
Changed line 126 from:
look here, the config stuff needed is in place.
to:
Changed line 146 from:
to:
Changed line 146 from:
to:
Added line 146:
Added line 145:
Changed line 1 from:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. blah to:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. Changed lines 1-2 from:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. to:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. blah Changed line 6 from:
blah to:
Added lines 5-6:
Added lines 17-18:
Added lines 27-28:
Added lines 47-48:
Added lines 84-85:
Added lines 90-91:
Added lines 114-115:
Deleted line 119:
Added lines 122-123:
Deleted line 127:
Added lines 130-131:
Added line 151:
Changed line 1 from:
Keep an eye on this page for all the site specifics that are not in the genral PmWiki help pages. to:
Keep an eye on this page for all the site specifics that are not in the general PmWiki help pages. Added line 99:
Added line 106:
Changed line 108 from:
to:
Added lines 114-115:
Added line 131:
Changed line 109 from:
look here, the config stuff needed is in place. to:
look here, the config stuff needed is in place.
Added lines 107-110:
to include a random page:
look here, the config stuff needed is in place. Deleted line 125:
To browse all uploaded images use http://electro-music.com/wiki/uploads/ Changed line 120 from:
to:
Changed line 115 from:
to:
Changed line 115 from:
to:
Changed line 115 from:
to:
Changed line 120 from:
to:
Changed line 120 from:
to:
Added line 120:
Added lines 122-125:
To browse all uploaded images use http://electro-music.com/wiki/uploads/ Changed line 112 from:
to:
Added line 112:
Added lines 1-2:
Keep an eye on this page for all the site specifics that are not in the genral PmWiki help pages. Added lines 1-2:
This page was last modified on 2013-04-14 21:12 [UTC-7].
Added lines 51-52:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%% Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names. to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.%%
Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names. Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
Changed line 9 from:
(:remark Be sure to read the uploads help for the wiki at [[http://www.pmwiki.org/wiki/PmWiki/Uploads]] - especially the bit about no spaces in file names.:)
to:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
Changed line 9 from:
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
to:
(:remark Be sure to read the uploads help for the wiki at [[http://www.pmwiki.org/wiki/PmWiki/Uploads]] - especially the bit about no spaces in file names.:)
Changed lines 3-7 from:
site wide icons are to be found in Site.Icons
to include a site wide icon use markup like Attach:Site.Icons/download.gif to get
Please upload icon like images to be used on many pages to Site.Icons
to:
site wide icons are to be found in Site.Icons
to include a site wide icon use markup like Attach:Site.Icons/download.gif to get
Please upload icon like images to be used on many pages to Site.Icons
Be sure to read the uploads help for the wiki at http://www.pmwiki.org/wiki/PmWiki/Uploads - especially the bit about no spaces in file names.
Added lines 6-7:
Please upload icon like images to be used on many pages to Site.Icons
Changed line 5 from:
to include a site wide icon use markup like Attach:Site./download.gif to get Attach:Site./download.gif Δ
to:
to include a site wide icon use markup like Attach:Site.Icons/download.gif to get
Added lines 4-5:
to include a site wide icon use markup like Attach:Site./download.gif to get Attach:Site./download.gif Δ
Changed line 13 from:
To get a listen link for this track use the markup
to:
To get a listen and download link for this track use the markup
Added lines 20-21:
Where the first icon is a direct listen and the second a download - the direct listen seems to not work in chrome.
Changed line 92 from:
to:
Changed line 23 from:
Using links this way the listen counts on the forum will be maintained.
to:
By using links this way the listen counts on the forum will be maintained.
Added lines 33-38:
You can also not specify a file extension in the the argument, like
(:audio myaudio:)
and then upload both an mp3 and an ogg file, the user's browser will then select what it likes best.
Changed line 15 from:
->{track: 33479 | Muied Lumens - music for walkmen} to:
{track: 33479 | Muied Lumens - music for walkmen}
Changed line 15 from:
{track: 33479 | Muied Lumens - music for walkmen}
to:
->{track: 33479 | Muied Lumens - music for walkmen} Changed lines 9-18 from:
Use {track: xxxxx | track title} to link to music posted on the forums, xxxxx being the track ID. For example the forum track http://electro-music.com/forum/download.php?id=33479 (from this page) has track ID 33479 and is called Muied Lumens - music for walkmen. To get a listen link for this track use the markup {track: 33479 | Muied Lumens - music for walkmen} which results in to:
Use {track: xxxxx | track title} to link to music posted on the forums, xxxxx being the track ID.
For example the forum track http://electro-music.com/forum/download.php?id=33479 (from this page) has track ID 33479 and is called Muied Lumens - music for walkmen.
To get a listen link for this track use the markup
{track: 33479 | Muied Lumens - music for walkmen}
which results in
Changed lines 21-24 from:
You can look up track IDs in the forum's media page by hovering your mouse over the track title or the speaker symbol in front of it. Using links this way the listen counts on the forum will be maintained. to:
You can look up track IDs in the forum's media page by hovering your mouse over the track title or the speaker symbol in front of it.
Using links this way the listen counts on the forum will be maintained.
Changed lines 27-51 from:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags (:audio myaudio.mp3:) or (:audio myaudio.ogg:) (where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Wav files should work too btw ... but they are getting large quickly ... For extra options have a look at http://www.pmwiki.org/wiki/Cookbook/Audio5 , please do not use auto starting audio. the following setup is in confg.php: $AudioPreload = 'auto'; // (auto|metadata|none) $AudioAutoplay = 0; $AudioControls = 1; $AudioLoop = 0; Audio uploaded to the wiki is not shared with the forum. An example: (:audio test07.ogg:) - Blue Hell - test07 gives: (:audio test07.ogg:) - Blue Hell - test07 to:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags
(:audio myaudio.mp3:) or
(:audio myaudio.ogg:)
(where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Wav files should work too btw ... but they are getting large quickly ...
For extra options have a look at http://www.pmwiki.org/wiki/Cookbook/Audio5 , please do not use auto starting audio.
the following setup is in confg.php:
$AudioPreload = 'auto'; // (auto|metadata|none)
$AudioAutoplay = 0;
$AudioControls = 1;
$AudioLoop = 0;
Audio uploaded to the wiki is not shared with the forum.
An example:
(:audio test07.ogg:) - Blue Hell - test07
gives: (:audio test07.ogg:) - Blue Hell - test07
Changed lines 54-55 from:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. For an example see http://electro-music.com/wiki/pmwiki.php?n=Articles.FeedbackOrNoInputMixing - scroll down a bit. to:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. For an example see http://electro-music.com/wiki/pmwiki.php?n=Articles.FeedbackOrNoInputMixing - scroll down a bit.
Changed lines 69-73 from:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% for the markup. to:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use
%class=electro_blue%electro_blue%%
for the markup.
Changed line 87 from:
to:
Changed line 87 from:
to:
Changed lines 1-2 from:
use:
to:
use:
Changed lines 7-8 from:
embed forum music:
to:
embed forum music:
Changed lines 25-26 from:
embed non forum (uploaded) audio:
to:
embed non forum (uploaded) audio:
Changed lines 52-53 from:
embed video:
to:
embed video:
Changed lines 56-57 from:
forum colors:
to:
forum colors:
Changed line 77 from:
The following extensions were installed 26 :
to:
The following extensions were installed 27 :
Changed lines 48-50 from:
(:audio test07.ogg:) - Blue Hell - test07.ogg gives: (:audio test07.ogg:) - Blue Hell - test07.ogg to:
(:audio test07.ogg:) - Blue Hell - test07 gives: (:audio test07.ogg:) - Blue Hell - test07 Changed line 48 from:
(:audio test07.ogg:) to:
(:audio test07.ogg:) - Blue Hell - test07.ogg Changed lines 46-48 from:
An example (using (:audio test07.ogg:)) to:
An example: (:audio test07.ogg:) Changed lines 46-50 from:
An example (:audio test07.ogg:) to:
An example (using (:audio test07.ogg:)) gives: (:audio test07.ogg:) - Blue Hell - test07.ogg Changed line 46 from:
An example (:audio test07.ogg:) to:
An example (:audio test07.ogg:) Changed line 46 from:
An example (:audio 07.ogg:) to:
An example (:audio test07.ogg:) Changed line 48 from:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. to:
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. For an example see http://electro-music.com/wiki/pmwiki.php?n=Articles.FeedbackOrNoInputMixing - scroll down a bit. Added lines 35-42:
the following setup is in confg.php: $AudioPreload = 'auto'; // (auto|metadata|none) $AudioAutoplay = 0; $AudioControls = 1; $AudioLoop = 0; Changed lines 1-2 from:
!!!use: to:
use:
Changed lines 7-8 from:
!!!embed forum music: to:
embed forum music:
Changed lines 25-26 from:
!!!embed non forum (uploaded) audio: to:
embed non forum (uploaded) audio:
Changed lines 38-39 from:
!!!embed video: to:
embed video:
Changed lines 42-43 from:
!!!forum colors: to:
forum colors:
Changed line 63 from:
!!!The following extensions were installed 28 : to:
The following extensions were installed 29 :
Changed lines 1-2 from:
!!!use: to:
!!!use: Changed lines 7-8 from:
!!!embed forum music: to:
!!!embed forum music: Changed lines 25-26 from:
!!!embed non forum (uploaded) audio: to:
!!!embed non forum (uploaded) audio: Changed lines 38-39 from:
!!!embed video: to:
!!!embed video: Changed lines 42-43 from:
!!!forum colors: to:
!!!forum colors: Changed line 63 from:
!!!The following extensions were installed 30 : to:
!!!The following extensions were installed 31 : Changed lines 1-2 from:
use:
to:
!!!use: Changed lines 7-8 from:
embed forum music:
to:
!!!embed forum music: Changed lines 25-26 from:
embed non forum audio:
to:
!!!embed non forum (uploaded) audio: Changed lines 38-39 from:
embed video:
to:
!!!embed video: Changed lines 42-43 from:
forum colors:
to:
!!!forum colors: Changed line 63 from:
The following extensions were installed 32 :
to:
!!!The following extensions were installed 33 : Added lines 33-36:
For extra options have a look at http://www.pmwiki.org/wiki/Cookbook/Audio5 , please do not use auto starting audio. Audio uploaded to the wiki is not shared with the forum. Changed line 32 from:
(where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. to:
(where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Wav files should work too btw ... but they are getting large quickly ... Changed lines 27-32 from:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags (:audio myaudio.np3:) or (:audio myaudio.ogg:) (where ogg is preferred as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. to:
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags (:audio myaudio.mp3:) or (:audio myaudio.ogg:) (where ogg is preferred over mp3 as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Changed line 25 from:
embed non forum audio
to:
embed non forum audio:
Added lines 24-27:
embed non forum audio
Use this sparingly, forum posts are preferred, yet local audio illustrations could make sense. Use the audio tags (:audio myaudio.np3:) or (:audio myaudio.ogg:) (where ogg is preferred as it works in most browsers) to define an inline audio element. After that the audio file will need to be uploaded, it works the same way as an image attach / upload. Added line 60:
Changed lines 7-8 from:
forum music:
to:
embed forum music:
Changed line 25 from:
video
to:
embed video:
Changed lines 7-8 from:
music:
to:
forum music:
Added lines 24-27:
video
Just use a YouTube, Vimeo, GoogleVideo or FlickrVid link - it should expand into a player box. Changed line 55 from:
to:
Changed line 6 from:
to:
Changed line 6 from:
to:
Changed line 18 from:
https://electro-music.com/wiki/uploads/Site/Icons/listen.gif https://electro-music.com/wiki/uploads/Site/Icons/download.gif %class=track_item%Muied Lumens - music for walkmen%%.
to:
https://electro-music.com/wiki/uploads/Site/Icons/listen.gif https://electro-music.com/wiki/uploads/Site/Icons/download.gif %class=track_item%Muied Lumens - music for walkmen%%
Changed line 12 from:
To get a listen link for that use the markup to:
To get a listen link for this track use the markup Changed line 14 from:
{track: 33479 | Muied Lumens - music for walkmen}, to:
{track: 33479 | Muied Lumens - music for walkmen} Changed lines 12-16 from:
To get a listen link for that use the markup {track: 33479 | Muied Lumens - music for walkmen}, which then results in to:
To get a listen link for that use the markup {track: 33479 | Muied Lumens - music for walkmen}, which then results in Changed line 18 from:
Using links this way the listen counts as maintained on the forum will be maintained. to:
Using links this way the listen counts on the forum will be maintained. Changed lines 5-18 from:
to:
music:
Use {track: xxxxx | track title} to link to music posted on the forums, xxxxx being the track ID. For example the forum track http://electro-music.com/forum/download.php?id=33479 (from this page) has track ID 33479 and is called Muied Lumens - music for walkmen. To get a listen link for that use the markup {track: 33479 | Muied Lumens - music for walkmen}, which then results in https://electro-music.com/wiki/uploads/Site/Icons/listen.gif https://electro-music.com/wiki/uploads/Site/Icons/download.gif %class=track_item%Muied Lumens - music for walkmen%%.
You can look up track IDs in the forum's media page by hovering your mouse over the track title or the speaker symbol in front of it. Using links this way the listen counts as maintained on the forum will be maintained. Changed line 5 from:
to:
Changed line 5 from:
to:
Changed line 5 from:
to:
Changed line 5 from:
to:
Added line 5:
Changed line 21 from:
->%class=electro_blue%electro_blue%% to:
%class=electro_blue%electro_blue%% Changed line 21 from:
%class=electro_blue%electro_blue%% to:
->%class=electro_blue%electro_blue%% Changed lines 19-23 from:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% for the markup. to:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% for the markup. Changed line 19 from:
These have been added to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. to:
These have been added to the main style sheet as .electro_blue etc. For instance, to make a bit of text electro_blue you can use %class=electro_blue%electro_blue%% for the markup. Changed line 19 from:
These have been edited to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. to:
These have been added to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. Changed lines 6-7 from:
colors 34:
to:
colors:
Changed line 19 from:
Thise have been edited to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. to:
These have been edited to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. Added lines 18-19:
Thise have been edited to the main style sheet. For instance to make text electro_blue use %class=electro_blue%electro_blue%%. Changed lines 28-29 from:
to:
Changed lines 12-16 from:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color
* electro-back is #ffffff or rgb( 255, 255, 255) white
* electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color
* electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells
* electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color
to:
* electro_blue is #255293 or rgb( 37, 82, 147) dark blue site color
* electro_back is #ffffff or rgb( 255, 255, 255) white
* electro_light is #efefef or rgb( 239, 239, 239) lightest table cell color
* electro_mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells
* electro_dark is #d2d6df or rgb( 210, 214, 223) the darker table cell color
* electro_hover is #eb6f6f or rgb( 204, 111, 111) sort of red, link hover color
Changed line 24 from:
to:
Changed line 25 from:
to:
Changed line 20 from:
The following extensions were installed 38 :
to:
The following extensions were installed 39 :
Changed line 22 from:
||border=1 width=95% style="border-collapse:collapse" class="left"
to:
Changed line 22 from:
||border=1 width=95% style="border-collapse:collapse" class="left"
to:
||border=1 width=95% style="border-collapse:collapse" class="left"
Changed line 22 from:
to:
||border=1 width=95% style="border-collapse:collapse" class="left"
Changed lines 13-16 from:
* electro-back is #ffffff or rgb( 255, 255, 255) white * electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color * electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells * electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color to:
* electro-back is #ffffff or rgb( 255, 255, 255) white
* electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color
* electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells
* electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color
Changed line 12 from:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color to:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color
Deleted lines 5-6:
forum color example Added lines 8-9:
forum color example Changed lines 12-16 from:
to:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color * electro-back is #ffffff or rgb( 255, 255, 255) white * electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color * electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells * electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color
Added lines 6-7:
forum color example Deleted lines 8-9:
forum color example Changed lines 10-14 from:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color * electro-back is #ffffff or rgb( 255, 255, 255) white * electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color * electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells * electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color to:
Changed lines 1-2 from:
use: to:
use:
Changed line 16 from:
The following extensions were installed 44 : to:
The following extensions were installed 45 :
Added lines 6-7:
forum color example Deleted lines 14-15:
forum color example Changed lines 8-12 from:
* electro-blue is #255293 or rgb( 37, 82,147) dark blue site color * electro-back is #ffffff or rgb(255,255,255) white * electro-light is #efefef or rgb(239,239,239) lightest table cell color * electro-mid is #dee3e7 or rgb(222,227,231) a mid color for table cells * electro-dark is #d2d6df ir rgb(210,214,223) the darker table cell color to:
* electro-blue is #255293 or rgb( 37, 82, 147) dark blue site color * electro-back is #ffffff or rgb( 255, 255, 255) white * electro-light is #efefef or rgb( 239, 239, 239) lightest table cell color * electro-mid is #dee3e7 or rgb( 222, 227, 231) a mid color for table cells * electro-dark is #d2d6df ir rgb( 210, 214, 223) the darker table cell color Changed lines 8-9 from:
* electro-blue is #255293 or rgb(37,82,147) dark blue site color * electro-back is #ffffff or rgb(255,255,255) white to:
* electro-blue is #255293 or rgb( 37, 82,147) dark blue site color * electro-back is #ffffff or rgb(255,255,255) white Changed lines 11-12 from:
* electro-mid is #dee3e7 or rgb(222,227,231) a mid color for table cells * electro-dark is #d2d6df ir rgb(210,214,223) the darker table cell color to:
* electro-mid is #dee3e7 or rgb(222,227,231) a mid color for table cells * electro-dark is #d2d6df ir rgb(210,214,223) the darker table cell color Changed lines 6-10 from:
to:
* electro-blue is #255293 or rgb(37,82,147) dark blue site color * electro-back is #ffffff or rgb(255,255,255) white * electro-light is #efefef or rgb(239,239,239) lightest table cell color * electro-mid is #dee3e7 or rgb(222,227,231) a mid color for table cells * electro-dark is #d2d6df ir rgb(210,214,223) the darker table cell color Changed lines 5-11 from:
electro-blue is #255293 or rgb(37,82,147) ... this needs a color definition still to:
these need color definitions still Changed line 10 from:
to:
Changed line 10 from:
to:
Changed lines 10-13 from:
to:
Changed lines 12-13 from:
to:
Changed lines 9-14 from:
* $RecipeInfo['AuthPhpbb2Sso']['Version'] = '080401'; - http://www.pmwiki.org/wiki/Cookbook/AuthPhpbb2Sso - for coupling to forum accounts * $RecipeInfo[ 'debug'][ 'Version'] = '130129'; - not published 49 - for debugging to a file * $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - http://www.pmwiki.org/wiki/Cookbook/Toggle - for sections to be switched in / out * define( FOOTNOTE_VERSION, '1.0.0' ); - http://www.pmwiki.org/wiki/Cookbook/Footnotes - for footnotes to:
Added lines 13-22:
Changed lines 7-14 from:
The following extensions were installed : * $RecipeInfo['AuthPhpbb2Sso']['Version'] = '080401'; - for coupling to forum accounts * $RecipeInfo[ 'debug'][ 'Version'] = '130129'; - for debugging to a file * $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - for sections to be switched in / out * define( FOOTNOTE_VERSION, '1.0.0' ); - for footnotes The skin used is emwiki, an edit of the standard pmwiki skin - it is not complete yet. to:
The following extensions were installed 51 : * $RecipeInfo['AuthPhpbb2Sso']['Version'] = '080401'; - http://www.pmwiki.org/wiki/Cookbook/AuthPhpbb2Sso - for coupling to forum accounts * $RecipeInfo[ 'debug'][ 'Version'] = '130129'; - not published 52 - for debugging to a file * $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - http://www.pmwiki.org/wiki/Cookbook/Toggle - for sections to be switched in / out * define( FOOTNOTE_VERSION, '1.0.0' ); - http://www.pmwiki.org/wiki/Cookbook/Footnotes - for footnotes The skin used is emwiki, an edit of the standard pmwiki skin - it is not complete yet. 1 slightly modified, see it's talk page on the PmWiki site: http://www.pmwiki.org/wiki/Cookbook/AuthPhpbb2Sso-Talk ⇑ 2 slightly modified, see it's talk page on the PmWiki site: http://www.pmwiki.org/wiki/Cookbook/AuthPhpbb2Sso-Talk ⇑ 3 some special needs programmed in, see calendar section ⇑ 4 local development, to be sorted out ⇑ 5 local development, to be sorted out ⇑ 6 modified slightly to allow access by WikiAdmins ⇑ 7 modified slightly to allow access by WikiAdmins ⇑ 8 This syntax is likely to be made easier later on ⇑ 9 modified slightly to allow access by WikiAdmins ⇑ 10 in the cookbook directory and/or the local config file ⇑ 11 in the cookbook directory and/or the local config file ⇑ 12 slightly modified, see it's talk page ⇑ 13 slightly modified, see it's talk page on the PmWiki site: http://www.pmwiki.org/wiki/Cookbook/AuthPhpbb2Sso-Talk ⇑ 14 in the cookbook directory ⇑ 15 in the cookbook directory and/or the local config file ⇑ 16 only the viewer - no admin interface ⇑ 17 only the viewer - no admin interface - small modifications * suppressed a PHP warning * display image file names for captions when there are none ⇑ 18 footnotes, yup, like this, jsut edit this page to see how ⇑ 19 footnotes, yup, like this, just edit this page to see how ⇑ 20 footnotes, yup, like this ⇑ 21 footnotes, yup, like this, jsut edit this page to see how ⇑ 22 footnotes, yup, like this ⇑ 23 only the viewer - no admin interface ⇑ 24 some small changes to get PHP undefined variable usage messages out ⇑ 25 some bugs fixed on this one ⇑ 26 in the cookbook directory ⇑ 27 in the cookbook directory ⇑ 28 in the cookbook directory ⇑ 29 in the cookbook directory ⇑ 30 in the cookbook directory ⇑ 31 in the cookbook directory ⇑ 32 in the cookbook directory ⇑ 33 in the cookbook directory ⇑ 34 these need color definitions still ⇑ 35 slightly modified, see it's talk page ⇑ 36 local development to be sorted out ⇑ 37 local development, to be sorted out ⇑ 38 into the cookbook directory ⇑ 39 in the cookbook directory ⇑ 40 these need color definitions still ⇑ 41 these need color definitions still ⇑ 42 these need color definitions still ⇑ 43 these need color definitions still ⇑ 44 into the cookbook directory ⇑ 45 into the cookbook directory ⇑ 46 these need color definitions still ⇑ 47 local development to be sorted out ⇑ 48 local development to be sorted out ⇑ 49 local development to be sorted out ⇑ 50 local development to be sorted out ⇑ 51 into the cookbook directory ⇑ 52 local development to be sorted out ⇑ Changed lines 11-13 from:
* $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - for sections to be switched in / out to:
* $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - for sections to be switched in / out The skin used is emwiki, an edit of the standard pmwiki skin - it is not complete yet. Changed lines 9-11 from:
to:
* $RecipeInfo['AuthPhpbb2Sso']['Version'] = '080401'; - for coupling to forum accounts * $RecipeInfo[ 'debug'][ 'Version'] = '130129'; - for debugging to a file * $RecipeInfo['Toggle']['Version'] = '2011-04-06'; - for sections to be switched in / out Changed lines 9-11 from:
to:
Changed lines 7-11 from:
to:
The following extensions were installed :
Added lines 1-7:
use
electro-blue is #255293 or rgb(37,82,147) ... this needs a color definition still
|
Edit - History - Print - Recent Changes - Search Page last modified on 2013-04-14 21:12 [UTC-7] - 2653 views