
![]() |
Show Changes |
![]() |
Edit |
![]() |
|
![]() |
Recent Changes |
![]() |
Subscriptions |
![]() |
Lost and Found |
![]() |
Find References |
![]() |
Rename |
![]() |
Administration Page |
| Search |
History
| 9/18/2008 5:26:09 PM |
| 66.78.111.231 |
| 8/12/2008 2:31:16 PM |
| 193.37.152.116 |
| 8/12/2008 2:17:33 PM |
| 193.37.152.116 |
| 8/12/2008 9:02:15 AM |
| 193.37.152.116 |
| 8/12/2008 8:09:46 AM |
| 193.37.152.116 |
![]() |
List all versions |
FlexWiki has a lot of bugs and formatting topic titles with exotic characters is often impossible. Below is a list of hacks to get around the bugs with intended and unintended consequences.
1 Does anyone know how to make those links to the topics below?
Creating a topic title with a colon may be impossible.
For example, to create Mt 5:30 as the title name, it will not create a link by smashing the link together like this: Mt5:30 or TopicName(12)
[Mt5:30] or [TopicName(12)]
To work around this, the following was suggested
@@Presentations.Link([federation.LinkMaker.LinkToTopic("Mt 5:30")].ToOneString, "Mt 5:30")@@
Mt 5:30
If you try to type Mt5:30 or Mt 5:30 in the topic bar, it will give you an application error.
None found yet
You can create topics with parentheses in special cases. The problem seems to be ending with a closing parenthisis.
Paragraph(12)a (Paragraph)12 Paragraph)12(Some system topics begin with an underscore: _NormalBorders, _InterWikis
Creating topic links to these can be troublesome.
If the topic, for example _NormalBorders, exists in a simple paragraph like this one then no problem.
But if you introduce an InterWiki topic before (example _NormalBorders) and after then the topic fails to render correctly (the underscore is missing and the URL has <em> instead).
And if you introduce WikiTalk before (example _NormalBorders) and after then the topic fails to render correctly (the underscore is missing and the URL has <em> instead).
Bug entered:
https://sourceforge.net/tracker/index.php?func=detail&aid=1237940&group_id=113273&atid=665396
--JoeGasper
Bug fixed as of build 1712 - NathanJones