All Apps and Add-ons

root_endpoint support in the FreshMaker

Communicator

Hi @nick,

The iframe in the FreshMaker isn't set up to deal with alternative root_endpoints. Do you think you can fix this?

Cheers,
Alex

0 Karma
1 Solution

SplunkTrust
SplunkTrust

Done. The change will be up in the next Sideview Utils - either 1.3.4, or 1.4 depending on how some other things go.

Either way the fix to the FreshMaker will be up sometime next week. Thanks for letting me know. I'd originally written the FreshMaker just as a personal tool, so it's yet another lesson about moving prototype code to production. 😃

UPDATE: Given how useful the FreshMaker can be, you might want to edit the view yourself to get the fix right away rather than waiting a week. If you do, it's simple - within "refreshentities.xml" find every occurrence of "/debug/refresh" and replace it with "../../debug/refresh". Piece of cake.
And although it goes against best practice, I would edit the file in default, precisely so that it will get clobbered by the official version when you do upgrade later. (ie make the edit within etc/apps/sideview
utils/default/data/ui/views/refresh_entities.xml)

View solution in original post

SplunkTrust
SplunkTrust

Done. The change will be up in the next Sideview Utils - either 1.3.4, or 1.4 depending on how some other things go.

Either way the fix to the FreshMaker will be up sometime next week. Thanks for letting me know. I'd originally written the FreshMaker just as a personal tool, so it's yet another lesson about moving prototype code to production. 😃

UPDATE: Given how useful the FreshMaker can be, you might want to edit the view yourself to get the fix right away rather than waiting a week. If you do, it's simple - within "refreshentities.xml" find every occurrence of "/debug/refresh" and replace it with "../../debug/refresh". Piece of cake.
And although it goes against best practice, I would edit the file in default, precisely so that it will get clobbered by the official version when you do upgrade later. (ie make the edit within etc/apps/sideview
utils/default/data/ui/views/refresh_entities.xml)

View solution in original post

Communicator

Great, thanks a lot for your excellent support!

0 Karma

SplunkTrust
SplunkTrust

I take it back. It was easy. I just got hung up cause if you change root_endpoint and only restart SplunkWeb, evil evil things happen. 😃 It'll be in the next release. Thanks.

0 Karma

SplunkTrust
SplunkTrust

Looking into it now. I have a fix but it's going to be pretty time consuming to implement across the whole app. The root cause is that Splunk's makeurl function, when called from the controller level, or when called from splunk.appserver.mrsparkle.lib.util, ignores rootendpoint completely.... So I have to rework everything to only ever call make_url from the mako templates. So I'm chasing down and testing a lot of little changes. I'll fix it in the next release. Sorry about that.

0 Karma

Communicator

Hi @nick, I've noticed that this is actually an issue on several other pages on Sideview Utils. For example, the Sideview Editor doesn't work at all because of the root_endpoint. Can you take a look?

0 Karma

Communicator

Great, thanks for the quick fix!

0 Karma