# Loading our SiteSetting properties before plugin loads

**URL:** <https://meta.discourse.org/t/loading-our-sitesetting-properties-before-plugin-loads/45572>\
**Category:** Development\
**Created:** [11. Juni 2016 um 19:09 UTC](https://meta.discourse.org/t/loading-our-sitesetting-properties-before-plugin-loads/45572 "2016-06-11T19:09:02Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![def](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/def/32/120841_2.png) [@def](https://meta.discourse.org/u/def)\
**Post date:** [8. Juli 2016 um 21:33 UTC](https://meta.discourse.org/t/loading-our-sitesetting-properties-before-plugin-loads/45572/16 "2016-07-08T21:33:32Z")

</div>

Thanks for bringing more attention to this topic @cpradio and thank you for taking a look into this as well @tgxworld, I’ve fixed my plugin now by using a lambda. I made it work with the OmniAuth 1.0 strategy I depend on by modifying it slightly so that it `.call`s the lambda, and hey presto - the reference to the site setting is preserved.

---

_[View the full topic](https://meta.discourse.org/t/loading-our-sitesetting-properties-before-plugin-loads/45572)._