recentChanges.jsp not working on ssl based connections about apollo

[cmdcolin]

Thanks for the report. It doesn't look like any of the https versions work on the demo site right now though.

Have you noticed this problem on your own instances?

[childers]

I realized that too, and retracted the initial comment until I had some
more information. I'm really interested to know if it still causes you
trouble on a ssl enabled site.

It isn't working on our site, but I can't rule out that the behavior isn't
caused by something else. I'll update you when I find out more.

Thanks,
Chris

On Mon, Sep 8, 2014 at 2:21 PM, Colin [email protected] wrote:

Thanks for the report. It doesn't look like any of the https versions work
on the demo site right now though.

Have you noticed this problem on your own instances?

—
Reply to this email directly or view it on GitHub
#20 (comment).

[cmdcolin]

This is unrelated to any potential issues that SSL could introduce, but it's important to make sure that each webapollo instance has it's own Annotations directory (they should not be shared between two instances)
Otherwise you will get errors such as sleepycat.je.EnvironmentLockedException

[childers]

Thanks for the reminder. We do keep separate Annotations directories for
each instance. Have other groups been reporting that error?

Chris

On Mon, Sep 8, 2014 at 4:19 PM, Colin [email protected] wrote:

This is unrelated to any potential issues that SSL could introduce, but
it's important to make sure that each webapollo instance has it's own
Annotations directory (they should not be shared between two instances)
Otherwise you will get errors such as
sleepycat.je.EnvironmentLockedException

—
Reply to this email directly or view it on GitHub
#20 (comment).

[nathandunn]

Chris, we have fixed this in the code for the new build. the changes were pretty mild, though so you may want to patch them yourself . . . basically just change the way the google jsapi is added:

15950df

Let me know if that doesn't fix the issue.