Problem with using Site Template and Pushing content from Staging

[Andrew O, módosítva 12 év-val korábban]

Specs:
Liferay 6.1 CE GA1
Tomcat 7.0.23 (bundled w/ Liferay)
MySQL 5
Apache 2.2.17
Ubuntu Server

So I have a bunch of site pages saved as .lar files (about 25 pages) that I created. I create a site template and import those saved pages into the template. Whenever I do, I get the following messages in the catalina.out log:

16:19:09,735 ERROR [LayoutImporter:1247] No theme loaders are deployed
16:19:09,949 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 10917 already exists. The new generated ID is 23136
16:19:10,034 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 10932 already exists. The new generated ID is 23147
16:19:10,132 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 10944 already exists. The new generated ID is 23157
16:19:10,247 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 10953 already exists. The new generated ID is 23166
16:19:10,393 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12364 already exists. The new generated ID is 23177
16:19:10,632 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12610 already exists. The new generated ID is 23190
16:19:10,740 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12646 already exists. The new generated ID is 23201
...(There are ~50 article ID warnings per imported page)

Aside from these messages, the imports go fine and I can see the pages great. Now when I create a new site based off of the site template, I get this in the log:

18:25:58,672 WARN  [JournalContentPortletDataHandlerImpl:128] No article id found in preferences of portlet 56

The site then just hangs and eventually throws me a timeout error. However, if I have a site template with only one page, then I can create a new site based off of the template, but still get this is the log:

18:20:34,782 WARN  [JournalContentPortletDataHandlerImpl:128] No article id found in preferences of portlet 56
18:20:42,234 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36779 already exists. The new generated ID is 38619
18:20:42,452 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36791 already exists. The new generated ID is 38630
18:20:42,678 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36801 already exists. The new generated ID is 38640
18:20:43,027 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36811 already exists. The new generated ID is 38649
18:20:43,278 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36823 already exists. The new generated ID is 38660
18:20:44,348 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 36836 already exists. The new generated ID is 38673
...

The new site then works with the one-page template. A similar issue occurs when I try to publish a site from staging. If I try to publish an entire site all at once, I get a timeout error after about 10 minutes. But if I publish one page at a time, it works but I get this in my Remote Live Log:

15:33:48,416 ERROR [LayoutImporter:1247] No theme loaders are deployed
15:33:49,693 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12492 already exists. The new generated ID is 11945
15:33:50,490 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12513 already exists. The new generated ID is 11956
15:33:50,900 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12152 already exists. The new generated ID is 11967
15:33:51,305 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12176 already exists. The new generated ID is 11978
15:33:51,670 WARN  [JournalPortletDataHandlerImpl:761] An article with the ID 12187 already exists. The new generated ID is 11989
...

I put this all together in one post because it seems to be all related to the database somehow. Anyone know what is going on and how to solve it? It seems terribly inefficient to have to do everything one page at a time, or to only be able to have a site template of size 1.

[Vincenzo Todisco, módosítva 12 év-val korábban]

I have the same problem: site template and staging features are very good approach, but it shall make confortable using it that the DB is not made dirty.