Drupal administration integration

[DanielMM]

Allow the change of configuration options like opening hours, ban secret code, etc.

There are two sets of opening hours, one for each type of chat. The 1-to-1 chat has a regular schedule, all week days for a few hours. The group chat is going to take place on a session based that is made public beforehand with a few days.

Updated 22.06.2012 by @DanielMM

As each type of chat has a different schedule, we need to have two separate ways to manage them. I was thinking that it could be done in the administration(configuration) area under the WebServices > Opeka chat system, to have two textareas that will allow the input of the schedule for each type of chat.

As these values are stored in the database, we can retrieve them in a block and place them where we need.

The issue is more on how can we then output that data in snippet.html.

[mikl]

@DanielMM I can't quite remember how we decided to handle the opening hours. Was it content from the main Cyberhus site that we embed in the page, or which was it.

As I understand the requirements, the ban code was supposed to be a single-use random code generated when needed, so we were planning to handle this in Node by adding another dialog the admins can call up to generate these.

[DanielMM]

@mikl The opening hours can be fetched from cyberhus.dk as there will be a page that will output using variable_get a string save in the database from a section in the admin configuration. It can be a simple textarea.

We need two on them so they can be changed independently.

[mikl]

@DanielMM it's not quite clear what needs to be done with this ticket. The ban code administration is handled in issue #5. Should this perhaps be updated to cover the opening hours, with a bit more information on how we are to implement it?

[cfdp]

See https://github.com/cfdp/opeka/issues/53