Dave,
All seems fine to me w.r.t your setup.
>From the logs you shared, it is clear the HADDOCK.JS fails during
startup. ("e.Findpages" fails)
The result is that all js driven functionality does not get active; you
can view the pages; but not use any of the dynamic styles, ajax searches
etc.
Try compiling with minifications "off" to get more detailed error logging :
mvn clean install -Dmaven.test.skip -Dminimize=false
dirk
On Sat, Jun 27, 2015 at 6:47 AM, Dave Koelmeyer <
[email protected]> wrote:
> Hi Dirk/All
>
> On 27/06/15 00:07, Dave Koelmeyer wrote:
> > Awesome, thanks. I've switched to Haddock full time to test, and I've
> > started opening bug reports with issues I've found:
> >
> > https://issues.apache.org/jira/browse/JSPWIKI-885
> > https://issues.apache.org/jira/browse/JSPWIKI-886
> > https://issues.apache.org/jira/browse/JSPWIKI-887
>
> Before I go much further, I'm wondering if there is some fundamental
> prerequisite I'm missing for using Haddock, based on the number of
> things which aren't working for me. My server set up:
>
> * JSPWiki v2.10.2-svn-17 running in GlassFish v4
> * Container manager authentication is enabled using a file-based realm
> * HTTPS is enabled
> * JSPWiki policy is locked down such that only authenticated users
> have access (both read and write)
>
>
> To enable Haddock, I simply make the required setting in my JSPWiki
> custom properties file, and reboot the application server.
>
> So far, instant search, Slimbox styles, editor live preview, resizing
> the editing interface, and attachment upload are all completely broken
> for me. All work fine simply switching back to Plain Vanilla. Is there
> something I'm missing here at all, or that I haven't taken into account?
>
> Cheers,
> Dave
>
>
