I'd like to encourage users my my XWiki installation to meep useful
information about themselves in their profile, and then have other link to
them when referring to them by name in other topics, e.g.
"A decision was made by [Brian Sayatovic|XWiki.bsayatovic]" to keep useful
information in user profiles..."
However, all we can edit is the description. While you can put wiki syntax
in that texbox, it is a very small box to work within (I end up copying &
pasting from a text editor) and you don't have the wysiwig editor.
Is there a way around this, or should I enter this as an enhancement
request?
Regards,
Brian.
P.S. I posted this message to the list on 7/17, but it never appeared
-----------------------------------------
CONFIDENTIALITY STATEMENT:
This e-mail transmission contains information that is intended to
be confidential. It is intended only for the addressee named
above. If you receive this e-mail in error, please do not read,
copy, or disseminate it. If you are not the intended recipient,
any disclosure, copying, distribution or use of the contents of
this information is prohibited. Please reply to the message
immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer
system. Your assistance in correcting this error is appreciated.
I am wondering..
Is there any reason why ALL user documents have to be in the XWiki space?
Wouldn't it make more sense to have an XWikiUser space, and perhaps an
XWikiGroup space?
For those of us with large installs already, it would be a pain to move..
but it doesn't seem to me that auth code checking for users should care
much about what space the user document is in (aside from
authorization/access, I suppose, as that is based on the space), but
still, I think separating user and group documents out into their own
spaces would make navigation of the xwiki space easier...
thoughts?
--
Waste of a good apple. --Samwise Gamgee
Hi,
After I create a blog entry using Create New Blog Post (let's say I named it crumbTest) and then view the entry, the navigational breadcrumb shows as Blog:Administration>crumbTest.
I would have expected it to just say Blog:crumbTest. Where does the Administration come from? Is this the way it was intended to work?
My guess is the parent determines the breadcrumb - which is XWiki.Webhome.
I'd like to have the navigational crumbs be consistent with what space the user is in. I've looked at the templates/classes for the blog but I can't figure out where the parent gets set when the blog entry is created.
I also tried creating a blog entry from the Blog.WebHome using the Add an Article button -and the resulting document was stored in the Main space (rather than Blog) and its breadcrumb showed Main:Administration>crumbTest2.
Can you point me in the right direction?
Thanks!
Rene
Hi, XWiki team,
It seems to me that upgrading the XWiki version on XWiki farm is very hard to do since it is not done for quite some time. Is this an indicator that maintaining an XWiki server with live sites is not easy?
Is there a path for site managers to move up to the next version XWiki? Or, is there a way for users to get to the new version or get around the problems of the old version? Not everyday everyone is starting from a clean new version, everyone has to face the upgrading time. If XWiki farm sites have to stay in old, old version, I guess moving up is really difficult. It does not look good to potential new users.
Thanks for thinking about this issue.
Wei-hsing
Hi, XWiki users,
Are you going to Taipei for Wikimania 2007? (http://wikimania2007.wikimedia.org/wiki/Main_Page) Would you be interested in a meet-up?
Please contact me if you plan to go. I grew up in Taipei and know the software industry. It would be nice to have a XWiki user gathering.
Wei-hsing
ps. Those who contacted me before, please do so again to confirm you are still going.
Hi,
I looked today over the XWikiMessageTool class, and I must say that I'm not
quite satisfied with it.
First, there was XWIKI-919, which I implemented. OK, I understand that files
stored on disk should be charset independent, so only ASCII characters are
supported by the ResourceBundle class (jvm) .But, when I can edit a wiki
document for storing bundles, I expect it to accept all the characters the
wiki supports (in my case, it was an UTF8 instance). I had some troubles
fixing this, since the JavaDoc says that bundles accepts only ASCII
characters, but it understands and parses unicode references ( \u0123 ).
Maybe I did something wrong, but doing content.replaceAll("\u0139",
"\\u0139") resulted in the string u0139 being displayed in the page. So I
had to trick it into believing that the component bytes of the encoding are
ASCII characters and manually restore the multibyte chars.
Second, I don't like the fact that XWIKI-921 was not already implemented.
Third, I don't like the cache refresh mechanism. It retrieves the
XWikiProperties->documentBundles property for each request, and It retrieves
the bundle documents for every request and checks if it must be refreshed or
not. Why isn't the com.xpn.xwiki.notify package used? It allows registering
callback handlers for specific document changes. How I see it:
- at startup, register a handler for XWiki.XWikiPreferences (so that we know
when the documentBundles property might change).
- remember the list of document bundles, don't ask it for each request
- also register handlers for the current bundle documents and load the
strings from these documents
- when XWikiPreferences is changed, if the documentBundle property is also
changed, remove the unused bundles and build the new ones
- when a undle document (or a translation for it) is changed, rebuild the
bundle for that document
This should speedup the code a bit, it makes use of a nice, but mostly
unknown feature, it doesn't log an error for each request when a specified
document is not found in the wiki, and it doesn't require so many variables
(previousDates, docsToRefresh).
Fourth, as I said above, if a document is specified in the documentBundles
property, but it does not exist in the wiki, for each $msg.get call an error
is logged. And there are a lot of calls for each request.
Now, in my opinion this is a nice way to get in the core of XWiki for a
newcomer, so does anybody want to write the changes I mentioned? Also, this
is a good occasion to document the event notification mechanism, in JavaDoc
and on www.xwiki.org
Regards,
Sergiu Dumitriu
--
http://purl.org/net/sergiu
Hi,
First; thanks to everyone who helped me make more blogs in my xwiki, it works beautifully! (though it's not the most beautiful code ever written...)
Second;
As far as I can tell there are no links from anywhere in the administration or editing modes to get back to the rest of the wiki. (there are save and cancel options, but that's not the same thing as 'Back') Have I missed something? If not; any hints on how and where to add such links?
For usability purposes- to make life easier for the future admins of the xwiki I'm setting up...
Thanks,
Karin
For a private wiki (with different companies involved), the use of email-addresses as userid would be great. Is there a possibility to achieve this?
Thanks,
Hanspeter
