[11:22] <sakrecoer> eylul, krytarik: got a repsonse from RT regarding the plug in.
[11:23] <eylul> oh?
[11:23] <eylul> result?
[11:23] <eylul> *goes to check*
[11:23] <sakrecoer> RT: "I am not confident that this plugin will play nicely with our read-only security model for Wordpress themes. "
[11:23] <sakrecoer> RT: "Can you come up with a list of read-write resources it would need access to?  If it's just the database, we're probably fine, but I worry it needs access to the filesystem in ways we deliberately prevent"
[11:24] <sakrecoer> eylul: https://rt.ubuntu.com/Ticket/Display.html?id=29028
[11:28] <eylul> I *think* it only touches the database (the pages are saved on the database in some compressed format). as in it doesn't create new files? the only part I have doubts about is the template creation (which we do not use, because it is buggy anyway) I am not entirely sure through. as in it doesn't touch the theme at all. 
[11:32] <eylul> sakrecoer: what I can do is to try to ftp into the stage to see if there are any files created by the plugin. I know it doesn't touch the theme. Not sure if it creates its own files somewhere through. I doubt it does but.. 
[11:39] <eylul> ok if this thing is modifying anything the filesystem I am not seeing it. krytarik might have more ideas on this.
[11:58] <sakrecoer> eylul: ok, i think we need a straight answer..
[11:58] <sakrecoer> krytarik seemed to be meaning we might not need that plugin anymore...
[11:58] <sakrecoer> not sure how or why, but today i leanred of another plugin by him, that we seem to use
[11:59] <sakrecoer> Simple Custom CSS plugin
[12:00] <sakrecoer> so, if we don't find a straight answer about what live-thing~plugin needs access to, i will tell RT to disregard it while i mention the simple-css-sthing-plugin
[12:10] <eylul> yes, we were discussing that we should probably have both plugins available
[12:10] <eylul> if possible
[12:11] <eylul> but my argument is that handcoding everything should be the last resort, and we should aim to maintain a min hassle website that doesn't require people to know css hacks to do a content update. 
[12:14] <sakrecoer> oh i agree, but it seems such a sollution also need to copmly with RT's rules...
[12:14] <sakrecoer> *comply
[12:16] <eylul> sakrecoer: that goes without saying. I am fairly certain it doesn't touch anything but the database through. 
[12:16] <eylul> I wish I knew exactly what parts they keep as read only. I could recreate the setup somewhere and ensure the plugin works
=== JLye is now known as JtLively
=== eylul- is now known as eylul