Hi,
i have a problem with german Umlaute when creating a new Page. The Umlaute
are not displayed correctly, but when i rename the page, then its works
correctly and the Umlaute are displayed. This problem appears only after
creating the page.
There are any solutions known?
Thanks
Regards,
Silvio
--
View this message in context: http://xwiki.475771.n2.nabble.com/Problem-with-german-Umlaute-a-o-u-when-cr…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
I'm testing installation of an extension with extension manager / extension
repository, on XE 4.3-milestone-2:
- deploy my extension (xar + deps) from maven to a local nexus
- import this extension into the extension repo in my xwiki
- try to install it with EM
I get a conflict:
Dependency [javax.jcr:jcr-2.0] is not compatible with core extension
[javax.jcr:jcr-1.0]
This dependency is a transitive dependency (runtime) of a mstor library
needed by my app. Currently, it is used in xwiki in version 1.0.
I first tried to add an <exclusion> block for it in my pom.xml, redeployed,
reimported, reinstalled, with same result.
I then added jcr 1.0 in a dependencyManagement section in order to override
version 2.0 brought by mstor, but again with same result.
BTW, additionally, the folder targeted by xwiki.data.dir remains empty ...
Seems a bit strange.
How can I solve this issue ?
Thanks,
Jeremie
Hi,
I know there have been discussions on collapsed panel headers
I've had user complaints about the 'complexity' of our website (based on XWiki).
After analysis of the complaints one of the reasons for perceived complexity were the panels
They distracted the focus from the content, because each panel (we use approx 4 on the left and 2 or 3 on the right) (www.cdlsworld.org)) contains links/information.
Sending screen shots of the site with collapsed panels was rated significantly 'easier'. The panel header is descriptive enough.
What is today's recommended strategy to have the panels collapsed by default (i would really like this to be a attribute when you define a panel; like a checkbox; default collapsed!)
We do not require user configuration here; the state of the panel does not have to be remembered per user session. We would rather have 'rules by context' If user has certain rights, if user is in certain space'
But this is a nice to have, not a must have; we would be fine if one single panel is always collapsed when entering a page. And for another panel that it is always open and can be collapsed!
Any recommendation would be highly appreciated...
My own thoughts are that this might be something for javascript; the script could collapse the panel...
Downside of javascript is that 'older' computers or users that have javascript disabled might not benefit, that would suggest a serverside setting of the CSS class ?
Gerritjan
I am just discovering XWiki and I am looking for some advice from more
experienced users on how to structure my wiki.
I am a data analyst at a hospital and would like to introduce a wiki into
our team. I feel XWiki is the best wiki engine for us to use because of the
WYSIWYG editor and the Office importer, which should help in the initial
adoption stage.
The aim of introducing a wiki would be to improve supporting documenting and
create more robust documentation on the following areas:
1. Definitions of measures - what it means, how it is calculated, what may
be excluded from this measure
2. Supporting user documentation to reports produced - how to navigate the
interactive reports, what the various graphs and charts represent
3. Document SQL databases/data warehouse - there are a whole host of
databases in the organisation that either no-one has no knowledge or one
person has knowledge of it. Documentation on the schemas, tables, views,
stored procedures, relationships etc.
4. Procedure information on how to produce reports - step by step on how to
produce a report extract. This documentation already exists in word
documents hosted in SharePoint libraries.
5. Technical documentation on how to produce reports - this would document
the inner workings DTS/SSIS packages or Microsoft Access databases that are
run as part of the procedure information.
Let me give you an example which may help you understand the situation
better.
There are various spreadsheet reports produced based on the number of weeks
patients have waited for treatment, referred to as 18 weeks, with numerous
measures used throughout.
The current documentation on how to produce these reports are split over
multiple word documents as the process is run in two stages on a Monday and
Thursday, both are very lengthy around 30 pages each. The documentation is a
step by step guide on how to produce the reports/extracts e.g. open this
file, copy and paste this, run this DTS package etc. To produce these
reports, another set of procedures need to be complete before as some of the
data produced by this process supports the 18 week process.
The entire process is based on a Microsoft Access database which an
ex-employee created and no-one knows anything about it's inner workings nor
is there any documentation on this database. Having looked at it briefly,
the database connects to an SQL server and uses data stored in some tables
which are produced by scheduled DTS packages - again which aren't
documented.
Thinking about how to logically store all this information within XWiki and
provide some clear structure, my thoughts were as follows:
Create virtual wikis which are based on the target audience/purpose
Create spaces for each of the subject areas/databases
Use tags to provide further categories, in particular for documenting
databases.
This would look something like this:
An XWiki for consumers of reports, this would contain documentation on
measures and supporting documentation on interpreting the various reports
produced. This wiki would be split into various spaces based on the subject
area, e.g. 18 Weeks, Inpatient, Outpatient.
An XWiki for procedural documentation on how to produce the various reports.
This would be split into various spaces based on the same subject areas as
the previous XWiki.
An XWiki for technical documentation on databases/DTS/SSIS packages. This
would be split into spaces for the various databases and would use tags to
distinguish between the different type of pages within the space e.g.
documentation on tables, views, stored procedures, functions.
Whilst the first two XWikis make sense and I don't see any issues with the
structure, it is the technical documentation part which I think may be
difficult to navigate. Perhaps the DTS/SSIS packages would need there own
XWiki as they are at a server level and not database level.
I am hopeful to hear your thoughts on the suggestions above.
Any help if greatly appreciated.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Looking-for-advise-on-structuring-XWiki-t…
Sent from the XWiki- Users mailing list archive at Nabble.com.
The XWiki development team is proud to announce the availability of XWiki
Enterprise 4.3 Milestone 2.
This release brings:
- a new and experimental Solr Search engine
- new default date, user and group pickers
- a new localization module allowing applications to register translations
- REST API additions
- various other improvements.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki43M2
Thanks
-The XWiki dev team
Hi,
i am very new to Xwiki. I have added the statistic Panel "MostViewedPages"
with the Panel-Wizard and saved the new Layout successfully. Now the new
Panel is visible for me - as Administrator - but not for normal Users. Why?
Maybe there are not enough collected informations at this moment? Or the
panel is only visible for Admins?
Thanks!
Kind Regards,
Silvio
--
View this message in context: http://xwiki.475771.n2.nabble.com/MostViewedPages-Panel-only-visible-for-Ad…
Sent from the XWiki- Users mailing list archive at Nabble.com.
You need to send messages to both me and xwiki-users list.
Everybody should share knowledges.
What I want to do is extract all object of a class from a specific page,
not the entire objects from the wiki database.
How should I modify the query in this case?
And where can I find all those XWQL object model references? (Yes, it
reminds me of DOM)
doc.object, etc, ...
On Tue, Nov 13, 2012 at 5:59 PM, Jeremie BOUSQUET <
jeremie.bousquet(a)gmail.com> wrote:
> Well, it's not because the name is the same that it's the same method or
> API ... :)
>
> XWiki core api is a Java api, available to components and scripts
> (velocity, groovy ...). It provides access to documents as well as various
> features of the wiki.
>
> XWQL is a query language, superset of JPQL (Java Persistence Query
> Language ?) with some differences. You use it to query the data stored in
> the database.
> One of the differences between jpql/xwql is the syntax
> "doc.object(MyClass)" that selects all XObjects belonging to a particular
> XClass from the database. Apart from that, if you know JPQL then you mostly
> know XWQL.
>
> ("doc.getObject("MyClass")" , from java api, retrieves XObjects of a
> particular XClass from specified document only (and not from the whole
> wiki).)
>
>
>
> 2012/11/13 crocket <crockabiscuit(a)gmail.com>
>
>> Isn't doc.object(Class) part of XWiki core API?
>> I thought it was an alias of $doc.getObject("Class")
>>
>> I want to know what APIs XWQL has access to, but I couldn't find the
>> information.
>> On Mon, Nov 12, 2012 at 11:42 PM, Jeremie BOUSQUET <
>> jeremie.bousquet(a)gmail.com> wrote:
>>
>>> doc.getObjects("MyClass") is from the xwiki core java api, but is not
>>> part of the XWQL querying language.
>>>
>>> The query:
>>>
>>> select srv.port from Document doc, doc.object(Private.Network Services)
>>> as srv order by srv.port
>>>
>>> ... translates to " select "port" field from all XObjects that are of
>>> class "Private.Network Services", ordering by "port" field "
>>> So this query would retrieve the value of "port" field from all of these
>>> XObjects (that we name "srv" in the query), wherever they are and whatever
>>> their count.
>>>
>>>
>>>
>>>
>>> 2012/11/12 crocket <crockabiscuit(a)gmail.com>
>>>
>>>> doc.getObjects was there since I had multiple instance of the same
>>>> class.
>>>>
>>>>
>>>>
>>>> On Mon, Nov 12, 2012 at 8:32 PM, Jeremie BOUSQUET <
>>>> jeremie.bousquet(a)gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I think this is not correct:
>>>>> select srv from IN (doc.getObjects("Private.Network Services")) srv
>>>>> order
>>>>> by srv.port
>>>>>
>>>>> Should be more something like:
>>>>> select srv.port from Document doc, doc.object(Private.Network
>>>>> Services) as
>>>>> srv order by srv.port
>>>>>
>>>>> Replacing the "select srv.port" by what fields you want to retrieve.
>>>>>
>>>>> Though obviously I'm not sure about what you wanted to achieve with
>>>>> your
>>>>> request to start with ...
>>>>>
>>>>> Br,
>>>>> Jeremie
>>>>>
>>>>>
>>>>> 2012/11/12 crocket <crockabiscuit(a)gmail.com>
>>>>>
>>>>> > Yes, I read it, and it seems collection member declarations don't
>>>>> work in
>>>>> > xwiki.
>>>>> >
>>>>> >
>>>>> > On Mon, Nov 12, 2012 at 6:13 PM, Jerome Velociter <
>>>>> jerome(a)velociter.fr
>>>>> > >wrote:
>>>>> >
>>>>> > > Le 12/11/12 09:37, crocket a écrit :
>>>>> > >
>>>>> > > I tried to execute a Query and saw an error below.
>>>>> > >>
>>>>> > >> Caused by: org.xwiki.query.**QueryException: Exception while
>>>>> translating
>>>>> > >> [select srv from IN (doc.getObjects("Private.**Network
>>>>> Services")) srv
>>>>> > >> order by srv.port] XWQL query to the [hql] language. Query
>>>>> statement =
>>>>> > >> [select srv from IN (doc.getObjects("Private.**Network
>>>>> Services")) srv
>>>>> > >> order by srv.port]
>>>>> > >>
>>>>> > >> Although I read JPQL documents, I couldn't come out with an
>>>>> answer.
>>>>> > >>
>>>>> > >> Does anybody know how to write a correct XWQL statement?
>>>>> > >>
>>>>> > >
>>>>> > > Have you read
>>>>> http://extensions.xwiki.org/**xwiki/bin/view/Extension/**
>>>>> > > Query+Module#**HQueryLanguageExamples<
>>>>> >
>>>>> http://extensions.xwiki.org/xwiki/bin/view/Extension/Query+Module#HQueryLan…
>>>>> > >?
>>>>> > >
>>>>> > > Jerome
>>>>> > >
>>>>> > >> ______________________________**_________________
>>>>> > >> users mailing list
>>>>> > >> users(a)xwiki.org
>>>>> > >> http://lists.xwiki.org/**mailman/listinfo/users<
>>>>> > http://lists.xwiki.org/mailman/listinfo/users>
>>>>> > >>
>>>>> > >
>>>>> > > ______________________________**_________________
>>>>> > > users mailing list
>>>>> > > users(a)xwiki.org
>>>>> > > http://lists.xwiki.org/**mailman/listinfo/users<
>>>>> > http://lists.xwiki.org/mailman/listinfo/users>
>>>>> > >
>>>>> > _______________________________________________
>>>>> > users mailing list
>>>>> > users(a)xwiki.org
>>>>> > http://lists.xwiki.org/mailman/listinfo/users
>>>>> >
>>>>> _______________________________________________
>>>>> users mailing list
>>>>> users(a)xwiki.org
>>>>> http://lists.xwiki.org/mailman/listinfo/users
>>>>>
>>>>
>>>>
>>>
>>
>