Demo App config.ini.php helpLink

2 replies [Last post]
Joined: 05/17/2011
Points: 117

I posted this in entirely the wrong forum before... Sorry!

Not sure this is the right forum, but it's the closest I could find to "Demo App in PHP being abused as Production Release"

I couldn't get helpLinks in config.ini.php to work at all with the comments from config.ini.php

I did find that hacking in a headerMenu[] series of statements let me re-define the whole header menu.

Well, except "logout" was locked-in.

headerMenu[] = "type=my_media"
headerMenu[] = "type=my_pl"
headerMenu[] = "type=menu,name=Help,label=Help,items=Users' Guide|/assets/images/help.pdf"
; This is un-documented in Kaltra-provided config.ini.php
; But it fits in with the code-base

Note also that I chopped off the http://DOMAINNAME/ part of the URL, since it will differ in DEV / STAGING / PRODUCTION.

It seems to work fine, but I'm now straying dangerously far down the path of un-documented feature.

Alas, I have no alternative, because the URL I want doesn't even exist in PRODUCTION (yet) much less have current content...

Surely we can't be the only ones who update our Help documentation in sync with the actual application...

Joined: 05/17/2011
Points: 117

In terms of regression...

helpLinks[] in config.ini.php worked in Kaltura svn -r66512

Somewhere between there and svn -r71574, however, a default Kaltura copyrighted documentation is forced into the Help menu, breaking the helpLinks[] configuration settings.

Perhaps allowing the helpLinks[] to augment the forced documentation, or allowing a "Help" entry to replace the default manual with a client-specific manual would be a better solution...

Or even setting "Help" empty and adding our own menu label, which is what my client is really seeking.

Joined: 05/17/2011
Points: 117

I can actually narrow the revision window down to -r71245, as we have sites on that as well, and they have the forced copyrighted Kaltura documentation in Help menu feature.