cancel
Showing results for 
Search instead for 
Did you mean: 

Publishing Worked now Doesn't

heislord5
Champ in-the-making
Champ in-the-making
Hi,

I was publishing stuff and it seemed to work.  Now it doesn't.  The only thing I can think that I changed was the title and description of the quick start folders so they would be what I wanted on the site.  I don't think that is the cause, but something isn't working.  I publish but the documents never get moved to the target folders.
18 REPLIES 18

bremmington
Champ on-the-rise
Champ on-the-rise
Sorry, missed the couple of questions you asked.

At the moment it is not possible to adjust the website that is used based on the webapp name. This was an oversight and will be addressed in the next release. For the time being I suggest using host aliases to achieve the required behaviour.

It is possible to adjust the frequency at which the publishing queues are processed. This is set with a property named "wcmqs.publishQueueProcessor.schedule" which can be overridden in alfresco-global.properties. It is a cron-like expression, and its default is to run every minute ("0 0/1 * * * ?"). You can read about this and the other scheduled jobs in the WQS on the wiki.

heislord5
Champ in-the-making
Champ in-the-making
Changing the Title seems to be one of the ways it breaks.  If I change title from "Alfresco Web Quick Start" to whatever I want the title of my site to be (in both folder metadata) publishing stops working.

I also tried to restart and delete work folder, but publishing still doesn't work.  Should changing the site title cause publishing to fail?  Is there a workaround?

heislord5
Champ in-the-making
Champ in-the-making
Thanks for all your replies….good thing I'm up London time today!  One of my coworkers supports our team out of London.

heislord5
Champ in-the-making
Champ in-the-making
OK….so I started over and before initially publishing the site structure, I changed the title.

Then I published the site structure.  The title changed, now it looks like I can publish other things.

So here is my hypothesis.  During the initial publication of the site structure, somewhere the title is saved and is later used to reference things to publish.  When it has changed, causes the publish to fail.  Changing title and republishing structure does not fix it….maybe it doesn't see a change in the site structure so the republish doesn't work?  Or maybe it doesn't change the cached site title on a republish if it already exists?

I think I'm done testing this for today.

Thanks,

Brad

heislord5
Champ in-the-making
Champ in-the-making
BTW,

I figured out how to adjust the website that is used based on webapp.

I copied the wcmqs.war file and named the copy prod.war.

Then I copied that to the webapp folder so tomcat would deploy it.

Then I went to the "Quick Start Live" folder and changed the metadata to "localhost" and "prod"

After that it worked.

Next I'm going to try to copy the "Quick Start Live" folder and "Quick Start Editorial" so I'll have those two plus:

CustomDev
CustomProd

or something like that.  Create two copies of the war file and deploy….change metadata to point to each other.  That should work.

bremmington
Champ on-the-rise
Champ on-the-rise
I've been able to reproduce the problem by following your steps above, so am in a good position now to work out what's going wrong. Thanks again for the detail - I'll come back to you when I've had a chance to investigate further.

heislord5
Champ in-the-making
Champ in-the-making
Thanks….should be helpful to the whole community in using the samples.

bremmington
Champ on-the-rise
Champ on-the-rise
There was a problem with the encoding of the file generated by the transfer service. I have committed a fix onto HEAD.

heislord5
Champ in-the-making
Champ in-the-making
Great…thanks!