Fell Off Turnip Truck

[Randy Smith]

I obviously don't get it.

I unpacked the program into the root. It's in a bugLog directory.

Displays are all screwed up.  The rs.assetsPath is set to /buglog/hq/ and when I re-set it to just /hq, everything looks so much better.

In test, Server works fine but Client does not.

I have this loaded on my test server, but don't understand how I can call this one install from local or production and identify which system they came from.

Did I forget to hold my tongue just right when I unpacked it, or is there some magic install program I missed seeing?

[Randy Smith]

When I run test/client, I get this:

The web site you are accessing has experienced an unexpected error.
Please contact the website administrator. 

The following information is meant for the website developer for debugging purposes.

Error Occurred While Processing Request

404 Not Found   The error occurred in D:/inetpub/wwwroot/bugLog/client/bugLogService.cfc: line 199 197 : <cfhttpparam type="body" value="#serializeJson(data)#"> 198 : <cfelse> 199 : <cfloop list="#structKeyList(data)#" index="key"> 200 : <cfif !isNull(data[key])> 201 : <cfhttpparam type="formfield" name="#key#" value="#data[key]#">

[Randy Smith]

All the links include bugLog, for some reason, and double up a forward slash:

<title>BugLogHQ :: Dashboard</title>
	<link rel="stylesheet" href="/bugLog/hq//includes/bootstrap/css/bootstrap.min.css" type="text/css" />
	<link rel="stylesheet" href="/bugLog/hq//includes/bootstrap/css/bootstrap-responsive.min.css" type="text/css" />
	<link rel="stylesheet" href="/bugLog/hq//includes/style.css" type="text/css">
	<link rel="shortcut icon" href="/bugLog/hq/../favicon.ico">
	<script type="text/javascript" src="/bugLog/hq//includes/jquery-1.8.0.min.js"></script>
	<meta name="viewport" content="width=device-width, initial-scale=1.0">

On Wednesday, September 2, 2015 at 1:59:17 PM UTC-5, Randy Smith wrote:

[Oscar Arevalo]

Randy, if you open any of the css or js files directly in your browser, do they work?

i.e. http://...your..host../bugLog/hq//includes/style.css

Also, what value do you have for "general.externalURL" in the main config file? (buglog-config.xml.cfm)

Thanks!

Oscar

--

---
You received this message because you are subscribed to the Google Groups "BugLogHQ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bugloghq+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Oscar Arevalo

http://about.me/oarevalo
http://www.coldbricks.com - Content Management System
http://www.oscararevalo.com - My Blog

[Randy Smith]

Oscar,

No, they do not work unless I remove /buglog and the extra forward slash after hq.

I have tried many thing in externalURL, from leaving it blank to using just one forward slash, to filling in the complete URL, http://buglog.contract-central.com/

I can get it to work to a point -- you can see if you go to http://buglog.contract-central.com/ and use credentials of admin/temp1

I also for the life of me cannot figure out how to consume this web service from my production and local environments based on the information provided. Any help would be appreciated. I started reviewing another product because of all the issues this one is giving me, but I'll hold up until I hear more from you.

RLS

[Oscar Arevalo]

Hi Randy,

Ok, so the "default" setup for BugLog is assuming you will having a folder named "/bugLog" at the root of your website. That is "http://hosname/bugLog". That should work without any modification to any setting on the config.

If you want to run buglog at the "root", so that it would be available at:  "http://bugs.domain.com/" or similar, you should only need to set externalURL to "/" (or depending on your DNS/network/webserver setup, sometimes you would need the full URL: i.e. http://bugs.domain.com/).

Now, after you make any change to the config file, remember to click the "reset app" link on the login page. Or if you can't access the login page due to bad paths, you can just go to http://domain/bugLog/hq/?resetapp=1 (or http://domain/hq/?resetapp=1, depending on your configuration). That will made the app force a reload of all its settings.

The way BugLogHQ works is as a "client/server" setup. That means that any application from which you want to report errors (or environments of the same app) have to be running a client component, which is called locally and it posts the error (or message) to the "server" (which is your BugLogHQ instance).

So, lets say you have an application MyApp. And you have it running locally for development and on another server as the production environment. On the codebase for MyApp you need to include the BugLogHQ client, which is available on "/client" directory of the BugLogHQ app. You can find there clients for different languages, but basically they all follow the same format. You include the appropriate client in your app, and then wherever your app handles errors, you call this component to send the error details to the buglog server. BugLogHQ will receive all these reports from all the instances/servers where MyApp is running and group them accordingly.

Hopefully this provides a bit more clarity, but let me know if you have any more questions or need more details.

Thanks!

Oscar