Hi Jayson,
Sorry for the late reply - looong weekend :)
Answers inline:
On May 20, 2009, at 10:06 PM, Jayson wrote:
Thanks Grégory, I really appreciate your help. Comments and questions
below.
On Wed, 2009-05-20 at 17:02 +0200, Grégory Joseph wrote:
I also saw this in the log before the DB issue...
*
* Magnolia needs module updates or installs, point your browser to
your
Magnolia instance and confirm ! *
*
... is it a clue to what is wrong? does that mean the bundle is
incomplete?
Not at all; there's an install "wizard" that you need to go through
when first installing, or when updating.
Is there an installer for the Community Edition bundle with tomcat?
No - this is a different thing: the first time you start and access
Magnolia through a web browser, it still needs to setup a "few" things
(bootstrapping configuration in the repository, ...) before you can
actually use it.
On the "Installing Magnolia" page
(http://documentation.magnolia-cms.com/administration/installation.html#InstallingastandaloneMagnoliadistribution
)
there is talk of an Enterprise Edition installer but under the heading
Installing the Community Edition it says "The procedure is exactly the
same as for the Enterprise Edition; unfortunately, we don't provide an
installer for the Community Edition at this time."
All I did was extract the files into my home directory and start
tomcat.
(Well I had to learn about setting JAVA_HOME - fortunately the script
was very clear about what was needed)
That's all you should have to do; and tbh, that's all the Enterprise
Edition installer does - the only difference being that it lets you
graphically select where to install it, and lets you select a JDK
instead of having you have set the JAVA_HOME (which can be useful on
some systems indeed)
What should I do to run the bundle? I can easily delete it and extract
the files again; is that what I should do?
That's the safest if you want to be totally sure you're starting with
a clean instance ;)
Isn't the whole point of the bundle that it is configured and ready to
run? What else do I need to do after extracting the files?
It is, you shouldn't have to do anything else than what you did. Go to
"http://localhost:8080"; using your web browser.
Out of curiosity, why did you go for 3.6.5, while Magnolia 4.0.1 has
been released for a while ?
(amongst lots of other things, it bundles a newer version of
Jackrabbit, which might help with your derby issues)
It was above 4.0.1 in the download list. It looked like it was the
latest bundle posted - so I hoped any kinks would have been worked
out!
I clicked "Download Magnolia Community Edition" on the Downloads page
(http://www.magnolia-cms.com/home/downloads.html) and that took me to
the sourceforge page
(http://sourceforge.net/project/showfiles.php?group_id=86297&package_id=89560
)
Magnolia CE 3.6.5 is listed first and expanded.
Right... we've noticed that, damn sourceforge always puts the latest
release on top - we indeed released the 3.6.5 bugfix version after
4.0.1, but really, new users should use 4.0.1 ;)
------
If any one is interested here is the trail I followed to get this far
(it ain't pretty) ...
<...>
Yikes! Indeed. We are aware of this... thanks so much for the
constructive and complete feedback!
Now to be honest, I lost track of what your original issue. Please try
with a completely clean installation (by re-extracting the bundle like
you suggested) and let us know how it goes !
Cheers,
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
