Hi devs,
So this proposal appeared in some of my proposals but right now I created a
proper Proposal/Idea mail for it.
It's about having an 'Administer Page' section in the menus, similar to the
'Administer Wiki' and 'Administer Space' functionality.
The 'Administer Page' will be accessible to global admins, page creators
and users with (edit?/admin?) rights for the page.
>From what we currently have implemented it should contain the 'Rights
Editor' (?editor=rights) at page level.
In the future we could make 'Presentation', 'Page Elements' or 'Panel
Wizard' to be more granular and be set at Page level (have different panels
and style for just one page).
Some screenshots at
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/PageAdministration
Thanks,
Caty
Hi,
We are using mixed naming when referring to a document/page, not only on
different pages, but also in the same context (Rename step for example).
There is also an issue referring to this problem
XWIKI-5401<http://jira.xwiki.org/jira/browse/XWIKI-5401>and we need to
find an answer in order to move forward consistency.
So the question is which version we prefer: "Page" or "Document" ?
I'm voting +1 for "Page".
"Page" is more used IMO, especially in the "Space"/"Page" context.
"Page" is more general than "Document" and better fitted for a platform that
encapsulates all kind of content (not just documents).
Please cast your vote.
Thanks,
Caty
Hi,
According to the javadoc in XWikiDocument:
/**
* The last user that has changed the document's content (ie not object, attachments). The Content author is only
* changed when the document content changes. Note that Content Author is used to check programming rights on a
* document and this is the reason we need to know the last author who's modified the content since programming
* rights depend on this.
*/
private DocumentReference contentAuthorReference;
This means that objectadd or objectremove actions shouldn't change the content author as they do now.
I'm proposing that we fix this.
Do you see any issue?
Thanks
-Vincent
Hi all,
some time ago we wrote about an idea of having an extensible API for
accessing structured data.
The final goal is to have a uniform API for accessing structured data
both on the client (Javascript+REST) and on the server.
We have written a little design document that I am submitting to the
list for comments:
http://design.xwiki.org/xwiki/bin/view/Proposal/ExtensibleAPIforaccessingst…
This idea is also related to other ones, like providing a way for
dynamically extending the REST API, and also to the integration with
client side frameworks like AngularJS.
Thanks,
Fabio
Hello,
I made a proposal on how we could improve App Within Minutes design.
In order to have an idea about that, you can visit -
http://design.xwiki.org/xwiki/bin/view/Proposal/AppWithinMinutesImprovement…
.
The main purpose of creating this design proposal is to help integrate the
following applications created with App Within Minutes with Flamingo Skin.
What I would like for you to take into consideration is the new layout for
the homepage of newly created applications, since there I proposed a bigger
change.
Thank you,
Gabriela
<http://www.xwiki.com/> *Gabriela Smeria*
*Web Developer *
gabriela.smeria(a)xwiki.com <corina.luong(a)xwiki.com>
tel: +40 742 024 392
skype: smeria.gabriela
Hi devs,
With the upgrade of BouncyCastle to version 1.52 the xwiki-platform-legacy-crypto-script legacy module doesn’t build anymore since BC has removed deprecated code.
We have of course the option to try to fix the legacy code to use newer APIs.
However I think this is overkill and not needed because I don’t believe this legacy code was ever used (Caleb, the author of it, seems to agree with this).
See the comments at http://jira.xwiki.org/browse/XCOMMONS-794
Thus, according to our rules, I’m sending this VOTE to decide to break this API voluntarily by removing this legacy module.
Here’s my +1
Thanks
-Vincent
Hi all,
I work/develop on XWiki 7.0.1-SNAPSHOT. I had some problems with the
Maven builds, as the ${*.version} variables are not replaced in final
WAR, but it is easy solved with shell scripts.
I have upgraded (actually I have tried but have created new deploy
now) from version 6.4.1. In that deploy I have a set of "favourite"
extensions. I had to manually install each and every one on new
deploy. Is there a way to create WAR bundle with all the extensions
and deploy that WAR-with-extensions? Or some other kind of pre-build
set of JAR/XAR files to just drop on Tomcat and run?
How would one start to create such a bundle? With Maven POM magic,
scripting, ... ?
Kind Regards,
--
Miroslav Beranič
MIBESIS
+386(0)40/814-843
miroslav.beranic(a)mibesis.si
http://www.mibesis.si