Sage Serveur I7 Download [NEW]
Angelo Dearring
I want to set up a local sage server for my freshman physics studentsto use. I am using Ubuntu 10.10 and followed the directions at theSageServer wiki and it worked just fine. Assuming my server is at , going to this URL would fire up sage justfine, with apache proxies rerouting / to localhost:8000.
This installation, however, assumes that the document root of the webserver is where the installation should occur. The associated proxyredirects essentially take over the whole web server--that is,accessing other web services, like a wiki or some other php codesbecomes impossible. I tried changing the proxies to referencesomething like (that is, proxy redirect/sage/ requests to localhost:8000). This works initially, but the css,etc. was all missing. I fixed this with URL rewrites in/sage/.htaccess, which edits the absolute references in the sage htmlfiles. Things looked perfect now at , andmy other web services were available too.
The problem now is that all sage worksheets contain a red "Searchingfor sage server..." and the worksheets become useless (i.e.disconnected from the sage server). Likewise the javascript action ofdeleting, etc. a worksheet are broken. I am stuck here and cannotfind a solution to this problem. Has anyone tried installing a sageserver into any web directory other that the root one? Any luck?
We're experiencing an issue with users who are logged into Windows during a Sage server restart. Whether the user has Sage 300 open or not, the Actian service begins using more CPU usage and the user is unable to connect to the Sage server until he restarts the desktop.
I have read thread after thread on here and on the sage forum to no avail and just cannot make head or tail of it. Im fairly sure its something to do with a redirection URL IE - The checkout_success page but im at a loss as to where its defined, or why it would need to be edited?
" I have investigated the all the log and each time the transaction are timing out due to the fact that we cannot connect to the following URL
( -api=woocommerce_sagepayserver)
I would advise on investigating the URL in question to see if it is active and responsive."