Even though the custom name space is being reported as loaded by Tomcat, check a few lines below in the Catalina.out log for.
15:38:41.719 [localhost-startStop-1] INFO o.a.g.extension.ExtensionModule - Extension "Theming Extension" loaded. If you're using mysql and/or LDAP authentication extensions, it should appear in the line below. If not, there may be some clues about possible syntax errors in your .json files in the catalina.out. I was able to discover most of my issues when branding our login page without having to turn on debug logging, but as Mike mentioned, this may prove helpful if you can't find anything useful in the tomcat logs. Erik Berndt / Systems Administrator 5551 Wellington Rd, Gainesville, VA 20155 703.631.0004 x520 (Phone) / 703.257.1725 (Fax) http://www.superiorpaving.net Need to open an IT support ticket? http://FixIT.superiorpaving.net/portal or [email protected] On Mon, Sep 18, 2017 at 2:22 PM, dan <[email protected]> wrote: > ok, here is what I've got, can't figure out why it isn't applying: > > in guac-manifest.json > { > "guacamoleVersion" : "*", > "name" : "xyz", > "namespace" : "xyz", > > "translations" : [ > "translations/en.json" > ] > } > > in translations/en.json > > { > "APP" : { > "NAME" : "XYZ APP", > } > } > > in the root where guac-manifest.json is located. > zip -r xyz.jar * > > move that to > /usr/share/tomcat8/.guacamole/extensions/ > which is linked to > /etc/guacamole > > reload tomcat > INFO o.a.g.extension.ExtensionModule - Extension "xyz" loaded. > > but no change to the app name. > > what am I missing? > > > On Mon, Sep 18, 2017 at 11:33 AM, Mike Jumper <[email protected]> > wrote: > > On Mon, Sep 18, 2017 at 8:32 AM, dan <[email protected]> wrote: > >> > >> how do I find the real guac home directory? I have a > >> /etc/guacamole/extensions, I dropped a file in that is basically > >> cut'n'paste from the example, zipped it up with 'zip -r > >> customtheme.jar *' and reloaded tomcat. no changes. > >> > > > > For all current releases of Guacamole, /etc/guacamole will not be used > > unless you have taken explicit steps to override the default search > > locations for GUACAMOLE_HOME. This has changed recently, but that change > is > > not yet in a release: > > > > https://issues.apache.org/jira/browse/GUACAMOLE-335 > > > > The default search locations, in order of priority, are defined in the > > manual: > > > > http://guacamole.incubator.apache.org/doc/gug/ > configuring-guacamole.html#guacamole-home > > > > The easiest option is to simply create a ".guacamole" directory within > the > > home directory of the tomcat user. Which user that actually is will > depend > > on how you've installed Tomcat, but assuming you installed Tomcat via > your > > distribution's packages, there will likely be a user defined specifically > > for that service, and the home directory will be visible within > /etc/passwd. > > > > Once you believe you have your extension in the right location, be sure > to > > check the Tomcat logs if things still aren't working. Guacamole will log > its > > attempts to load extensions, including any failures due to the extension > not > > following the correct format. If those messages don't provide enough > > information, you can also enable debug-level logging: > > > > http://guacamole.incubator.apache.org/doc/gug/ > configuring-guacamole.html#webapp-logging > > > > - Mike > > >
