Hi,
I installed Xwiki-Entreprise-Web8.0 stable using the .jar in a Tomcat server.
I just installed the extension LDAP Admin Application.
The xwiki seem to work perfectly except for LDAP Admin Application.
I configure dit but I noticied that there is no changes write in the xwiki.cfg file.
I checked the perms and they are set to tomcat :tomcat... chmod 744
Why ?
Sébastien
Hi,
I want to modify document content while user is saving a document, for
example: [[PageA]] will be replaced by [[PageA.WebHome]]. I want to write a
component extension to do that. Which component should I look into?
Thanks,
Wei
--
View this message in context: http://xwiki.475771.n2.nabble.com/Document-save-hook-to-modify-content-tp75…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
I have a working xwiki 7.1.4 installation. It uses MySQL + file system
datastore and LDAP as an authentication backend.
I'm trying - so far unsuccessfully - to upgrade it to more recent version.
I've
tried 7.4.3 and 8.0 but in both cases I end up with broken UI - the search
bar at the top is missing - http://www.bankfotek.pl/image/1995162, the
right hand 'drawer' menu has much has only Log-in/Log out buttons:
http://www.bankfotek.pl/image/1995161 . In contrast this is how 7.1.4 looks
like: http://www.bankfotek.pl/image/1995168
The steps I'm taking during the upgrade process:
* i move the old instance of the xwiki into another folder
* there are no files left by the old instance
* i download and unzip xwiki-enterprise-jetty-hsqldb-7.4.3.zip or
xwiki-enterprise-jetty-hsqldb-8.0.zip
* i copy webapps/xwiki/WEB-INF/lib/mysql-connector-java from the
old xwiki installation
* i also copy the whole data/storage from the old instance
* i modify the webapps/xwiki/WEB-INF hibernate.cfg.xml coming from
7.4.3 or 8.0 and comment out there the definition of
<property
name="connection.url">jdbc:hsqldb:file:${environment.permanentDirectory}/database/xwiki_db;shutdown=true</property>
<property name="connection.username">sa</property>
<property name="connection.password"></property>
<property name="connection.driver_class">org.hsqldb.jdbcDriver</property>
<property name="dialect">org.hibernate.dialect.HSQLDialect</property> -->
and replace it with own connection string to local mysql
in the xwiki.cfg taken from 7.4.3 or 8.0 i add:
xwiki.store.attachment.hint=file
xwiki.store.attachment.versioning.hint=file
xwiki.store.attachment.recyclebin.hint=file
xwiki.authentication.authclass=com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl
xwiki.authentication.ldap=1
Then I start the new xwiki using:
./start_xwiki.sh -p 8090 -ld /tmp/
When I visit the newly installed wiki [also after logging in] - there's no
Distribution
Wizard - just a familiar front page of our wiki.
I've tried triggering the Distribution Wizard by
removing data/jobs/status/distribution/status.xml
and restarting the xwiki but it did not help.
I'd greatly appreciate any suggestions that can help me with bringing 8.0
to fully usable state.
--
regards,
Pawel Kudzia
--
regards,
Pawel Kudzia
Let's say I have a page hirearchy like this:
- A
- - B
- - C
and page B contains an image. When I export page A with children, the page B
in the resulting PDF does not contain the image.
The url parameters used to perform the export are
?format=pdf&pagebreaks=1&attachments=1&includelinks=0&includechilds=6
The image is specified as an attachment of page B, and added into the page
using [[image:activation.png]].
>From the tomcat log, I see that the image URL cannot be found.
https://BASE_URL/bin/download/SPACENAME/WebHome/activation.png,
where BASE_URL is my site domain and SPACE_NAME is the name of the space.
Is this a known issue? WHat do you suggest I do to get the image exported in
the PDF as well?
Thank you,
--
View this message in context: http://xwiki.475771.n2.nabble.com/PDF-Page-Export-with-children-does-not-co…
Sent from the XWiki- Users mailing list archive at Nabble.com.
The XWiki development team is proud to announce the availability of XWiki
8.1 Release Candidate 1.
This release candidate brings a couple of improvements and bugfixes to
Extension Manager and other bundled components.
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/ReleaseNotesXWiki81RC1
The following people have contributed code to this release (sorted
alphabetically):
Alexandru Cotiuga
Clemens Robbenhaar
Denis Gervalle
Ecaterina Moraru (Valica)
Guillaume Delhumeau
Thomas Mortagne
Thanks for your support
-The XWiki dev team
Hi,
i use the macro "code" to highlight code blocks in the text. On export
(e.g. as pdf) only the text is colored and has another font, but there
is no border or background color, like in the web view. The text before
and after the code block is also not quite nice styled. It is indented
wich is not good for reading.
How can i change the style of the code blok and surrounding text in the
exported document?
With best regards
Alina
--
-----------------------------------
SOURCEPARK GmbH
B.Sc. Alina Kupgisch
Partner der Allianz für Cyber-Sicherheit
des Bundesamtes für Sicherheit in der
Informationstechnik (BSI)
Hohenzollerndamm 150, Gebaeude 7
14199 Berlin
Tel: +49 (0)30/398 068 30
Fax: +49 (0)30/398 068 39
e-mail: alina.kupgisch(a)sourcepark.de
WWW: www.sourcepark.de
-----------------------------------
SOURCEPARK GmbH
Sitz der Gesellschaft: Berlin
Handelsregister: Amtsgericht Berlin-Charlottenburg, HRB 80254
Geschäftsführer: Matthias Barmeier, Harald Dürr
-----------------------------------
Wichtiger Hinweis: Die vorgenannten Angaben werden jeder
E-Mail automatisch hinzugefügt und lassen keine Rückschlüsse
auf den Rechtscharakter der E-Mail zu.
Diese E-Mail kann vertrauliche und/oder rechtlich geschützte
Informationen enthalten. Wenn Sie nicht der richtige Adressat
sind oder diese E-Mail irrtümlich erhalten haben, informieren
Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser E-Mail ist nicht gestattet.
Hi all,
my next request is regarding to let xwiki initialize a new, empty SQL Server database to use the xwiki with this empty database. The problem is that the table activitystream_events seems to be created twice:
com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'activitystream_events' in the database.
Has somebody an idea of how I can solve that issue? There are some interesting logs that looks like access problems with the database, but if there are problems accessing the database it might not be possible to create any table, isn't it?
So here is the tomcat log, maybe it is helpful to solve the issue.
Kind regards,
Sebastian.
Hibernate: select this_.XWV_VERSION as XWV1_26_0_ from xwikidbversion this_
Hibernate: select count(*) as y0_ from xwikidoc this_
2016-05-04 15:19:37,334 [http://pippin:8080/xwiki2/bin/view/Main/] INFO .HibernateDataMigrationManager - Checking Hibernate mapping and updating schema if needed for wiki [xwiki]
2016-05-04 15:19:37,570 [http://pippin:8080/xwiki2/bin/view/Main/] ERROR .HibernateDataMigrationManager - The empty database xwiki seems to be not writable, please check your configuration!
com.xpn.xwiki.store.migration.DataMigrationException: Unable to update schema of wiki [xwiki]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.updateSchema(HibernateDataMigrationManager.java:182) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.initializeEmptyDB(HibernateDataMigrationManager.java:142) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.initNewDB(AbstractDataMigrationManager.java:445) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.initializeCurrentDatabase(AbstractDataMigrationManager.java:550) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.checkDatabase(AbstractDataMigrationManager.java:533) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.setDatabase(XWikiHibernateBaseStore.java:734) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:911) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:843) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:856) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiCacheStore.loadXWikiDoc(XWikiCacheStore.java:299) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:1634) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:1680) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
Caused by: org.hibernate.HibernateException: Failed updating schema while executing query [create table activitystream_events (ase_eventid varchar(48) not null, ase_requestid varchar(48) null, ase_stream varchar(255) null, ase_date datetime null, ase_priority int null, ase_type varchar(255) null, ase_application varchar(255) null, ase_user varchar(255) null, ase_wiki varchar(255) null, ase_space varchar(255) null, ase_page varchar(255) null, ase_hidden tinyint null, ase_url varchar(2000) null, ase_title varchar(2000) null, ase_body varchar(2000) null, ase_version varchar(30) null, ase_param1 varchar(2000) null, ase_param2 varchar(2000) null, ase_param3 varchar(2000) null, ase_param4 varchar(2000) null, ase_param5 varchar(2000) null, primary key (ase_eventid))]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.updateSchema(XWikiHibernateBaseStore.java:625) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.updateSchema(XWikiHibernateBaseStore.java:371) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.hibernateShemaUpdate(HibernateDataMigrationManager.java:198) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.updateSchema(HibernateDataMigrationManager.java:179) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
... 77 common frames omitted
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'activitystream_events' in the database.
2016-05-04 15:19:37,570 [http://pippin:8080/xwiki2/bin/view/Main/] ERROR PreferencesConfigurationSource - Failed to access configuration property
com.xpn.xwiki.XWikiException: Error number 3202 in 3: Exception while reading document [xwiki:XWiki.XWikiPreferences]
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:989) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiCacheStore.loadXWikiDoc(XWikiCacheStore.java:299) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:1634) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.XWiki.getDocument(XWiki.java:1680) [xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at org.xwiki.configuration.internal.AbstractXWikiPreferencesConfigurationSource.getBaseObject(AbstractXWikiPreferencesConfigurationSource.java:86) ~[xwiki-platform-configuration-default-7.4.2.jar:na]
at org.xwiki.configuration.internal.AbstractXWikiPreferencesConfigurationSource.getBaseProperty(AbstractXWikiPreferencesConfigurationSource.java:139) ~[xwiki-platform-configuration-default-7.4.2.jar:na]
at org.xwiki.configuration.internal.AbstractXWikiPreferencesConfigurationSource.getBaseProperty(AbstractXWikiPreferencesConfigurationSource.java:156) ~[xwiki-platform-configuration-default-7.4.2.jar:na]
at org.xwiki.configuration.internal.AbstractDocumentConfigurationSource.getPropertyValue(AbstractDocumentConfigurationSource.java:315) [xwiki-platform-configuration-default-7.4.2.jar:na]
Caused by: com.xpn.xwiki.XWikiException: Error number 3301 in 3: Exception while switching to database xwiki
at com.xpn.xwiki.store.XWikiHibernateBaseStore.setDatabase(XWikiHibernateBaseStore.java:738) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:911) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.beginTransaction(XWikiHibernateBaseStore.java:843) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateStore.loadXWikiDoc(XWikiHibernateStore.java:856) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
... 69 common frames omitted
Caused by: com.xpn.xwiki.store.migration.DataMigrationException: The empty database xwiki seems to be not writable, please check your configuration!
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.initializeCurrentDatabase(AbstractDataMigrationManager.java:556) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.checkDatabase(AbstractDataMigrationManager.java:533) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.XWikiHibernateBaseStore.setDatabase(XWikiHibernateBaseStore.java:734) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
... 72 common frames omitted
Caused by: com.xpn.xwiki.store.migration.DataMigrationException: Unable to update schema of wiki [xwiki]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.updateSchema(HibernateDataMigrationManager.java:182) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.hibernate.HibernateDataMigrationManager.initializeEmptyDB(HibernateDataMigrationManager.java:142) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.initNewDB(AbstractDataMigrationManager.java:445) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
at com.xpn.xwiki.store.migration.AbstractDataMigrationManager.initializeCurrentDatabase(AbstractDataMigrationManager.java:550) ~[xwiki-platform-legacy-oldcore-7.4.2.jar:na]
... 74 common frames omitted
Dear List,
After a Debian Upgrade from Wheezy to Jessie, my XWiki 7.2 was also
upgraded. But during the upgrade process, it seems there were some
conflicts I did not really bother as the system told me it could manage
them (Maybe I was a bit naive at this point ...).
After the upgrade process finished, I landed on my XWiki with all the pages
filled with "Failed to execute the [velocity] macro. Click on this message
for details."
Even the Admin user cannot access admin pages due to the error. I tried to
dig in the database to find if I could resolve the problem but I did not
succeed.
Do you have any pointer on how to solve the issue?
Thanks for all!
Best Regards,
Frédéric
Hi, again.
How can I correct date format (to include leading zeros) in faq application? I suppose, that changing the default language of my wiki to 'pl' has broken the format and now 'Creation date' in list of faq entries looks like '2016-04-15 09:6:34' .
TIA,
R.
Hello:
I installed XWiki 8.0 in tomcat 9 under windows 2008; The menu bar is
missing!! I thought this was the new layout of the screen, but I looked up
some screenshots, and apparently there is supposed to be a menu bar right
next to the xwiki logo, with "home" "add" "space" "page" items just like in
6.0. Why is it not showing in my installation? I tried both chrome and ie.
Dan
--
View this message in context: http://xwiki.475771.n2.nabble.com/Missing-menu-bar-tp7599328.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi!
A few days ago I summited this as a bug http://jira.xwiki.org/browse/XRENDERING-448. I would like to thank Vincent for the quick response on it, but am a little surprised by the response and the change from "Bug" into "New Feature" request, because to me this feels like a bug in syntax precedence, where syntax tokens have a higher order of operations than the {{ }} macro syntax tokens when it should be the other way around: The macro should have higher precedence in the syntax tree and get evaluated before being used as a source for the image tag. In my opinion that would provide the most flexible and dynamic behavior for Xwiki users.
Can someone on this email list share more information on the rationale behind this design decision?
Thanks
Regards,
Francisco Peredo
Dear all,
thanks for your help regarding to my question about ACE related javascript errors when editing xwiki articles a few days ago. As we figured out it is likely not an issue regarding tot he xwiki system and come in from a particular addon. Due to the fact, that is is not easily trackable for us which addon is working wrong, we want to setup a second xwiki instance with a new database and without extentions. This is only to ensure the errors weg et is not related to xwiki and to get a closer view to the issue.
We tried simply to run a second xwiki using apache tomcat using an webapp directory called "xwiki2" with a xwiki 7.4.2 WAR-Distribution and the default (empty) HSQL Database. But this seems not to work due to the following issue. Could someone help me with fixing that issue?
Kind Regards,
Sebastian.
Here is what the error is about:
HTTP Status 500 - Failed to locate an ExtendedURL Resource Type Resolver component
type Exception report
message Failed to locate an ExtendedURL Resource Type Resolver component
description The server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Failed to locate an ExtendedURL Resource Type Resolver component
org.xwiki.resource.servlet.RoutingFilter.getResourceTypeResolver(RoutingFilter.java:181)
org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:103)
[...]
org.xwiki.cache.CacheException: Failed to get cache factory for role hint [infinispan]
org.xwiki.cache.internal.DefaultCacheManager.createNewCache(DefaultCacheManager.java:109)
org.xwiki.cache.internal.DefaultCacheManager.createNewCache(DefaultCacheManager.java:85)
org.xwiki.wiki.internal.manager.WikiDescriptorCache.createCache(WikiDescriptorCache.java:67)
org.xwiki.wiki.internal.manager.WikiDescriptorCache.initialize(WikiDescriptorCache.java:58)
org.xwiki.component.embed.InitializableLifecycleHandler.handle(InitializableLifecycleHandler.java:39)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:322)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190)
org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363)
org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424)
org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392)
org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:184)
org.xwiki.resource.servlet.RoutingFilter.getResourceTypeResolver(RoutingFilter.java:177)
org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:103)
Hi everyone,
I’d like to give everyone some heads up about the plan I discussed with Marius (who’s working on the new CKEditor integration) regarding the new CKEditor-based WYSIWYG.
Goals:
======
* Replace the current GWT-based WYSIWYG editor with one based on CKEditor, see http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration
* Keep it as an extension so that it can be installed using the Extension Manager on XWiki versions 7.4.x. We need to introduce some UIXP to be able to replace the existing editor in the XWiki menus so we’ll need to commit that in 7.4.x (with x >= 2).
* Make it possible to install the extension on XWiki versions 6.2.5+. However the installation will have some manual parts, to replace the GWT-based editor.
Timeline:
=========
* Before the 19th of Feb, a new version of the CKEditor integration will be released containing wiki page/attachment linking and image insertion features. At that point what will remain is:
** Support for editing macros
** Office importer (if needed)
** Configuration UI in the administration
** Add UIXP to integrate the CKEditor nicely into the platform (using extension points)
** Future: Add support for packaging CKEditor plugins as XWiki Extension.
* The goal is to implement all these remaining features around when 8.1M1 is released (i.e. early April 2016), except maybe the Future part which could be done later on.
* Starting 8.1M2, the goal would be to bundle the Extension in the distribution (default flavor) but to not make it the default yet. There would be some configuration option to select which WYSIWYG editor to use (GTW-based or CKEditor-based).
* Starting 8.2, if all goes alright, we would set the CKEditor WYSIWYG to be the default (still with ability for admins to configure the editor they wish to use so they can continue to use the GWT-based one if they want that).
* Starting 9.0, the idea would be to remove the GWT-editor and retire it to XWiki Contrib with instructions for advanced developers to build it and use it in XWiki should they still want to do that. However we won’t spend extra time to refactor it as an extension since that would spend too much time which we prefer to spend on improving the new WYSIWYG editor.
WDYT?
Thanks
-Vincent
PS: cc-ing the users list to let the XWiki users know about the plan ahead of time!
Hello again.
I don´t have really much knowledge in Velocity. So right now begging for help :D
#set($users = $xwiki.rightsmanager.usersApi.allUsers)
#foreach($user in $users)
I am getting an array of objects(user in xwiki). $users-array should be sorted by familyname
Here is the snippet from
https://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/g…
I am still kinda confused how to apply this on mine
Single Property Sort
#foreach($obj in $sorter.sort($objects, "name"))
$obj.name Ordinal= $obj.ordinal
#end
End
Thank you, guys =)
Hi,
I run the Wiki http://tutos.myxwiki.org on the community farm and search crashed
with "Solr query require programming right" error ... does someone can save the
required pages with the correct rights ? or better solution can give me
"programming rights"?
Regards,
Hi,
On 5 Jan 2016 at 10:09:27, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)) wrote:
> Sorry for reply so later, I have taken a vacation for days.
Hope you had some nice holidays! :)
> Actually, I modified Dashboard.WebHome after upgrade, and use {{spaces}} macro which comes from 7.3 release.
> Now I replace {{spaces}} with {{documentTree}}, but I have some little problem.
> 1. I want to avoid "xxx more", but limit=100 do not work.
> 2. I want to limit the tree level, but I have no idea.
All documentation for the tree macro can be found at
http://extensions.xwiki.org/xwiki/bin/view/Extension/Document+Tree+Macro
AFAIK there’s currently no way to configure how many items to display before “xxx more” appears. @Marius: is that correct? It seems it would be useful to have this in the future if that’s the case. WDYT? Do we have a jira issue about it already?
I’m not sure what’s your use case for point 2. I guess you mean limit the hierarchy but it seems it would prevent users from navigating correctly so I’m not sure what’s the use case.
Thanks
-Vincent
> 发件人: Vincent Massol 代表 "vincent@massol.net(mailto:vincent@massol.net)"
> 日期: 2015年12月23日 星期三 下午7:35
> 至: KirbY ZhoU , XWiki Users
> 主题: Re: [xwiki-users] How to avoid nested space?
>
> Hi,
>
> The default dashboard is located in Dashboard.WebHome. When you upgraded you should have had the Distribution Wizard upgrade that page. Was that the case? Could you check the history for that page?
>
> Now two things could have happened:
>
> 1) you overwrote the changes brought by the Distribution Wizard by importing old versions of pages from your previous wiki. If you’ve done that then you’ve most likely broken the upgrade process since you’ve removed all the upgrades that were required to all default wiki pages! :) See http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade for the canonical way of upgrading an XWiki instance. If you’ve done that I suggest that you redo the upgrade.
>
> 2) you have modified Dashboard.WebHome. If this is the case then you’ll need to update your version to use the {{documentTree}} macro instead of the spaces macro.
>
> As I’ve mentioned already in my reply the notion of Spaces have been removed from the UI (I’ve linked you to some page with the explanation, have you been able to read that page? was it clear? should we improve things there with more explanations?).
>
> Thanks
> Hope it helps,
> -Vincent
>
>
>
> On 23 Dec 2015 at 12:19:45, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)) wrote:
>
> > I belived that I have use the space widget version 7.3.
> > I created a new Xwiki-7.3, and then import the old spaces one by one, excluding 'Main', 'XWiki' and all spaces coming with Xwiki default pages.
> >
> > I just want to get a simple space list.
> >
> >
> >
> > 发件人: Vincent Massol 代表 "vincent@massol.net(mailto:vincent@massol.net)"
> > 日期: 2015年12月23日 星期三 上午4:41
> > 至: XWiki Users
> > 抄送: KirbY ZhoU
> > 主题: Re: [xwiki-users] How to avoid nested space?
> >
> > Hi KirbY,
> > On 22 Dec 2015 at 21:27:47, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)(mailto:kirbyzhou@gmail.com)) wrote:
> >
> > > How to avoid nested space?
> > >
> > > Since the new nested space feature, a lot of nested space such as "XXX.YYY" appears in the "Space List" in my home page.
> > > If I want to create a sub page, a new nested space created silently. It becomes more and more, and bothers our users.
> > >
> > > I want keep the original simple one level space and documents tree model instead of the new nested space model. How can I get it?
> >
> > The issue is that you haven’t upgraded your home page (the dashboard I presume). We have replaced the Space widget with a Documents widget. Normally, when you have upgrade you should have had the Distribution Wizard kicking in and updating the default wiki pages. Please let us know what you’ve done when the Distribution Wizard has executed.
> >
> > The notion of Spaces has been removed starting with XWiki 7.2+
> >
> > Please see http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization
> >
> > The introduction of Nested Spaces is a large change and we wish to make it as seamless as possible to our users. Please let us know any issue you see and we’ll try to help you and see if we can improve things by default so that other users have less problems upgrading.
> >
> > Thanks for your help and patience.
> > -Vincent
> >
Hello:
I am using XWiki 6.0, and App Within Minutes. I have created several apps
that work fine. I can already customize the view and edit sheets and things
like that. But I don't like that AWM forces the home page to be called
{space} 'Home'. I'd like to change the behavior. There is an object of class
AppWithinMinutes.LiveTableClass which apparently is the hook for AWM to
display the home page. But I can't see in the LiveTableViewSheet where on
earth the space name is set! Where is the word 'Home' coming from? I tried
changing the Translations page (it contains the word 'Home') but that
doesn't fix it!!
Help!
Dan
ps.: I wanted to add a field to the LiveTableClass to hold the name of the
app. not sure if that would break anything.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Changing-the-app-name-in-App-Within-Minut…
Sent from the XWiki- Users mailing list archive at Nabble.com.
the default title should be "$doc.web - $doc.name"
I hope cover one page title (as blog main page) ,I know that Space
Preferences make a different title for each space,but I just want to cover a
page title
I try to use velocity code In the blog.Webhome as:
{{velocity}}
$doc.setTitle("My new title")
{{/velocity}}
it's not working
Is there any other way to cover a page title without modifying the database?
--
View this message in context: http://xwiki.475771.n2.nabble.com/how-to-cover-one-page-title-tp7599271.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Using a simple XWiki 7.4.2 system I'm having problems getting Export and
then Import to work. I'm want to export the entire contents of one Wiki
and import it into another one.
I think I'm following the instructions here correctly:
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ImportExport
The Export seem to go OK and generates a xar file.
But when I try to Import that into a different 7.4.2 wiki (or even the
one it was exported from) I get told that "No package is available for
import".
Tim
Hi all,
I have doubts about how permissions are inherited in XWiki v7.4. Does
this statement from your documentation still apply for this version?
/"*Note on permission inheritance*//
//When a permission is explicitly set for a given group or user at a
certain scope (page, space or wiki) then other groups and users must
also have the right explicitly set as well, at this scope or a scope
upstream.//
//For example, when you decide to explicitly allow the view right for
"GroupA" on a given space, users that are not members of "GroupA" must
have the view right explicitly set either on the given space or on the
whole wiki to be able to view the space as well."/
I expose my problem:
GroupA with edit rights at Wiki level.
GroupB with view rights at Wiki level.
I grant GroupB edit permissions on a certain page => GroupA is no longer
able to edit this page (neither its children) until I specifically grant
them edit rights (again, as at Wiki level they have them). This
contradicts previous statement.
Could you please clarify? Thanks in advance!
--
ASOL Email Un cordial saludo,
Iago Lluque
/
*Alínea Software Solutions S.L.*
Travesía del Comercio 3, 2º 36002 Pontevedra España
Tel: +34 986 845 699
Email: info(a)alineasol.com <mailto:info@alineasol.com>
Web: http://www.alineasol.com
/
Hi,
I would like to gather your ideas about how we could simplify the Homepage
of XWiki Enterprise.
- Maybe is something that doesn't make sense to have on it?
- Maybe is something that is missing?
Thanks,
Caty
Interaction Designer on behalf of XWiki Development Team