Thank you for the new Release, Marius!
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki52RC1#HNe…
Is it possible to disable/enable this Home menu item by purpose besides changing vm files and attaching them to the skin page?
Use case is following:
Home Wiki (Main Wiki)
1. Workspaces:
- workspace 1
.....
- workspace N
2. Wiki farm:
- wiki farm 1
In the Workspaces I can guess, I'd need Home menu sometimes. Probably. But in most of cases, in the wiki-farm I'd prefer users would not even know about each other.
Are you going to make it configurable via UI?
Понедельник, 30 сентября 2013, 16:22 +03:00 от Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com>:
>The XWiki development team is proud to announce the availability of
>XWiki 5.2 Release Candidate 1.
>This is mostly a stabilization release leading to XWiki 5.2 final and
>it brings a new "Home" top level menu (available when there is more
>than one wiki) and a new Distribution Wizard step to upgrade all
>wikis. The WikiStream framework has been improved and now can be used
>to export large wikis in XAR format. Besides this the new release
>includes 49 bug fixes and 16 small 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/ReleaseNotesXWiki52RC1
>
>Thanks
>-The XWiki dev team
>_______________________________________________
>users mailing list
>users(a)xwiki.org
>http://lists.xwiki.org/mailman/listinfo/users
Kind regards,
Dmitry
Hi
I have a problem with a URL containing a parameter of the form
action_...=... The page does not load with this parameter. For an example
see the xwiki.org start page (
http://www.xwiki.org/xwiki/bin/view/Main/WebHome?action_xyz).
The parameter action_... seems to be used for something, but I couldn't
find anything on what exactly and on how I can work around that.
Unfortunately this URL is created by an external source (Facebook), so I
can't change it.
Can somebody point me in the right direction?
Thanks,
Edo
The XWiki development team is proud to announce the availability of
XWiki 5.2 Release Candidate 1.
This is mostly a stabilization release leading to XWiki 5.2 final and
it brings a new "Home" top level menu (available when there is more
than one wiki) and a new Distribution Wizard step to upgrade all
wikis. The WikiStream framework has been improved and now can be used
to export large wikis in XAR format. Besides this the new release
includes 49 bug fixes and 16 small 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/ReleaseNotesXWiki52RC1
Thanks
-The XWiki dev team
Hello,
I'm trying to use the Job Module [1] for my own needs.
I know some of its APIs are marked as unstable, but well I wanted to give
it a try.
I'm on a XWiki 4.5.2 instance currently.
So I created some dummy interface:
@Role
public interface ILoadingJob extends Job
{
}
A Job implementation:
@Component
@Named(LoadingJob.JOBTYPE)
public class LoadingJob extends AbstractJob<DefaultRequest> implements
ILoadingJob, Initializable
{
public static final String JOBTYPE = "mailarchivejob";
// ...
}
In debug mode, I run the following:
this.componentManager.getComponentDescriptorList(org.xwiki.job.Job.class)
It returns:
[implementation = [org.xwiki.contrib.mailarchive.internal.LoadingJob],
instantiation = [PER_LOOKUP], implementation =
[org.xwiki.extension.job.internal.UpgradePlanJob], ... ]
So it seems OK.
I have the following code to create and execute my Job:
DefaultRequest request = new DefaultRequest();
request.setId("test");
request.setInteractive(false);
// ... other properties set
LoadingJob job = (LoadingJob)
jobManager.executeJob("mailarchivejob", request);
But this code fails with following stack trace:
org.xwiki.job.JobException: Failed to lookup any Job for role hint
[mailarchivejob]
at
org.xwiki.job.internal.DefaultJobManager.createJob(DefaultJobManager.java:185)
at
org.xwiki.job.internal.DefaultJobManager.addJob(DefaultJobManager.java:208)
at
org.xwiki.job.internal.DefaultJobManager.executeJob(DefaultJobManager.java:194)
at
org.xwiki.contrib.mailarchive.internal.MailArchiveScriptService.createLoadingJob(MailArchiveScriptService.java:112)
at
org.xwiki.contrib.mailarchive.internal.MailArchiveScriptService.load(MailArchiveScriptService.java:94)
[...]
Caused by: org.xwiki.component.manager.ComponentLookupException: Can't find
descriptor for the component [role = [interface org.xwiki.job.Job] hint =
[mailarchivejob]]
at
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:355)
at
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:161)
at
org.xwiki.job.internal.DefaultJobManager.createJob(DefaultJobManager.java:183)
[...]
I also tried to manually register my custom Job component, in the
initialize() of a side component (I checked that this code got executed
previously to job creation), but with no different result:
// Register custom job
this.componentManager.registerComponent(this.componentManager.getComponentDescriptor(Job.class,
"mailarchivejob"));
Do you see something wrong in my approach ?
Thanks,
Jeremie
I tried to write f(x) and got f followed by a pretty image of a red x.
My guess is that there's a help page showing these replacements and
how to avoid them, but I couldn't find it with a quick search. Where
should I look?
Thanks,
Todd
Hi there,
I'm investigating whether this wiki engine is right for me. I'm
looking for three specific design features:
1. able to attach autonomous agents to pages
2. transclusions / includes.
3. capability security model rather than ACLs
features #3 + #1 can easily be made to enact:
3a. patron blindness - users can become patrons of others and their
own patron is blind to that, but must deal with the entire
sub-hierarchy of users as a collective
which makes this other feature rather important:
3b. patron multiplicity - users can acquire multiple patrons just in
case their first patron decides to eradicate them
Oh and I suppose:
4. automatic garbage collection and revisions even of deleted pages
If you know of another wiki engine that supports these better, please
let me know. I know that Wagn supports transclusions but I'm rather
doubtful that anyone supports a capability security model. Even though
ACLs really should have died out in the 70s.
Thanks for reading this far,
Richard
I am having some issues with the site not properly displaying in IE. I
am using the Colibri skin.
The top bar (Add, wiki, etc..) is displayed under the page heading and
off to the right (starts above the right panel column and extends
right).
The site displays properly in FF, Chrome and Opera (although annotations
don't work in Opera properly).
Thoughts?
Paul Pinkerton
KnowledgeNow Project Lead
I am still hopeful that someone out there would be able to assist me
with this. The Navigation Menu Macro only properly displays 2 levels.
The 3rd level simply displays overtop of the 2nd, making it unusable.
It is not an option to use the newer macro, as it is incompatible with
the wiki version.
I did discover in looking at the html code that the macro assigns screen
placement values in the first 2 levels to "pop out" a menu. It fails to
assign values in the 3rd level (actually assigns 0,0,0...) Although I
could probably fix this by manually assigning values, it would be
helpful to know how to fix the macro, so that I don't have to custom
program every entry and every list!
You can see my previous post below here.
Assistance appreciated!
Paul Pinkerton
_______ previous post _________
Date: Fri, 20 Sep 2013 13:58:57 -0400
From: "Paul Pinkerton (ACLCO)" <pinkerp(a)lao.on.ca>
To: <users(a)xwiki.org>
Subject: [xwiki-users] Help with Navigation Menu Wiki Macro
Message-ID: <5ADF7493B6AD244BB1AA71BC4034DA3A091F04EF(a)ontario.lao.res>
Content-Type: text/plain; charset="us-ascii"
I am using the Nav Menu Wiki Macro to create some menus - and it's
working - but not completely.
I have the following issues:
In a horizontal menu, the 1st and 2nd levels appear correctly. When I
add a 3rd level, it displays overtop of existing text, rather
than'popping out'.
*Main1
** Sub1
*** Sub1Sub1
**Sub2
***Sub2Sub1
*Main2
In a vertical menu, the submenu items appear to the side, but below the
level of the related main menu item, making it difficult to move the
mouse to the submenu to select links there.
I have tried adding line spaces, etc.. but this doesn't affect the
display.
I did check online for existing solutions - and found this thread
detailing a similar issue from late 2012/ early 2013. No solutions were
offered.
http://xwiki.475771.n2.nabble.com/Navigation-Menu-Wiki-Macro-td7582112.h
tml#a7582455 (see Hamster's post of Nov 16, 2012 2:06 and following)
The poster suggests that the issue is in the JavaScript code.
Any help here would be appreciated.
Paul Pinkerton
KnowledgeNow Project Lead
Hey there,
im new to this whole xwiki stuff and trying to upgrade our xwiki
installation, which was installed by a former employee, to the latest build.
xwiki is installed on ubuntu 12.04 with the help of apt-get some time ago.
Now i tried to upgrade the instance with /apt-get install
xwiki-enterprise-tomcat6-mysql/ .
During the installation i was asked if i want to keep some config-files,
which i did.
But now my browser shows a a 404 :( that he could not find the resource (The
requested resource (/xwiki/) is not available.)
here is a the catalina.out:
/INFO: Server startup in 199 ms
23.09.2013 17:03:12 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
23.09.2013 17:03:13 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
23.09.2013 17:03:13 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
23.09.2013 17:03:14 org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNUNG: Problem with directory [/usr/share/tomcat6/server/classes], exists:
[false], isDirectory: [false], canRead: [false]
23.09.2013 17:03:15 org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNUNG: Problem with directory [/usr/share/tomcat6/server], exists:
[false], isDirectory: [false], canRead: [false]
23.09.2013 17:03:15 org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNUNG: Problem with directory [/usr/share/tomcat6/shared/classes], exists:
[false], isDirectory: [false], canRead: [false]
23.09.2013 17:03:15 org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNUNG: Problem with directory [/usr/share/tomcat6/shared], exists:
[false], isDirectory: [false], canRead: [false]
23.09.2013 17:03:15 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
23.09.2013 17:03:15 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 386 ms
23.09.2013 17:03:15 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
23.09.2013 17:03:15 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.35
23.09.2013 17:03:15 org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ROOT.xml
23.09.2013 17:03:15 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
23.09.2013 17:03:15 org.apache.catalina.startup.Catalina start
INFO: Server startup in 182 ms/
Can you help me?
thanks in advance,
Eric
--
View this message in context: http://xwiki.475771.n2.nabble.com/Upgrade-problem-xwiki-4-4-to-4-1-tp758722…
Sent from the XWiki- Users mailing list archive at Nabble.com.
And hello once more.
It seems I had problems with the HTTP headers. Raising the maximum Size in Apache,
Tomcat and the jk-worker (yes, all three) helped to solve my problem.
This is just an information for the next person that encounters a similar issue.
Thilo
-----Ursprüngliche Nachricht-----
Von: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] Im Auftrag von Schmidt, Thilo (VZ)
Gesendet: Montag, 23. September 2013 10:58
An: 'users(a)xwiki.org'
Betreff: Re: [xwiki-users] AJAX requests don't finish / 401 Error
Hello again.
I had a look at the http headers both sent and received with the tool "LiveHttpHeaders" and found out, that indeed every GET-request is answered with a 401 ("Forbidden"), then resent with an "Authorization" field and answered with a 200 ("OK").
So the problem does not seem to be in my setup and/or Kerberos, but maybe in the xwiki itself?
What can I do to make xwiki show the correct result for AJAX requests?
Thilo
> Hello.
>
> In short: Ajax requests like loading the attachment section, showing
> the user list or autocompleting searches don't work in my wiki. I see
> only the loading bar/circle and nothing else happens.
>
> When watching with Firebug, I realise there are two identical requests
> each, both with "401: Forbidden". The weird thing is, that the
> finished/aborted request got a result, but the wiki doesn't show it.
> The double-request is due to (I think) the Kerberos SSO, since the
> common way to authenticate seems to be to submit a request without
> credentials first, waiting for a
> 401 and then requesting again, this time with credentials.
>
> Fun fact: if i right-click the url in Firebug and choose "open in new
> tab", i get the correct resultset.
>
> A screenshot of the Firebug console can be found here:
> http://i39.tinypic.com/2moxw6v.png
>
> My setup:
> Apache that authenticates via Kerberos (and AD), then transfers to
> tomcat where the user is logged into the xwiki 3.1.4 automatically (this works).
>
> The wiki worked fine when I used NTLM authentication (wich only
> authenticates once per session, not for each HTTP-request)
>
>
> Did anyone encounter similar problems and is able to help me with this?
> Also, feel free to ask if you need more information.
>
>
> Thilo
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users