1) I had to regress to LC server 6.6.2 to solve some problems that David and I have yet to ascertain. I think this is related to the session context bug 14452. Drop the LC server executable version of your choice into your cig-bin folder(I used livecode-server-6.6.2). Then put this into your .htaccess file: AddHandler livecode-redirect .lc Action livecode-redirect /cgi-bin/livecode-server-6.6.2
2) Be aware that the new Unicode enabled MySQL server has 2 things that got me: a) I could not insert HTML into a text field and had to change the collation of the field to utf8mb4_general_ci. After that the old code worked just fine. b) When you insert into tables that have fields that do not have the "null attribute" and also no "default value" MySQL will now throw an error if that field is not part of the insert. Again after setting the "null attribute" check box all was fine with the existing code. Hope this gets you back in business. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -----Original Message----- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Phil Davis Sent: Wednesday, March 16, 2016 2:38 PM To: How to use LiveCode; LiveCode Developer List Subject: server difficulties coming from LC7, or new host? Hi folks, Summary: Since diesel was moved to the new hosting provider last weekend, my main customer's relatively stable client/server system no longer works. I'm trying to understand why. (The server code is in my customer's on-rev account, not on a LAN server.) I have adjusted arrayEncode() in my server code to work with my 6.x client apps, but this has not been enough to make everything work again. The apps are able to interact with server code enough to get authenticated as valid users of the system, but any attempt by an app to download a data chunk of 200k or so causes timeout errors, even if I set client and server socketTimeoutIntervals to a ridiculously long 60 seconds. (My server tests show that the server is done with the 'put' loooong before the client 'post' times out.) Communication from clients to server use 'post' or 'get', and the server code 'puts' all data back to clients. Details: Each of 3 desktop apps reaches out to the code in my customer's on-rev (now LC) hosting account for authentication and data before proceeding. Then in the course of doing their jobs, they will upload or download other info. With the advent of the new hosting provider, we were also given LC 7.1.0 as our only choice of server engine. This in itself is not a bad thing, but it immediately impacted my world. I had to change all instances of "arrayEncode()" in my server code to include the "6.7" param since all our desktop apps are currently built with LC 6.x. (Our transfer data is often structured in arrays underneath the encoding.) For a full 10 seconds or so after that change, I thought our problems were solved, but it only allowed the next problem to manifest itself. I'm probably leaving out some vital info, so feel free to ask. I'm getting nowhere right now, so I'll greatly appreciate any insight you can offer. I would love to discover that I'm overlooking something simple. (Hey, I can always hope!) Thanks - -- Phil Davis _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
