infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Kolinko (JIRA)" <>
Subject [jira] [Created] (INFRA-13787) CMS for www.a.o: "Force New www Working Copy" results in stale data (y2012)
Date Thu, 30 Mar 2017 08:08:41 GMT
Konstantin Kolinko created INFRA-13787:

             Summary: CMS for www.a.o: "Force New www Working Copy" results in stale data
                 Key: INFRA-13787
             Project: Infrastructure
          Issue Type: Bug
          Components: CMS
            Reporter: Konstantin Kolinko

I noted this issue while using CMS to edit site.

Steps to reproduce:
1. Go to
2. Click "Force New www Working Copy"

A new fresh working copy, like a fresh svn checkout,
free of local edits and up-to-date.

The data in this working copy is stale.
E.g. the copyright date in the footer of /trunk/templates/skeleton.html  is year 2012.

Workaroung for a user:
Go to /trunk/ directory (one level upper from the default "/trunk/content/" directory) and
use "[Update this directory]" link there.

(A catch for a newbie user is that calling "Update" in the default "content" directory is
not enough - you have to go one level upper.)

Possible fix:
1. Configure a cron job:

It seems that "Force New Working Copy" command works so fast by cloning some canonical working

CMS FAQ mentions that there is a cron job that performs update of working copies daily,

I think that the cron job shall be configured to update that canonical wc daily as well.

2. Amend implementation of "Force New Working Copy" command:
Maybe automatically call "svn update" on created user's wc.
Or at least tell user to do so.

This message was sent by Atlassian JIRA

View raw message