I am using the XWiki version 7.4.1 with UTF-8 in Xwiki, tomcat8 and
Postgres, but every time than I save a page with accent in the name, XWiki
change the name. For example, I try to save a page with the name "é" and
XWiki save "%25C3%25A9" Please, why this happens?
*My settings in windows:*
*tomcat\conf\server.xml:*
<Connector port="8080" protocol="HTTP/1.1"
URIEncoding="UTF-8"
*xwiki.cfg:*
xwiki.encoding=UTF-8
*PostgreSQL:*
CREATE DATABASE wiki
WITH OWNER = postgres
ENCODING = 'UTF8'
TABLESPACE = pg_default
LC_COLLATE = 'Portuguese_Brazil.1252'
LC_CTYPE = 'Portuguese_Brazil.1252'
CONNECTION LIMIT = -1;
Thanks,
Julio
Hi,
Since May 2015 we added in the Release Plan Help a step that collects the
list of code contributors of a release and lists them in the announcement
mail.
IMO this is a nice way to acknowledge and thank people that are
contributing to XWiki.
I want to propose that we add this contributors list in the Release Notes.
Release Notes are accessible when someone wants to downloads XWiki and they
are also referenced as documentation when we close issues, while the
mailinglist are read just by the people that are subscribed.
This visibility increase will be beneficial to thank participants and also
maybe motivate other users to join the development.
We could have this listing both in the Release Notes and the Announcement
Mail, but I believe it's sufficient in the Release Notes (let me know if
you disagree).
This change would imply:
- Change in the Release Plan to add this step
- Change in the Release Plan Help to document the process
- Change the Release Notes Template to add the Contributors section
The Release Manager would compute the code contributors, but additional
people could add themselves in case they contributed translations or
performed tests (which usually happen after the release, so it's hard to
put this responsibility on the shoulders of the RM). Let me know if you
want the contributions to be exclusive to code contributions. Also having
other types of contributions means that we drop the announcement mail
listing since it could be incomplete.
Let me know what you think.
My +1
Thanks,
Caty
Hello all,
while using the ratings application on an XWiki 6.2.4, we encountered some
bugs related to the storage of ratings in a separate space and with the
update of a user's rating.
We fixed them in these 2 commits:
https://github.com/xwiki-contrib/application-ratings/commit/07758a698d400ed…
and
https://github.com/xwiki-contrib/application-ratings/commit/cd2c190e22f709e…
.
Now, the contrib ratings application was indeed "retired" so we normally
should not use the contrib repo anymore.
However, the work in these 2 commits is about fixing bugs (which might even
be affecting the most recent version of ratings - we need to check that,
didn't check it yet), and I don't see exactly what other option we have in
this case (note that we cannot switch to the "platform ratings" as we're on
XWiki 6.2.4 and ratings are in platform since 6.4.
So, this is what I propose:
* release a 1.3.5 version from the contrib code
- if I understand correctly how extensions.xwiki.org works, this release
will not appear as "most recent" on the application page
- if I understand correctly how maven works, this version will not be
considered more recent than 8.1 even if released after, because of the
version number.
* this means that the version 1.3.5 will be available as an upgrade to the
users that use the contrib extension (v 1.3.4 or lower), will be available
for new install to all users for which the dependencies requirements are
satisfied and will not impact the users which use the platform version of
the ratings app.
Please let me know if I'm wrong in my reasoning.
The advantage of this release would be publishing the bugfix work that
we've done and making it available to all users of the ratings extension on
versions lower than 6.4.
Also, for us the advantage would be not having to deal with a code fork and
manage a release / snapshot of this forked code separately.
Unless somebody -1s this in the very close feature, we will go ahead with
the release.
Thanks,
Anca
P.S. There is a larger discussion to have about how to provide bugfixes on
older versions of platform applications without upgrading all the wiki, but
this should be in another mail or on IRC (e.g. if we discover that indeed
these issues affect ratings app, the platform version, and we make fixes
for these bugs, how can we provide these fixes to an XWiki 6.4 user?)
The XWiki development team is proud to announce the availability of XWiki 7.4.4.
This is a bugfix release that fixes important bugs discovered in the 7.4.3 version.
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/ReleaseNotesXWiki744
The following people have contributed code to this release (sorted alphabetically):
Alexandru Cotiuga
Clemens Robbenhaar
Denis Gervalle
Eduard Moraru
Guillaume Delhumeau
Marius Dumitru Florea
Medjdoub
Pascal Bastien
Thomas Mortagne
Vincent Massol
Thanks for your support
-The XWiki dev team
Hello
A new version of the Nested Pages Migrator Application extension is
available. See
http://extensions.xwiki.org/xwiki/bin/view/Extension/Nested+Pages+Migrator+…
You can install or upgrade with the Extension Manager.
The application is still a beta version that you should use carefully. But
this version brings some important bug fixes.
Enjoy!
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
According to the new decided strategy in
http://markmail.org/search/?q=[xwiki-devs]+[VOTE]+New+Strategy+for+the+XWik…,
third-party extensions can by bundled in XWiki Enterprise. In some cases,
we would need some content from those extension to be available at build
time. Where could we put it?
Taking the Tour Application's example, which It is about to be added in the
dependency management of xwiki-enterprise and inherited in
xwiki-enterprise/xwiki-enterprise-ui/xwiki-enterprise-ui-commons, we could
have the following options:
1) xwiki-enterprise-ui-commons as a space Tours
2) xwiki-enterprise-ui-wiki as a space Tours
3) xwiki-enterprise-ui-mainwiki as a space Tours
4) in a new child module of xwiki-enterprise.ui (looks like "help" keyword
would make sense: xwiki-enterprise-ui-help) which could be used for future
cases
5) in a new child module of xwiki-enterprise-ui having a specific name for
tours.
Could we decide a new rule for this topic?
Thanks,
Alex
Hi,
This thread is about deciding on a future for the Main.Welcome page. This
page was used as the first gadget's content and was intended to be modified
by the users. In 8.2M2 we changed the content of Main.WebHome page to
provide simple wiki text instead of the Dashboard include, deprecating
somehow the purpose of the Welcome page.
Problem: In the 'Navigation' panel the "Welcome to your wiki" is displayed
as a child page of "Home". Users might ask what is the purpose of this page.
We could either:
1. Keep it
1.A and mark it as hidden: in order to not be displayed in the Navigation
tree
1.B and move it to Dashboard: instead of being in the Main space, since now
it's used only there.
1.C and change the text: from a generic 'Welcome' message, to instructions
on how to edit the Dashboard (we would need a separate proposal on the
content + if we want to display other gadgets)
2. Remove it
We could consider that its content is deprecated by the new Main.WebHome
page, so no need for this page. So we could delete the page + remove it
from Dashboard. Dashboard could highlight more advanced gadgets (needing
the separate Dashboard proposal).
Let me know what you think,
Caty
Hei devs,
I intend to integrate the ratings application which is now on xwiki-contrib
into the xwiki-platform.
This in mainly due to 3 points:
-----
1/ give the ability to use ratings in a wiki
2/ using it to provide ratings for the Extension Repository Application
(XWIKI-7780)
3/ display ratings within Extension Manager (XWIKI-11509)
The first point can be accomplished by using the ratings app as is but the
other two imply that the ratings app should be a module that is maintained
by XWiki. It makes sense that if the Extension Repository App and Extension
Manager which are maintained by XWiki depend on the Ratings App, that this
itself is maintained by XWiki as well.
The steps needed for this is as follows:
-----
1/ create a new module in the xwiki-platform core for the ratings
- xwiki-platform-core
-- xwiki-platform-ratings
--- xwiki-platform-ratings-api
--- xwiki-platform-ratings-ui
2/ change the artifact id from "application-ratings" to
"xwiki-platform-ratings"
3/ change the package from "org.xwiki.contrib.ratings" to
"org.xwiki.platform.ratings"
Implications
-----
1/ clone of the existing code is now in xwiki-platform under a different
artifact id (having duplicate code, this takes us to #2)
2/ the code from xwiki-contrib would probably have to be deemed as "retired"
3/ the applications with a dependency to the xwiki-contrib ratings would
have to be upgraded to depend on the module from xwiki-platform
4/ the script service would remain unchanged (changing the artifact id and
package name does not affect the service)
5/ if by any chance someone has code that uses the classes from the ratings
app on contrib, by upgrading, that code will cease to function
Please state you position on this matter.
Links
-----
http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+APIhttp://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+Applicationhttps://github.com/xwiki-contrib/application-ratings
Thank you,
Victor
Hello,
How can I customize the title of a blog?
I need to replace the title; information author, date, etc., which are
below the title for a picture.
I would like to replace this layout:
[image: Imagem inline 1]
for this layout (with image):
[image: Imagem inline 2]
Thank you in advance.
Sincerely,
Julio