07:52 <ocdtrekkie__> I have fond memories of that page, funwhilelost. :D

08:02 <kentonv> funwhilelost: https://sandstorm.io/apps redirects -- /apps/index was never directly linked anywhere except secretly by people who explicitly wanted to get back to the old app list. :)

13:44 <Guest95550> Help needed. I am fairly new at Wordpress. I have WP running on Oasis. I installed a contact form plugin. I tested sending email from the plugin and got the following error message: object(PHPMailer)... ["ErrorInfo"]=>"Could not instantiate mail function". In the docs here: https://docs.sandstorm.io/en/latest/administering/email/#outgoing-smtp, it

13:44 <Guest95550> says: "To enable this feature, you must configure an SMTP relay in the Email configuration page of the Admin panel." However, when I look at my "admin panel" in Oasis, I don't see anything to do with configuring SMTP. Any help would be much appreciated.

14:17 <dwrensha> Guest95550: Sorry, the Sandstorm WordPress app does not yet have the ability to send email

14:18 <dwrensha> https://github.com/dwrensha/wordpress-sandstorm/issues/12

14:18 <Guest95550> ok thanks for letting me know

14:20 <Guest95550> do you have any suggestions as to a workaround? like perhaps using mailgun instead?

14:22 <dwrensha> what are you trying to accomplish?

15:15 <DanC> "So far, I've been hesitant to hook this up until we have proper powerbox support" is a refrain I see more and more often. I don't suppose you're interested to publish a roadmap of milestones?

15:15 <DanC> that quote is from Apr https://github.com/dwrensha/wordpress-sandstorm/issues/12#issuecomment-214502467

15:16 <DanC> the docs speak of it in the present tense "To that end, Sandstorm implements other kinds of powerbox flows for different occasions."

15:17 <DanC> I think I'd be willing to contribute again for access to a roadmap.

15:18 <DanC> though I suppose the sorts of funding that would make a difference are significantly larger than such a contribution.

15:35 <DanC> a blog item with an update on stretch goals from https://sandstorm.io/news/2015-01-15-sandstorm-1.3M-seed-round-pay-it-forward would be nifty

15:37 <DanC> actually, what I'd rather do is have either a label or a milestone for each of the stretch goals and have issues that represent sort of 80% of a plan for each of them

15:37 <DanC> I'd be happy to interview somebody and build the issues

15:37 <DanC> maybe what I'm after is already there...

17:55 <asheesh> In other news, mnutt_ and I are trying to figure out why LibreOffice isn't starting in a grain, but is starting in the vagrant-spk VM.

17:57 <dwrensha> would `spk dev --proc` help debugging that?

17:57 <asheesh> Ooh, interesting idea; we might do that.

17:57 <asheesh> I'm no longer sure /proc is related fwiw

17:57 <dwrensha> I think you need to rebuild sandstorm to get that to work now

17:58 <dwrensha> I'm wondering if I should prioritize implementing that flag as a `spk dev` feature

20:13 <asheesh> dwrensha: No, at least not yet. I'm going to see what's going on with libreoffice, but strace doesn't suggest that /proc is the problem.

20:13 <asheesh> (anymore)

20:13 <asheesh> (now that we have a few files in /proc )

20:14 <jemc> DanC: I, for one, only idle in this channel so I can see when the powerbox is ready to use :P

20:14 <DanC> heh

20:14 <jemc> I'm not super interested in building things for sandstorm until then

20:15 <DanC> is there any particular way that it's not ready to use yet?

20:15 <asheesh> mnutt_ was also grilling me about this today over lunch : )

20:15 <asheesh> Some powerbox flows work; some don't. The ones that don't aren't ready to use. (-:

20:16 <asheesh> https://docs.sandstorm.io/en/latest/developing/powerbox/ hints that requesting an IpNetwork works, which it does indeed.

20:16 <asheesh> It's a little visually ugly, but there's nothing wrong with it that I know.

20:16 <jemc> DanC: I, like you, had trouble figuring out the true status of the feature

20:16 <asheesh> Another thing that can be done is the thing the Collections app does.

20:17 <asheesh> I'm +1 on me (or someone) writing up what does/doesn't work on e.g. https://docs.sandstorm.io/en/latest/developing/powerbox/

20:17 <asheesh> What doesn't work currently is grains exporting arbitrary objects to each other. Another thing that doesn't work is connecting grains to each other's HTTP API endpoints.

20:17 <asheesh> mnutt_ wants that second one; I do too, in fact!

20:17 <DanC> jemc, did you see https://github.com/sandstorm-io/sandstorm/issues/2450 Powerbox stretch goal ?

20:18 <asheesh> Sorry that the state of things is a bit misleading. DanC, thanks for requesting more clarity on it.

20:18 <mnutt_> yeah, really looking forward to the second one

20:20 <asheesh> An interesting difficulty is that it's been basically second on our collective todo list for ages, and keeps getting bumped. For example, the new focus on "productivity suite" lately means more polishing existing APIs and the most commonly-used apps rather than enabling the long tail of goodness that powerbox enables.

20:22 <asheesh> But we haven't, like, published a roadmap of what is required for other powerbox features.

20:38 <asheesh> jemc: What kinds of powerbox application(s) are you interested in building, btw?

20:38 <asheesh> mnutt_: We never tried "upgrade libreoffice to libreoffice from jessie-backports" so I'm going to try that first.

20:38 <asheesh> I did also write my LD_PRELOAD to get a stacktrace on exit().

20:39 <asheesh> Hopefully I don't have to use it!

21:06 <mnutt_> asheesh: ohh, interesting. I believed that unoconv only worked on libreoffice 4.x but I see its CI passing on 5.x

21:11 <asheesh> Also it doesn't help. |:

22:11 <mnutt_> asheesh: I came to the same conclusion. New stack traces, but same exit(77)

22:12 <mnutt_> I guess it's time for that LD_PRELOAD?

22:41 <gwillen> I am excited that Quick Survey appears to have improved since I last tried it!

22:42 <gwillen> As I recall it used to require you to hit 'save' after adding a question, and now it appears to not do this.

22:42 <gwillen> Also I am pretty sure the results table used to be a lot less readable because I think I remember complaining about it.

22:42 <gwillen> So yay!

22:47 <gwillen> ooh, writing out all the options and then changing between 'radio' and 'checkbox' wipes them. I don't think google surveys do that.

23:31 <simonv3> gwillen: that’s good to hear. thanks for the feedback!

23:32 <simonv3> also, that last thing you mentioned is an oversight on my part. that should probably be fixed. Can you file a bug? https://github.com/simonv3/quick-survey/issues/

23:32 <simonv3> I’ve got some more UI changes in the works as well. Actually just needs to be wrapped up and packaged.

23:43 <simonv3> oh, just saw that you already had. Sorry!

23:48 <gwillen> simonv3: haha, np!

23:48 <gwillen> I filed it right after I mentioned it here

23:48 <gwillen> because I realized that was more useful ;-)

23:56 <simonv3> I’m much more likely to see it there :)