Creating a theme base on the STK

[mahmoud said]

Guys,

I'm using magnolia 4.1.1 with the STK... I'm trying to create a custom theme module for my website by cloning magnolia-theme-pop  example and modifying it. However I am stuck at the part where the uuids are duplicates (config.modules.standard-templating-kit.config.themes.pop.xml), as described on the wiki. I've change the names properly and the references inside the files. but I'm not sure what should be done to have a different uuid for nodes.

I've tried also copying the pop node under themes in magnolia, exporting it and using it as the configuration file. as suggested on the mailing list earlier. However I see now a lot of  errors in the log of like the following:

javax.jcr.InvalidItemStateException: 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not exist anymore

Any advice on how one can build  this starting from the pop theme example ?






--
Mahmoud Said

[Jan Haderka-2]

Copying the pop theme node is a good start since it will ensure there
are no longer uuid duplicates.
AFAIK there are no internal references within the theme itself so you
should not cet any messages about missing uuids or invalid states.
Maybe providing the full stacktrace with the info on what exact
operation it occured would allow us to help you  better ... if you want
to post the stacktrace, please don't put it in the mail directly, but
rather post it to pastebin.com or similar service and just provide a
link to it. Thx.
Jan

On Wed, 2009-10-14 at 10:05 +0200, Mahmoud Said wrote:

> Guys,
>
> I'm using magnolia 4.1.1 with the STK... I'm trying to create a custom
> theme module for my website by cloning magnolia-theme-pop  example and
> modifying it. However I am stuck at the part where the uuids are
> duplicates
> (config.modules.standard-templating-kit.config.themes.pop.xml), as
> described on the wiki. I've change the names properly and the
> references inside the files. but I'm not sure what should be done to
> have a different uuid for nodes.
>
> I've tried also copying the pop node under themes in magnolia,
> exporting it and using it as the configuration file. as suggested on
> the mailing list earlier. However I see now a lot of  errors in the
> log of like the following:
>
> javax.jcr.InvalidItemStateException:
> 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not exist anymore
>
> Any advice on how one can build  this starting from the pop theme
> example ?
>
>
>
>
>
>
> --
> Mahmoud Said
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[mahmoud said]

Thank you for the quick reply Jan,

It seems things are working well now. here is the exact scenario

Initially:

1. I started magnolia with the STK bundled.
2. I copied the themes/pop true to mytheme
3. I exported the mytheme tree to xml
4. used that exported xml in the mytheme project (when i correctly migrated all references to be mytheme instead of pop)
5. Then i built the new jar and places it in magnolia/WEB-INF/lib/
6. I restarted the tomcat
   

I got a bunch of  those errors I mentioned earlier  http://pastebin.com/m345c844

But now:
I started with a new fresh installation of magnolia with the STK.. I just added mytheme.jar (without manually copying the theme/pop node through the admin interface. and things work like charm.

I'm wondering now where i can find the magnolia templates prototype to be handed to our designer so he can build his CSS on that html prototypes


Thanks a lot

On Wed, Oct 14, 2009 at 10:17 AM, Jan Haderka <jan.haderka@...> wrote:

Copying the pop theme node is a good start since it will ensure there
are no longer uuid duplicates.
AFAIK there are no internal references within the theme itself so you
should not cet any messages about missing uuids or invalid states.
Maybe providing the full stacktrace with the info on what exact
operation it occured would allow us to help you  better ... if you want
to post the stacktrace, please don't put it in the mail directly, but
rather post it to pastebin.com or similar service and just provide a
link to it. Thx.
Jan

On Wed, 2009-10-14 at 10:05 +0200, Mahmoud Said wrote:
> Guys,
>
> I'm using magnolia 4.1.1 with the STK... I'm trying to create a custom
> theme module for my website by cloning magnolia-theme-pop  example and
> modifying it. However I am stuck at the part where the uuids are
> duplicates
> (config.modules.standard-templating-kit.config.themes.pop.xml), as
> described on the wiki. I've change the names properly and the
> references inside the files. but I'm not sure what should be done to
> have a different uuid for nodes.
>
> I've tried also copying the pop node under themes in magnolia,
> exporting it and using it as the configuration file. as suggested on
> the mailing list earlier. However I see now a lot of  errors in the
> log of like the following:
>
> javax.jcr.InvalidItemStateException:
> 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not exist anymore
>
> Any advice on how one can build  this starting from the pop theme
> example ?
>
>
>
>
>
>
> --
> Mahmoud Said
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

--
Mahmoud Said
Software Engineer - eSpace
blog.modsaid.com

[mahmoud said]

Just found them in the bundle code at http://svn.magnolia-cms.com/svn/community/modules/standard-templating-kit/tags/standard-templating-kit-1.1/bundle/src/bundle/prototype

I initially thought they would be in the STK library itself

On Wed, Oct 14, 2009 at 10:33 AM, Mahmoud Said <eng.mahmoud.said@...> wrote:

Thank you for the quick reply Jan,

It seems things are working well now. here is the exact scenario

Initially:

1. I started magnolia with the STK bundled.
2. I copied the themes/pop true to mytheme
3. I exported the mytheme tree to xml
4. used that exported xml in the mytheme project (when i correctly migrated all references to be mytheme instead of pop)
5. Then i built the new jar and places it in magnolia/WEB-INF/lib/
6. I restarted the tomcat
   

I got a bunch of  those errors I mentioned earlier  http://pastebin.com/m345c844

But now:
I started with a new fresh installation of magnolia with the STK.. I just added mytheme.jar (without manually copying the theme/pop node through the admin interface. and things work like charm.

I'm wondering now where i can find the magnolia templates prototype to be handed to our designer so he can build his CSS on that html prototypes


Thanks a lot

On Wed, Oct 14, 2009 at 10:17 AM, Jan Haderka <jan.haderka@...> wrote:

Copying the pop theme node is a good start since it will ensure there
are no longer uuid duplicates.
AFAIK there are no internal references within the theme itself so you
should not cet any messages about missing uuids or invalid states.
Maybe providing the full stacktrace with the info on what exact
operation it occured would allow us to help you  better ... if you want
to post the stacktrace, please don't put it in the mail directly, but
rather post it to pastebin.com or similar service and just provide a
link to it. Thx.
Jan

On Wed, 2009-10-14 at 10:05 +0200, Mahmoud Said wrote:
> Guys,
>
> I'm using magnolia 4.1.1 with the STK... I'm trying to create a custom
> theme module for my website by cloning magnolia-theme-pop  example and
> modifying it. However I am stuck at the part where the uuids are
> duplicates
> (config.modules.standard-templating-kit.config.themes.pop.xml), as
> described on the wiki. I've change the names properly and the
> references inside the files. but I'm not sure what should be done to
> have a different uuid for nodes.
>
> I've tried also copying the pop node under themes in magnolia,
> exporting it and using it as the configuration file. as suggested on
> the mailing list earlier. However I see now a lot of  errors in the
> log of like the following:
>
> javax.jcr.InvalidItemStateException:
> 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not exist anymore
>
> Any advice on how one can build  this starting from the pop theme
> example ?
>
>
>
>
>
>
> --
> Mahmoud Said
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

--
Mahmoud Said
Software Engineer - eSpace
blog.modsaid.com

--
Mahmoud Said
Software Engineer - eSpace
blog.modsaid.com

[Jan Haderka-2]

On Wed, 2009-10-14 at 10:33 +0200, Mahmoud Said wrote:

> Thank you for the quick reply Jan,
>
> It seems things are working well now. here is the exact scenario
>
> Initially:
>      1. I started magnolia with the STK bundled.
>      2. I copied the themes/pop true to mytheme
>      3. I exported the mytheme tree to xml
>      4. used that exported xml in the mytheme project (when i
>         correctly migrated all references to be mytheme instead of
>         pop)
>      5. Then i built the new jar and places it in
>         magnolia/WEB-INF/lib/
>      6. I restarted the tomcat
> I got a bunch of  those errors I mentioned earlier
> http://pastebin.com/m345c844

Hmm, that sounds all right. The stacktrace is unfortunately not as
helpful as I have hoped. It comes from the observation and reloading
module instance on its change ... is it possible you have also removed
the pop theme at the same time? ... maybe few more lines from the log
file above the stacktrace to see which module was being reloaded would
tell me more.

>
> But now:
> I started with a new fresh installation of magnolia with the STK.. I
> just added mytheme.jar (without manually copying the theme/pop node
> through the admin interface. and things work like charm.

Glad to hear that.
>
> I'm wondering now where i can find the magnolia templates prototype to
> be handed to our designer so he can build his CSS on that html
> prototypes

Not sure which version are you looking for, but html prototype is packed
with the STK bundle which you can find for example at [1]. And yes, you
guessed it, version number is part of the URL so you should be easily
able to get the version you need.

[1]
http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-standard-templating-kit-bundle/1.1.2/magnolia-standard-templating-kit-bundle-1.1.2-bundle.zip

HTH,
Jan

>
>
> Thanks a lot
>
>
>
>
> On Wed, Oct 14, 2009 at 10:17 AM, Jan Haderka
> <jan.haderka@...> wrote:
>        
>         Copying the pop theme node is a good start since it will
>         ensure there
>         are no longer uuid duplicates.
>         AFAIK there are no internal references within the theme itself
>         so you
>         should not cet any messages about missing uuids or invalid
>         states.
>         Maybe providing the full stacktrace with the info on what
>         exact
>         operation it occured would allow us to help you  better ... if
>         you want
>         to post the stacktrace, please don't put it in the mail
>         directly, but
>         rather post it to pastebin.com or similar service and just
>         provide a
>         link to it. Thx.
>         Jan
>        
>        
>         On Wed, 2009-10-14 at 10:05 +0200, Mahmoud Said wrote:
>         > Guys,
>         >
>         > I'm using magnolia 4.1.1 with the STK... I'm trying to
>         create a custom
>         > theme module for my website by cloning magnolia-theme-pop
>          example and
>         > modifying it. However I am stuck at the part where the uuids
>         are
>         > duplicates
>         >
>         (config.modules.standard-templating-kit.config.themes.pop.xml), as
>         > described on the wiki. I've change the names properly and
>         the
>         > references inside the files. but I'm not sure what should be
>         done to
>         > have a different uuid for nodes.
>         >
>         > I've tried also copying the pop node under themes in
>         magnolia,
>         > exporting it and using it as the configuration file. as
>         suggested on
>         > the mailing list earlier. However I see now a lot of  errors
>         in the
>         > log of like the following:
>         >
>         > javax.jcr.InvalidItemStateException:
>         > 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not
>         exist anymore
>         >
>         > Any advice on how one can build  this starting from the pop
>         theme
>         > example ?
>         >
>         >
>         >
>         >
>         >
>         >
>         > --
>         > Mahmoud Said
>         >
>         >
>         >
>         >
>        
>        
>        
>         ----------------------------------------------------------------
>         For list details see
>         http://www.magnolia-cms.com/home/community/mailing-lists.html
>         To unsubscribe, E-mail to:
>         <user-list-unsubscribe@...>
>         ----------------------------------------------------------------
>        
>
>
>
> --
> Mahmoud Said
> Software Engineer - eSpace
> blog.modsaid.com
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[mahmoud said]

On Wed, Oct 14, 2009 at 10:42 AM, Jan Haderka <jan.haderka@...> wrote:

On Wed, 2009-10-14 at 10:33 +0200, Mahmoud Said wrote:
> Thank you for the quick reply Jan,
>
> It seems things are working well now. here is the exact scenario
>
> Initially:

>      1. I started magnolia with the STK bundled.
>      2. I copied the themes/pop true to mytheme
>      3. I exported the mytheme tree to xml
>      4. used that exported xml in the mytheme project (when i

>         correctly migrated all references to be mytheme instead of
>         pop)

>      5. Then i built the new jar and places it in
>         magnolia/WEB-INF/lib/
>      6. I restarted the tomcat

> I got a bunch of  those errors I mentioned earlier
> http://pastebin.com/m345c844

Hmm, that sounds all right. The stacktrace is unfortunately not as
helpful as I have hoped. It comes from the observation and reloading
module instance on its change ... is it possible you have also removed
the pop theme at the same time? ... maybe few more lines from the log
file above the stacktrace to see which module was being reloaded would
tell me more.

Actualy I haven't removed the pop module then... I may get back trying to reproduce the case in a while.. i'll let u know


 

>
> But now:
> I started with a new fresh installation of magnolia with the STK.. I
> just added mytheme.jar (without manually copying the theme/pop node
> through the admin interface. and things work like charm.

Glad to hear that.

>
> I'm wondering now where i can find the magnolia templates prototype to
> be handed to our designer so he can build his CSS on that html
> prototypes

Not sure which version are you looking for, but html prototype is packed
with the STK bundle which you can find for example at [1]. And yes, you
guessed it, version number is part of the URL so you should be easily
able to get the version you need.

[1]
http://repo.magnolia-cms.com/m2/info/magnolia/magnolia-standard-templating-kit-bundle/1.1.2/magnolia-standard-templating-kit-bundle-1.1.2-bundle.zip

HTH,
Jan

>
>
> Thanks a lot
>
>
>
>
> On Wed, Oct 14, 2009 at 10:17 AM, Jan Haderka
> <jan.haderka@...> wrote:
>
>         Copying the pop theme node is a good start since it will
>         ensure there
>         are no longer uuid duplicates.
>         AFAIK there are no internal references within the theme itself
>         so you
>         should not cet any messages about missing uuids or invalid
>         states.
>         Maybe providing the full stacktrace with the info on what
>         exact
>         operation it occured would allow us to help you  better ... if
>         you want
>         to post the stacktrace, please don't put it in the mail
>         directly, but
>         rather post it to pastebin.com or similar service and just
>         provide a
>         link to it. Thx.
>         Jan
>
>
>         On Wed, 2009-10-14 at 10:05 +0200, Mahmoud Said wrote:
>         > Guys,
>         >
>         > I'm using magnolia 4.1.1 with the STK... I'm trying to
>         create a custom
>         > theme module for my website by cloning magnolia-theme-pop
>          example and
>         > modifying it. However I am stuck at the part where the uuids
>         are
>         > duplicates
>         >
>         (config.modules.standard-templating-kit.config.themes.pop.xml), as
>         > described on the wiki. I've change the names properly and
>         the
>         > references inside the files. but I'm not sure what should be
>         done to
>         > have a different uuid for nodes.
>         >
>         > I've tried also copying the pop node under themes in
>         magnolia,
>         > exporting it and using it as the configuration file. as
>         suggested on
>         > the mailing list earlier. However I see now a lot of  errors
>         in the
>         > log of like the following:
>         >
>         > javax.jcr.InvalidItemStateException:
>         > 3bd68bfa-8fc9-4c92-8a04-45a25ac720a5: the item does not
>         exist anymore
>         >
>         > Any advice on how one can build  this starting from the pop
>         theme
>         > example ?
>         >
>         >
>         >
>         >
>         >
>         >
>         > --
>         > Mahmoud Said
>         >
>         >
>         >
>         >
>
>
>
>         ----------------------------------------------------------------
>         For list details see
>         http://www.magnolia-cms.com/home/community/mailing-lists.html
>         To unsubscribe, E-mail to:
>         <user-list-unsubscribe@...>
>         ----------------------------------------------------------------
>
>
>
>
> --
> Mahmoud Said
> Software Engineer - eSpace
> blog.modsaid.com
>
>
>
>


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

--
Mahmoud Said
Software Engineer - eSpace
blog.modsaid.com