Jump to content

Problem Report: Update Logs

Adam Sternberg

Recommended Posts

I've noticed some strange behavior with the update logs in build when updating content using Sidekick vs. within ComicBase itself.  I have three databases that I maintain and update weekly through Sidekick.  The update logs generated all have the name of the first database in the queue (which happens to be the default ComicBase Database.cbdb) in the log filename.  However, when I update from ComicBase, the log has the name of the database open (in this case, Default ComicBase Database.cbdb) is in the log filename.  The same also is true of the name of the database listed in the log itself.

Either the filename variable isn't populating correctly when generating the log, or the log for the first update operation is getting created multiple times.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...