Log message #4198817

# At Username Text
# Aug 19th 2019, 22:24 D-rex yeah the logs they provide are useless
# Aug 19th 2019, 22:23 rightscoreanalysis the answer will be there
# Aug 19th 2019, 22:22 D-rex only the ones i could find
# Aug 19th 2019, 22:22 rightscoreanalysis did you check logs?
# Aug 19th 2019, 22:19 rightscoreanalysis on nginx I believe I have the root set to foo/webroot
# Aug 19th 2019, 22:19 D-rex the other was a local host apache on arch linux
# Aug 19th 2019, 22:19 D-rex no one is a web host namecheap to be exact
# Aug 19th 2019, 22:18 rightscoreanalysis are the servers both the same
# Aug 19th 2019, 22:18 D-rex yeah i have all that, it was working on my dev server
# Aug 19th 2019, 22:18 rightscoreanalysis for me anyway
# Aug 19th 2019, 22:18 rightscoreanalysis <IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^$ webroot/ [L] RewriteRule (.*) webroot/$1 [L] </IfModule>
# Aug 19th 2019, 22:18 rightscoreanalysis if apache
# Aug 19th 2019, 22:17 D-rex yeah /home/path/public_html
# Aug 19th 2019, 22:16 rightscoreanalysis are they both pointing to the same folder
# Aug 19th 2019, 22:16 D-rex i added the rewritebase
# Aug 19th 2019, 22:16 D-rex i tried that unless im missing something else
# Aug 19th 2019, 22:16 rightscoreanalysis hthaccess?
# Aug 19th 2019, 22:14 D-rex i have tried numerous different configs and setting changes
# Aug 19th 2019, 22:14 D-rex need some assistance. site ran fine on localhost but just went to upload it to webserver and now im getting error 500
# Aug 19th 2019, 21:41 rightscoreanalysis I tried: $routes->connect('articles/view/:slug', ['controller' => 'Articles', 'action' => 'view'], ['pass' => ['slug']]);
# Aug 19th 2019, 21:41 rightscoreanalysis anyone know how to connect slug route sin the routes.php
# Aug 19th 2019, 19:36 btx @kailas do prod/dev have different OS? the case-sensitivity of the host OS changes results with mysql
# Aug 19th 2019, 16:36 kailas and again, the SQL matches
# Aug 19th 2019, 16:36 kailas @admad yeah… it’s weird that the 100s of other queries wouldn’t have an issue, though
# Aug 19th 2019, 15:58 admad @kailas the disparity in local and prod PHP version is concerning
# Aug 19th 2019, 15:44 kailas downstream of executing the SQL that is
# Aug 19th 2019, 15:44 kailas feels like it could be something like that. but it’d have to be downstream of getting the results of the query, right?
# Aug 19th 2019, 15:43 kailas hrm. where would that be changed/twiddled?
# Aug 19th 2019, 15:43 josbeir maybe some kind of escaping or encoding issue
# Aug 19th 2019, 15:42 kailas @josbeir yeah, I’ve been looking through the log files and broken it down to just that one finder.
# Aug 19th 2019, 15:40 josbeir @kalias if debugging is enabled on production you would not see a possible error, check the debug and error logfiles to make sure nothing fishy is happening
# Aug 19th 2019, 15:36 admad @vossen.steven per url local storage is also an option. Similar to GH
# Aug 19th 2019, 15:36 kailas I’ve also tried clearing cache
# Aug 19th 2019, 15:36 kailas In my code I have a finder that returns no result on my production server, but proper results on my local dev environment. - I’ve looked at the SQL log on the production server and the SQL is identical. - If i execute that SQL from mysql command line on the production server, I get proper results (as well as any other connection to the production SQL server) totally stumped. any ideas?
# Aug 19th 2019, 15:33 vossen.steven session is already done, so will check out the cookie thingy, tyvm!
# Aug 19th 2019, 15:32 dereuromark yeah it would need maybe a more global JS based solution then ;) easiest is to fix the session/cookie part for now to hit this less likely
# Aug 19th 2019, 15:31 vossen.steven was thinking of saving drafts in 5min intervals, but seems to me it's a lot of overhead, if I have to do it for every form
# Aug 19th 2019, 15:31 dereuromark session often has a set limit for timeout (fixed date), if not reactivated/refreshed again.
# Aug 19th 2019, 15:30 vossen.steven yea noticed a lot of apps have the same problem, I thought it was a session problem so I increased the timeout to 24 hours, but it seems to be an auth problem
# Aug 19th 2019, 15:29 dereuromark the persisting and restore is used by github for example
# Aug 19th 2019, 15:29 dereuromark otherwise try the higher session and cookie relogin times, but it can still happen then.