Hi Doug, Thanks for this feedback.
More in your mail On 09/22/2010 10:15 PM, douglas.hur...@mail.cuny.edu wrote:
> > IMO, change > > - src="kupublank.html" > > to > > - src="modules/kupu/resources/kupu/common/kupublank.html" > > in file > > - /src/modules/kupu/resources/kupu/apache-lenya/kupu/kupumacros.html This fixes the kupublank.html not found error. :-) But lead to another error after I made the above change: org.apache.lenya.cms.site.usecases.ChangeLabel.getNodesToLock() throws NullPointerException because AbstractUsecase.java.getDocument() returns null. A simple check for the document being NULL fixes the problem, so that ChangeLabel.getNodesToLock() returns an empty arraylist if getDocument() == null. Everything seems to work now, without errors being thrown in the logs. My question is: is it safe to modify org.apache.lenya.cms.site.usecases.ChangeLabel.getNodesToLock() in this way? I'm not very familiar with Lenya 2, so I hope someone more knowledgable than I can determine if it's a safe change. It seems to me that anything that extends documentusecase as usecases.ChangeLabel does, should in fact have a document associated with it. Or is it perhaps better to fix the individual usecase for Kupu which I haven't looked at yet.
Yep, I am not the knowledgable on editor you looking for, but it's seems also to me that patch the changelabel is not a way to do in this case : - this usecase seems to work with others editors... so problem seems to come from kupu...
Can you describe what you want to do ? Create a document, modify existing one, ...
Hope we solve it soon ! ++
I can provide a patch for both changes if you think it's a safe change. Cheers, -doug florent andré <florent.andre-...@4sengines.com> wrote on 09/22/2010 08:19:16 AM: > Hi Doug, > > Thanks for your patch, applied on the 2_0_X branch (removed from the > 2_0_3 because it's was already released). > > The 2.0.x is ok on the publish bug. > > Do you have more invest on this kupu error ? > > regards. > > On 09/16/2010 03:12 PM, florent andré wrote: > > Thanks to look at it, patch very welcome. Ask questions if needed. > > > > About the kupu, I invest a little bit and found this : > > > > $ find . -name kupublank.html -print | grep -v build > > $ ./src/modules/kupu/resources/kupu/common/kupublank.html > > > > here is the kupublank.html (error is left for kupublank.xml cause of > > Lenya processing) > > > > > > $ rgrep kupublank . | grep -v .svn | grep -v build > > > > $ ./src/modules/kupu/resources/kupu/default/drawers.kupu: > > id="kupu-linkdrawer-preview" src="kupublank.html"> > > > > $ ./src/modules/kupu/resources/kupu/apache-lenya/kupu/kupumacros.html: > > <iframe frameborder="1" scrolling="auto" width="440" height="198" > > id="kupu-linkdrawer-preview" src="kupublank.html"> > > > > $ ./src/modules/kupu/resources/kupu/common/kupudrawers/drawer.xsl: > > src="kupublank.html" scrolling="off" frameborder="0" width="0px" > > height="0px" display="None"> > > > > IMO, change > > - src="kupublank.html" > > to > > - src="modules/kupu/resources/kupu/common/kupublank.html" > > in file > > - /src/modules/kupu/resources/kupu/apache-lenya/kupu/kupumacros.html > > may solve this. > > > > Let's editor killers says if it's the best way to proceed. > > > > Can you try it and send some feedback ? > > > > Thanks. > > Have a good day > > > > On 09/16/2010 01:14 PM, douglas.hur...@mail.cuny.edu wrote: > >> > >> Yes, that's exactly what I see. > >> > >> A direct publish doesn't seem to cause any problems, even with > >> "notification" checkbox checked. > >> > >> However, Submit a modified document, and as a second step Publish a > >> document with notification checked, gives the error you described. > >> > >> I'm looking into it today. Maybe I'll be able to find something to help > >> fix it. > >> > >> -doug > >> > >> florent andré <florent.andre-...@4sengines.com> wrote on 09/16/2010 > >> 06:04:57 AM: > >> > >> > Hi Douglas, > >> > > >> > Thanks for this report. > >> > > >> > I just have a try to a "fresh" 2.0.3 on ubuntu with open-jdk-6 > >> > > >> > When I directly publish, it's work > >> > When I commit then publish : commit work well, but publish says on form > >> > "Exception during commit or rollback: null (see logfiles for details)" > >> > ... but in fact, page is publish. > >> > Have to invest more on this. > >> > > >> > > >> > No more much time right now, will try kupu this afternoon. > >> > > >> > Cheers > >> > > >> > > >> > On 09/15/2010 05:21 PM, douglas.hur...@mail.cuny.edu wrote: > >> > > > >> > > Hi all, > >> > > > >> > > Maybe someone can shed some light on what might be common errors > >> thrown > >> > > by a fresh build of a fresh checkout of Lenya 2.0.3. > >> > > > >> > > System: > >> > > OS X 10.5 > >> > > JDK 1.5 > >> > > JbossAS 5.1.0 > >> > > > >> > > In general, the build works, I can log in and import the default > >> content > >> > > to the default publication. However, when publishing and selecting > >> the > >> > > options for notification, I get the following error: > >> > > > >> > > Caused by: org.mozilla.javascript.WrappedException: Wrapped > >> > > java.lang.IllegalStateException: No transition found for event > >> > > [checkPreconditions] in state [execChecked]! > >> > > (file:///Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/ > >> > > < > >> < <file:////Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/>file:////Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/ > >file:////Volumes/Sun/Installed/jboss_deploy/lenya.war/lenya/modules/> > >> > >> > > usecase/usecases.js#254) > >> > > > >> > > and also: > >> > > > >> > > 2010-09-15 10:33:55,469 [ajp-192.168.1.2-8009-2] ERROR > >> usecases.workflow > >> > > - Could not commit/rollback usecase [workflow.submit]: > >> > > java.lang.NullPointerException > >> > > > >> > > > >> > > I'm also getting a persistent Kupu error: > >> > > > >> > > 2010-09-15 10:33:43,527 [ajp-192.168.1.2-8009-3] ERROR > >> > > sitemap.handled-errors - Unable to get transformer handler for > >> > > cocoon://lenya-page/default/authoring/kupublank.xml > >> > > > >> > > Kupublank doesn't seem to exist. > >> > > > >> > > I've checked permissions and Jboss is able to write to write and read > >> > > the entire install base. > >> > > > >> > > Without using notification I can edit/publish as expected. > >> > > > >> > > Thanks for any light you can shed on why this would happen to a clean > >> > > checkout and build. > >> > > > >> > > -doug > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org > >> > For additional commands, e-mail: user-h...@lenya.apache.org > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org > > For additional commands, e-mail: user-h...@lenya.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org > For additional commands, e-mail: user-h...@lenya.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org For additional commands, e-mail: user-h...@lenya.apache.org
