Opened 10 years ago

Closed 8 years ago

#310 closed bug (fixed)

MOD_LOG module is not caring ARCH database

Reported by: jeanyves Owned by: jeanyves
Priority: major Milestone: 0.5.2
Component: BW General Keywords: Logs ModLog
Cc: steinwinde

Description

in the old BW function LogStr?, there was an option to write in the Logs table in a separated ARCH database.

since this separated ARCH table was not active in test, it has been forgotten while moving LogStr? to MOD_log

I am going to restore the option (and will put it online very quicly as soon at it will work, because for now the ModLogs? don't store logs at the proper place in production).

nota : it is an easy fix.

Change History (3)

comment:1 Changed 10 years ago by philipp

  • freq_reported set to 1
  • Milestone changed from 0.1.4 - improving userinterface for members and volunteers and start work on big 0.2 tasks to 0.5.2-short cleanup and framework
  • show_on_bw set to 0

whats the status of this?

comment:2 Changed 8 years ago by fake51

Why is there a need to use ARCH instead of MAIN for logs? I don't see the point in making the setups more complex than needed - I can't see us getting anything extra of out this.

comment:3 Changed 8 years ago by jeanyves

  • Resolution set to fixed
  • Status changed from new to closed

The status is that it is fixed since a while (according to my initial design, logs go in the separate database).

The reason is that I preferred that for rights managment and for backup managment, the whole BW_ARCH database is less critical than the BW_MAIN database. I don't think that it creates problems since the setup is stable. I also allow to have everything in the same database if you want it (this is what I have done on my local environment for exemple and what is done in test).

Note: See TracTickets for help on using tickets.