Version 0 of wiki page prevents its display.

[Markus Tacker <m@…>]

Some wiki pages (dated 2005-08-02 15:39 and earlier) which have been created with trunk have an initial value of 0 as version. These pages are not displayed in the wiki.

[vivek@…]

I have some older pages from july which have never been updated since they were created, and those do not appear. They all have the highest revision number = 0. Pages which have been updated show up just fine. svn update version of trac from about 15 minutes ago still has this problem.

[anonymous]

This is probably due to [2071].

[anonymous]

workaround:

run sqlite project/db/trac.db then issue these commands:

begin;
update wiki set version=1 where version=0 and name in (select name from wiki group by name having max(version)=0);
commit;

Perhaps the trac-admin upgrade command should/could do this for you?

[anonymous]

This looks to be an issue only for people using the development version after the wiki code refactor and prior to [2071]. I don't think the current trac production release creates wiki pages at version 0. In light of that, I think a small script to correct bad pages would be the best solution.

[Christopher Lenz]

This mess is my fault; not sure how to clean it up… :-P

[Shunichi Goto <gotoh@…>]

Fixup version number of wiki page which starts from version 0

[Shunichi Goto <gotoh@…>]

This problem bother me, too. I made fixup (renumbering) script, attached. Use like this:

  python renumber-wiki-version.py /var/trac/projects/myproj

Note: Do not forget backup before use it.

[Matthew Good]

Yeah, I'd actually written a similar script of my own. This can pretty easily be added to Trac so that it's done by trac-admin upgrade, though I'm debating whether it should go into a new db-version upgrade script, or as a separate IEnvironmentSetupParticipant. It doesn't really seem necessary to create a new DB version, since this may not actually be necessary for some users, although otherwise we'll need to check for any Wiki pages with version 0 every time the evironment is loaded. Perhaps we should have some recommended manner (maybe via the system table) that scripts can keep track that they're only run once.

I'll include the possible patch for the db-version method here since it's short and we can discuss if there's a good way to convert it to an IEnvironmentSetupParticipant.

trac/db_default.py

@@ -18 +18 @@
 from trac.db import Table, Column, Index
 
 # Database version identifier. Used for automatic upgrades.
-db_version = 13
+db_version = 14
 
 def __mkreports(reports):
     """Utility function used to create report data in same syntax as the

trac/upgrades/db14.py

@@ +1 @@
+def do_upgrade(env, ver, cursor):
+    cursor.execute('select name, version from wiki where name in '
+                   '(select name from wiki  where version = 0) order by name,'
+                   ' version desc')
+    cursor.executemany('update wiki set version = version + 1 where name = %s '
+                       'and version = %s',
+                       [tuple(row) for row in cursor.fetchall()])
+

[Christopher Lenz]

Patch applied in [2186].

[Emmanuel Blot]

if you get the following error while executing Shunichi Goto 's script:

Traceback (most recent call last):
  File "renumber-wiki-version.py", line 25, in ?
    cursor.execute('SELECT version FROM wiki WHERE name = %s ORDER BY version DESC', page)
  File "/local/engine/trac/trac/db.py", line 178, in execute
    sql = sql % tuple(['?'] * len(args))
TypeError: not all arguments converted during string formatting

replace line 25 with

cursor.execute('SELECT version FROM wiki WHERE name = %s ORDER BY version DESC', (page,))