IRC Archive for channel #xwiki

abusenius left at 00:17 (Quit: Konversation terminated!
abusenius joined #xwiki at 00:17
npm - (00:42): caleb -- fyi, the way to solve the issue w/ registration page in multiwiki is to enable registration for unregistered users in the root wiki. you have to check/set the registration field for unregistered users in Rights-Management on the root wiki in order to have other virtual wikis registration feature not automatically send you to "login" (2.3.1)
npm - (00:43): ^^^ CalebJamesDeLisl -- do you think this behavior is a bug, or a feature? How would you disable registration on the root wiki, assuming people could get to that wiki?
abusenius left at 01:38 (Ping timeout: 240 seconds
npm - (01:42): ^^^ actually, it's not "enable registration" but rather disabling registration for unreg-users in the root wiki's Rights is what causes other wikis' registration to redirect to login.
spaci joined #xwiki at 01:42
spaci - (01:43): I have a blank xwiki install, and having some trouble getting the standard package of pages in
spaci - (01:44): I get the page for uploading the xar, and I do so, and it looks like it's going to import but I press "import" and get this:
spaci - (01:44): Importing xwiki-enterprise-wiki-2.4-milestone-1.xar: Error while preparing importing
CalebJamesDeLisl - (02:17): npm: Good that you solved the problem. I would say yes it's a bug because the root wiki should be able to be closed for security reasons. You want to report it on jira?
CalebJamesDeLisl - (02:18): spaci: Can you pastebin the log from the console? I think there must be a real stack trace for this.
spaci - (02:19): there's no stack trace in the localhost log, but the catalina log has this line:
spaci - (02:19): Jun 24, 2010 4:54:11 PM org.apache.catalina.users.MemoryUserDatabase save
spaci - (02:19): WARNING: User database is not persistable - no write permissions on directory
spaci - (02:19): i was going to try to track down what directory it's talking about
CalebJamesDeLisl - (02:19): Yes XWiki needs write access in the work directory.
CalebJamesDeLisl - (02:20): You're using the default HSQLDB database?
spaci - (02:20): no, i'm using tomcat6 and postgresql
spaci - (02:20): don't know where the work directory is
spaci - (02:21): oh wait
CalebJamesDeLisl - (02:21): Another postgres user :D
spaci - (02:21): :)
CalebJamesDeLisl - (02:22): Did you add the permissions to the tomcat security manager?
CalebJamesDeLisl - (02:22): http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HInstallandconfigureaServletContainer
spaci - (02:24): right I set TOMCAT6_SECURITY=no
DSpair left at 02:25 (Quit: Leaving
CalebJamesDeLisl - (02:25): Ok. Even with a database you need filesystem access to upload attachments.
spaci - (02:28): well, the xar seems to still be in the system after restarting tomcat
CalebJamesDeLisl - (02:28): In xwiki.cfg file it specifies a couple of directories which the XWiki user has to have write access to.
CalebJamesDeLisl - (02:28): I assume you are running it as a user who has few permissions.
xwikibot joined #xwiki at 02:47
spaci - (02:47): hey thanks :) this is a personal wiki though
spaci - (02:58): well, results seem the same.
spaci - (02:59): some pages seem ok
spaci - (02:59): i'm pretty new to xwiki so i'm uncertain what I should expect it to look like
spaci - (03:00): but the admin page and webpreferences show the "your wiki seems empty" message
spaci - (03:02): oh heck. i think i might have figured it out
spaci - (03:05): yes it seems that there is import/XWiki/XWikiPreferences and admin/XWiki/WebPreferences.
spaci - (03:05): they look the same, but the former works and the latter gives an error
CalebJamesDeLisl - (03:07): Yes. you should be directed to admin/XWiki/XWikiPreferences from the admin button in the upper left.
spaci - (03:09): it gave me an import page before. now it gives me a login page, and past that the Wiki Preferences page
spaci - (03:09): but the import didn't work from admin/XWiki/WebPreferences
spaci - (03:10): anyway, I much appreciate you helping me through that
CalebJamesDeLisl - (03:10): You lose your permissions when the documents are loaded in and you have to login as "Admin" password "admin" (capitalism counts)
spaci - (03:12): was that login active before importing the xar? I thought I tried that
CalebJamesDeLisl - (03:13): Before importing, there are no permissions so guest equals admin.
spaci - (03:37): sweet. i think things look good with this fresh install.
spaci - (03:40): thanks again, and good night
spaci left at 03:40 (Quit: Leaving.
Denis left at 07:01 (Read error: Connection reset by peer
Denis joined #xwiki at 07:09
vmassol joined #xwiki at 08:18
silviar joined #xwiki at 08:59
vmassol left at 09:21 (Quit: Leaving.
florinciu joined #xwiki at 09:23
vmassol joined #xwiki at 09:23
jvelociter joined #xwiki at 09:37
KermitTheFragger joined #xwiki at 09:48
CalebJamesDeLisl - (10:21): Fixed the flickering tests. The problem is the way I fixed them was to put some words into the search box and make sure they don't disappear (indicating a page load)
CalebJamesDeLisl - (10:21): I can't find anything on detecting page loads with webdriver.
vmassol - (10:21): CalebJamesDeLisl: you don't detect page loads I think
vmassol - (10:22): but instead wait on an element in the page
CalebJamesDeLisl - (10:22): Wait for what?
vmassol - (10:22): for whatever you need to be there
CalebJamesDeLisl - (10:22): I want to fail the test if the page loads.
CalebJamesDeLisl - (10:22): So it sounds like it would depend on a wait timeout.
vmassol - (10:23): don't you want to verify that livervalidation has printed statuses?
CalebJamesDeLisl - (10:23): The problem is even if livevalidation fails, the page will load and the server provides the exact same error messages.
CalebJamesDeLisl - (10:24): No javascript = almost exact same experience.
vmassol - (10:25): but it you don't click on submit
vmassol - (10:25): then there will be no new page
CalebJamesDeLisl - (10:25): I can't figure out any other way to relyably trigger liveValidation.
vmassol - (10:25): strange
vmassol - (10:25): focusing the fields should work
vmassol - (10:26): this is what we do manually
vmassol - (10:26): would be interesting to ask on the webdriver mailing list
vmassol - (10:26): (if it doesn't work)
CalebJamesDeLisl - (10:26): When you blur the field, livevalidation will act after some number of milliseconds.
abusenius joined #xwiki at 10:26
vmassol - (10:26): yes
vmassol - (10:26): but we can wait for that
vmassol - (10:27): same as I waited for the "saved" mesasge at the bottom of the screen in save&continue
CalebJamesDeLisl - (10:27): If you are expecting an error message.
vmassol - (10:27): yes but we know what we are expecting, aren't we?
vmassol - (10:27): we control the inputs
CalebJamesDeLisl - (10:27): validateAndRegister doesn't know whether it's being called to try a valid registration or an invalid one.
tmortagne joined #xwiki at 10:28
vmassol - (10:28): then
vmassol - (10:28): we can gather all messages
vmassol - (10:28): and return them
vmassol - (10:28): and let the test do the assert
vmassol - (10:29): we just wait for messages (not for the message content)
CalebJamesDeLisl - (10:29): rewrite test?
lucaa left at 10:29 (Ping timeout: 260 seconds
vmassol - (10:29): if the test requires rewrite sure
vmassol - (10:29): (I don't know it)
CalebJamesDeLisl - (10:31): It's not setup to know whether the registration is expected to succeed or fail.
vmassol1 joined #xwiki at 10:31
vmassol left at 10:32 (Read error: No route to host
CalebJamesDeLisl - (10:37): Ok, I'll pass a parameter to validateAndRegister whether the registration is expected to succeed.
vmassol joined #xwiki at 10:39
vmassol1 left at 10:39 (Read error: Connection reset by peer
vmassol1 joined #xwiki at 10:41
vmassol left at 10:44 (Ping timeout: 240 seconds
lucaa joined #xwiki at 10:52
jvdrean joined #xwiki at 10:54
evalica joined #xwiki at 11:06
vmassol1 - (11:08): guys annotations are broken!
vmassol1 - (11:08): (a functional test might be good btw ;))
vmassol1 - (11:08): lucaa: is that something you can look at?
vmassol1 - (11:08): before the 2.4M2 release ie before a few days ago
vmassol1 - (11:09): ;)
lucaa - (11:09): vmassol1: sure I will investigate
vmassol1 - (11:09): thanks
lucaa - (11:09): but in the future, not in the past
lucaa - (11:09): :)
vmassol1 - (11:09): come on
vmassol1 - (11:09): use your special powers
vmassol1 - (11:10): note to tmortagne: wait for this to be fixed before we release
tmortagne - (11:10): sure, adding it to the releaseplan
vmassol1 - (11:10): note to sergiu: don't take this as an excuse to be even more late...
lucaa - (11:12): mmh, what changed? I was doing an #includeTopic() in a velo macro in a html macro that included a document with some macro definitions, and it started to fail at one point (don't know which).
lucaa - (11:12): Now I replaced that with a big {{include}} on top of my document, outside the velo macro and it all works fine
lucaa - (11:12): anyone has any idea why?
vmassol1 - (11:13): hmm I don't see
vmassol1 - (11:13): maybe thomas has an idea
CalebJamesDeLisl - (11:14): macro cache...
vmassol1 - (11:14): ahah
tmortagne - (11:15): lucaa: includeTopic is supposed to work in a different context, i'm even supprised it did worked for you before
lucaa - (11:15): I love these bugs :)
lucaa - (11:17): ok... is {{include}} supposed to work in a velocity macro?
lucaa - (11:17): because it doens't really work and I don't understand...
CalebJamesDeLisl - (11:17): To velocity, {{include}} is text. it doesn't work until it is printed.
lucaa - (11:18): CalebJamesDeLisl: it's wiki syntax, it should work
lucaa - (11:18): ah right
lucaa - (11:18): I see what you mean
CalebJamesDeLisl - (11:18): I think #includeInContext should work but I didn't review the macro cache change.
CalebJamesDeLisl - (11:20): Great I have Schrodenger's flickering test. It only fails when I test with the browser minimized :/
lucaa - (11:22): tmortagne: what would be the right method to include a document with macros in a page with velocity script?
lucaa - (11:22): preferably only when I need it, i.e. not make an include on top whether I need it or not
tmortagne - (11:22): lucaa: why do you need it to be in the velocity macro ? do you have an if around this include or something ?
lucaa - (11:23): yes, that's the idea
lucaa - (11:23): I mean, I can just put it on top, it doens't do harm
lucaa - (11:23): but it would be suboptimal
tmortagne - (11:23): you have have several velocity macros
lucaa - (11:23): ok
lucaa - (11:23): with an include between them, right?
tmortagne - (11:24): but i think in this case i would just put the include
tmortagne - (11:24): if it only contaisn macros
abusenius - (11:24): CalebJamesDeLisl: thats probably because it focuses some inputs to enter text
tmortagne - (11:24): 1/ that way it's listed when you edit the document
CalebJamesDeLisl - (11:24): Oh focus doesn't work when the browser is miminized?
tmortagne - (11:25): 2/ the source is simpliers and i doubt it's costly
tmortagne - (11:25): listed:listed as include in the right panel
lucaa - (11:25): it was working before as well ;)
lucaa - (11:25): the listing
lucaa - (11:25): maybe it's a bug too ;)
abusenius - (11:25): it doesnt work for me too (focus)
tmortagne - (11:25): because of a ugly search for #include*
tmortagne - (11:26): for backward compatibility
tmortagne - (11:26): it's not a bug but a hack
tmortagne - (11:27): (of course at some point we will try to support include macro inside other macros but it's realy not a priority right now)
lucaa - (11:28): ok, lemme fix that. Max 1h
vmassol joined #xwiki at 11:28
vmassol1 left at 11:29 (Ping timeout: 264 seconds
vmassol1 joined #xwiki at 11:29
vmassol left at 11:32 (Ping timeout: 240 seconds
CalebJamesDeLisl - (11:43): Yup looks like the problem is focus and blur. Can't even blur programmatically with js.
CalebJamesDeLisl - (11:43): So the only solution is submit.
CalebJamesDeLisl - (11:43): Can't detect page load.
vmassol1 - (11:43): CalebJamesDeLisl: you should ask on the webdriver list too IMO
CalebJamesDeLisl - (11:44): I'll send out a message.
vmassol1 - (11:44): http://groups.google.com/group/webdriver
vmassol1 - (11:45): there are lots of messages when you search for focus or blur
vmassol1 - (11:45): "As an aside, Firefox only reliably fires focus events when its window
vmassol1 - (11:45): is the active one. It's possible that may be causing you trouble,
vmassol1 - (11:45): though I doubt it in this case; it's probably webdriver not doing the
vmassol1 - (11:45): Right Thing :)"
vmassol1 - (11:46): but then
vmassol1 - (11:46): "Would you mind trying the newest version? I've patched the Firefox and
vmassol1 - (11:46): IE drivers, so hopefully things will now be better."
vmassol1 - (11:46): http://groups.google.com/group/webdriver/browse_thread/thread/804746eb0696585c/ffa37757d33e2e9b?lnk=gst&q=blur#ffa37757d33e2e9b
CalebJamesDeLisl - (11:46): Hmm. Well if that gets fixed then the current method will work.
vmassol1 - (11:46): we have the new version
vmassol1 - (11:46): I've updtaed to 2.0a4 yesterday
CalebJamesDeLisl - (11:46): I don't see any place to put my address in the mailing list.
vmassol1 - (11:48): CalebJamesDeLisl: btw note that we do force the focus in our seleinum1 tests on hudson
vmassol1 - (11:48): using some shell script
vmassol1 - (11:49): jvdrean is the one who did this so he might have more info
CalebJamesDeLisl - (11:49): I see. focus seems to be forces in selenium2 as well since I have to push the browser off to another workspace to avoid it jumping up at me.
jvdrean - (11:54): vmassol1: iirc the wysiwyg has been modified in such way that forcing the focus is no longer necessary
vmassol1 - (11:54): jvdrean: ah ok cool
jvdrean - (11:54): we should ask mflorea
lucaa - (12:11): guys I need an advice on how to commit these changes in the annos. It would be the only change causing the release of an 1.5, so I would say I need a jira for it
jvdrean left at 12:11 (Quit: Leaving.
lucaa - (12:11): however I cannot reproduce it for neither 2.4M1 or 2.3.1, so I cannot report a bug from a user perspective
lucaa - (12:12): should I just fill in an improvement issue describing the refactor?
tmortagne - (12:12): lucaa: you already committed stuff in annotaion app
lucaa - (12:12): did I?
tmortagne - (12:12): XAANNOTATIONS-23: If there are no annotations, the content of the document should not be replaced with the annotated one
lucaa - (12:12): for M2?
lucaa - (12:12): ah I did
tmortagne - (12:12): after M1 for sire
tmortagne - (12:12): sure
lucaa - (12:12): it was so fast I didn't even remember it :)
lucaa - (12:13): well, I guess I need a jira anyway
lucaa - (12:13): so I'll do a technical jira
lucaa - (12:13): 'though I don't really like it that much
lucaa - (12:18): tmortagne: can you point me to a reference where it says that #includeTopic should not work in {{velocity}} macros which I could refer in my issue?
tmortagne - (12:20): lucaa: i never said #includeTopic does not work in {{velocity}}, #includeTopic is supposed to work in a different context and it's not bahave like in xwiki/1.0 because vmassol1 fixed the fact that xwiki/2.0 velocity code was always executed in the same namespace previously
tmortagne - (12:20): s/not/now/
vmassol1 - (12:21): so in essence you were benefitting from a bug
lucaa - (12:21): yeah I seem to have an affinity for it :)
tmortagne - (12:21): you where doing something that would never work in xwiki/1.0 to be summurize
lucaa - (12:21): can you point me to the issue?
tmortagne - (12:21): s/be//
lucaa - (12:21): xwiki/2.0 I assume
vmassol1 - (12:21): http://code.xwiki.org/xwiki/bin/view/Macros/IncludeTopicMacro
vmassol1 - (12:22): let me find it
lucaa - (12:22): so include topic should have NEVER worked to include macros?
lucaa - (12:22): I mean, by design?
lucaa - (12:23): not in xwiki 1 not in xwiki 2?
lucaa - (12:23): that's what I understand from this page...
tmortagne - (12:23): yes
lucaa - (12:23): :)
vmassol1 - (12:23): http://jira.xwiki.org/jira/browse/XWIKI-5278
lucaa - (12:23): thanks for the info
lucaa - (12:26): I don't really understand how XWIKI-5278 fixed the fact that #includeTopic worked for including macros, but I will trust you
lucaa - (12:26): was it working in xwiki/1.0 as well or only in 2.0 {{velocity}} macros?
lucaa - (12:27): ok, read the history, I got it
lucaa - (12:32): done with the commit, can go ahead with the rel
vmassol1 - (12:32): thxs
vmassol1 - (12:33): there's still the mystery as to why it fails on xwiki.org
lucaa - (12:34): yes, going there now
lucaa - (12:34): link to a page?
CalebJamesDeLisl left at 12:37 (Quit: reconnect
vmassol1 - (12:37): hmmm
vmassol1 - (12:37): I don't see annotations on xwiki.org
vmassol1 - (12:37): maybe I meant myxwiki.org
lucaa - (12:37): :)
CalebJamesDeLisl joined #xwiki at 12:37
lucaa - (12:38): that would make more sense re version, re annotations existance, re annotations interface (will not quite work on toucan :( )
vmassol1 - (12:38): tmortagne: just tried adding an object and it seems ok now
CalebJamesDeLisl left at 12:40 (Client Quit
sdumitriu joined #xwiki at 12:42
vmassol1 - (12:44): lunch time
CalebJamesDeLisl joined #xwiki at 12:47
jvdrean joined #xwiki at 12:50
lucaa - (13:06): vmassol1:  it also works on myxwiki... at least on the incubator
vmassol1 - (13:08): checking my browsing history....
vmassol1 - (13:11): my history suggests xwiki.org
vmassol1 - (13:11): but I don't see how it's possible since there's no annotations menu....
lucaa - (13:11): you pointed me to a local host link after you told me that annos don't work on xwiki org...
vmassol1 - (13:11): anyway let's froget it for me
vmassol1 - (13:11): s/me/now/
lucaa - (13:11): +1
CalebJamesDeLisl - (13:19): Maybe I could register an event handler to squash the submit event so the page isn't loaded.
CalebJamesDeLisl - (13:20): I didn't send mail to the webdriver people because I realize there is no good way to detect a page load without waiting for one and then you have wait timeouts which take a long time.
SvenDowideit left at 13:21 (Ping timeout: 276 seconds
SvenDowideit joined #xwiki at 13:22
CalebJamesDeLisl - (13:26): Asked over on #selenium
vmassol1 - (13:42): tmortagne: are we ready to release?
vmassol1 - (13:43): lucaa: hmm, annotations are failing on the user profile
vmassol1 - (13:43): here's what I did:
vmassol1 - (13:44): 1) selected "Administrator" in "Profile of Administrator" and added an annotation
vmassol1 - (13:44): so far so good
tmortagne - (13:44): vmassol1: apart from the fact that tests are still failing yes
vmassol1 - (13:44): 2) selected "Administrator" under "First Name" and added an annotation
vmassol1 - (13:44): so far so good
vmassol1 - (13:44): 3) selected the "show annotation" check box
vmassol1 - (13:44): boom
lucaa - (13:44): boom?
vmassol1 - (13:44): the annotations are displayed are wrong places
lucaa - (13:44): that's not a boom
vmassol1 - (13:45): s/are wrong/at wrong/
lucaa - (13:45): boom is when you don't see anything on the page :)
vmassol1 - (13:45): it's a boom as in a Steve Job's boom :)
lucaa - (13:45): oh I thought bsod boom
lucaa - (13:45): it's normal, I have a feeling that that page is a big html macro
lucaa - (13:45): in which annos are not working
vmassol1 - (13:45): ok….. still a pb to fix
lucaa - (13:46): because html macro is only supposed to be used in special special exceptionally special cases
lucaa - (13:46): ;)
vmassol1 - (13:46): the annotation module should protect itself
vmassol1 - (13:46): ideally
vmassol1 - (13:46): for ex, refuse to add annotations in an html macro
lucaa - (13:47): well the anno module puts the annotation around the html macro iirc
lucaa - (13:47): so if the html macro is an innocent inline one, it will work fine
lucaa - (13:47): but not otherwise, like in this case
lucaa - (13:47):  Imean in this case it still puts it around but around != fine
lucaa - (13:47): I should parse HTML syntax and mark the annotation right inside
vmassol1 - (13:48): fyi this is what I see: http://tinycoke.com/_6reI9l7LbhPIk/screen_shot_2010-06-25_at_1.47.11_pm.png
lucaa - (13:48): because this thing that html macro is so special and exceptional is just not true
lucaa - (13:48): yes, I see the same
vmassol1 - (13:50): sdumitriu: we have lots of failing tests
vmassol1 - (13:50): related to your change
vmassol1 - (13:51): just tested property delete and it seems ok
vmassol1 - (13:51): sdumitriu: all these are failing because of you object editor change I believe: http://hudson.xwiki.org/view/Functional%20Tests/job/xwiki-product-enterprise-tests/com.xpn.xwiki.products$xwiki-enterprise-test-selenium/996/testReport/
vmassol1 - (13:52): (except possibly 1 or 2)
vmassol1 - (13:53): we need the tests to pass before we can release
vmassol1 - (13:54): Can you please fix them quickly so that we can release?
vmassol1 - (13:54): (they've been failing like this for the past 2-3 days)
CalebJamesDeLisl - (13:57): Well I can stop the flickering test with this:
CalebJamesDeLisl - (13:57): executeScript(
CalebJamesDeLisl - (13:57):       "var div = document.createElement('div');"
CalebJamesDeLisl - (13:57):     + "div.setAttribute('id', 'this-should-not-dissapear');"
CalebJamesDeLisl - (13:57):     + "document.body.appendChild(div);");
tmortagne - (13:58): sdumitriu: would be great if you would put some datas in http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise24M2#HObjectsandclasseseditorimprovements
CalebJamesDeLisl - (13:58): #selenium didn't have much to say about detecting page loads (yet)
sdumitriu - (13:58): K
vmassol1 - (14:01): ah we still have deprecations in the console
vmassol1 - (14:01): 2010-06-25 13:49:37,768 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in @15,68
vmassol1 - (14:01): 2010-06-25 13:49:37,881 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in /templates/editwysiwygnew.vm@25,43
vmassol1 - (14:01): 2010-06-25 13:49:37,883 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in /templates/macros.vm@2341,54
vmassol1 - (14:02): ah yes
vmassol1 - (14:02): I forgot to check the skins
tmortagne - (14:02): the only getSyntaxId i can find in templates is in preview.vm in colibri
vmassol1 - (14:02): yep
vmassol1 - (14:02): fixing
tmortagne - (14:02): editwysiwygnew.vm does not seems to have that
vmassol1 - (14:05): hmm I still get the deprecation
vmassol1 - (14:05): s
tmortagne - (14:05): vmassol1: are you up to date ?
vmassol1 - (14:05): yes
vmassol1 - (14:09): I need to remember how velocity deprecations work
vmassol1 - (14:09): some uberspector
vmassol1 - (14:09): checking
vmassol1 - (14:10): ok it's velocity calls to getMethod which is intercepted
tmortagne - (14:10): yep some unberspector, it's supposed to be thing directly called from velocity
tmortagne - (14:10): so it's either template or pages but i can't find any in template (and skins)
vmassol1 - (14:10): so calls to to XWikiDcoument from velocity will also generate
vmassol1 - (14:10): a deprecation on getSyntaxId
vmassol1 - (14:10): not just on Document
tmortagne - (14:11): any metod called with @Deprecate
vmassol1 - (14:11): but yes you have to call it from velocity
vmassol1 - (14:11): methods calling other methods internally
tmortagne - (14:11): @Deprecated
vmassol1 - (14:11): will not generate deprecations at the velo level
tmortagne - (14:11): yes
vmassol1 - (14:11): so I don't understand
tmortagne - (14:11): where do you go to have the deprecation warning ?
vmassol1 - (14:11): I just start XE
tmortagne - (14:12): on main page ?
vmassol1 - (14:12): then I edit he home page and click on preview, then cancel
vmassol1 - (14:12): yes
vmassol1 - (14:12): then create a new page
vmassol1 - (14:12): and save it
vmassol1 - (14:12): that's all I did
vmassol1 - (14:12): and I got the 3 deprecations metnioned above
tmortagne - (14:12): or preview get me:
tmortagne - (14:12): 2010-06-25 14:12:34,542 [http://127.0.0.1:8080/xwiki/bin/preview/Main/WebHome] WARN  internal.DefaultVelocityEngine  - Deprecated usage of method [com.xpn.xwiki.api.Document.getSyntaxId] in @11,47
tmortagne - (14:12): this one is pretty weird
tmortagne - (14:13): (no resource name)
vmassol1 - (14:13): the template name is not mentioned for a few cases as I recall
vmassol1 - (14:13): "" is used
tmortagne - (14:14): trying to see who is calling it in debug mode then
tmortagne - (14:15): actually this one is the one you just fixed
tmortagne - (14:15): fixing it on my side too
vmassol1 - (14:15): I redeployed the colibri skin locally
vmassol1 - (14:16): ah yes it's different
vmassol1 - (14:16): the ones I have are:
vmassol1 - (14:16): 2010-06-25 14:05:00,034 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in @15,68
vmassol1 - (14:16): 2010-06-25 14:05:00,384 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in /templates/editwysiwygnew.vm@25,43
vmassol1 - (14:16): 2010-06-25 14:05:00,385 [http://localhost:8080/xwiki/bin/edit/Main/NewPage?parent=Main.WebHome&template=&title=NewPage] WARN  internal.DefaultVelocityEngine  - Deprecated usage of getter [com.xpn.xwiki.api.Document.getSyntaxId] in /templates/macros.vm@2341,54
vmassol1 - (14:17): theh'yre generated when you create a new page
tmortagne - (14:17): so just calling preview does not produce any warning for me, trying other use case you listed
tmortagne - (14:18): searching getSyntaxId in pages
vmassol1 - (14:18): ah I didn't search syntaxId
vmassol1 - (14:18): I searched getSyntaxId
vmassol1 - (14:18): researching
tmortagne - (14:19): indeed could be that
vmassol1 - (14:19): yep!
vmassol1 - (14:19): fixing
tmortagne - (14:19): ok
vmassol1 - (14:24): grrr there's still one out there
vmassol1 - (14:24): checking in skins
vmassol1 - (14:25): found 2 more in blogs app
vmassol1 - (14:28): adding the blog?
tmortagne - (14:29): was already there
vmassol1 - (14:29): ok
tmortagne - (14:29): removed "annotation broken"
vmassol1 - (14:29): I can't find the last deprecation
vmassol1 - (14:29): I have only 1 now when creating a new page
tmortagne - (14:31): vmassol1: did you fixed the one in Macros.xml ?
tmortagne - (14:31): it's in target actually
tmortagne - (14:32): (ther eis one in IRC bot btw ;))
vmassol1 - (14:32): I know
vmassol1 - (14:32): fixed
tmortagne - (14:32): i can only find one in RssCode.xml
vmassol1 - (14:32): at least part of it fixed
tmortagne - (14:32): in blog
vmassol1 - (14:32): I haven't fixed the set
vmassol1 - (14:32): gixed too
tmortagne - (14:33): yep seen it
vmassol1 - (14:33): *fixed
tmortagne - (14:33): can't find any other one by search
tmortagne - (14:33): maybe some generated template of something
tmortagne - (14:33): s/template/page/
vmassol1 - (14:35): debugging
tmortagne - (14:35): you fixed edit.vm in colibri ?
tmortagne - (14:35): updating
vmassol1 - (14:36): I don't see any syntaxIf in edit.vm of colibri
tmortagne - (14:36): it's a capital S actually :)
tmortagne - (14:36): doc.SyntaxId
vmassol1 - (14:36): ohhhhh
tmortagne - (14:37): (i did a case-insentive search)
tmortagne - (14:37): i did not know that worked actually (capital first letter)
vmassol1 - (14:37): yeah velocity is kind
vmassol1 - (14:37): that's the only one with capital S?
tmortagne - (14:38): no
tmortagne - (14:38): there is the same in edit.vm in template
tmortagne - (14:39): searching in pages now
tmortagne - (14:40): can't find any in pages
vmassol1 - (14:40): ok page creation is ok now
vmassol1 - (14:40): thanks for the catch :)
vmassol1 - (14:40): should be good now
tmortagne - (14:40): ok
jvdrean - (14:47): vmassol1: about the title problem you've noticed on the user profile, I've reproduced the issue on incubator
jvdrean - (14:47): http://incubator.myxwiki.org/xwiki/bin/view/Test/TestTitleComputation1
jvdrean - (14:48): Doc1 doesn't have a title set, neither do Doc2. Doc2 has a first level heading ('My Title')
jvdrean - (14:59): IIRC the heading from Doc2 should be used as the main title when Doc1 is displayed
lucaa left at 15:12 (Ping timeout: 245 seconds
lucaa joined #xwiki at 15:14