Fork me on GitHub
Subscribe 2

Ticket #704 (fixed enhancement)

Config

  • Created: 2012-07-10 12:51:45
  • Reported by: Franz
  • Assigned to: Franz
  • Milestone: 2.0-alpha1
  • Component: code
  • Priority: highest

The lack of a replacement for the old $pun_config mechanism is causing quite a few TODOs in the code.

We need to dive into how to best handle configuration. There's a bunch of values in the config table in the database, and they should be easily accessible (and cached, but that could wait, if necessary).

History

Franz 2012-07-10 12:51:54

  • Description changed. (Diff)

AlexCogn 2012-07-10 14:01:02

Can't we simply use Laravel's configuration? It provides us Get and Set methods.

Franz 2012-07-10 14:05:32

No, because the set() is not persistent.

We will use Laravel's config stuff for database access etc.

Franz 2012-07-13 10:54:03

  • Owner set to Franz.

Franz 2012-07-13 21:16:06

Commit d51b4f5 to core master

#704: Add a basic config class with caching.

Franz 2012-07-13 21:23:41

Commit 3b2db0f to core master

#704: Add helper methods to the Config class for checking whether certain options are enabled or disabled.

Franz 2012-07-13 21:24:45

All done, except for saving.

Franz 2012-08-01 21:20:03

Commit 290beb8 to core master

#704: Implement setting and saving config values.

Franz 2012-08-01 21:22:14

Commit 78cb0d2 to core master

Only execute queries if necessary when saving config data.

Related to #704.

Franz 2012-08-01 21:23:32

  • Status changed from open to fixed.

That should be enough.

Franz 2012-08-01 21:23:46

Commit 65846af to core master

#704: Clear the cache when changing config data.