Faster searching and free account access

[omcgb]

Odd because that code is generated by php
the line at server before being interpreted reads:

maxDate: new Date(<? echo date("Y, ").(date("m")-1).", ".date("d"); ?>),

Ah actually could be a combination of different login session levels. Let me see if I can recode.

Very strange! Shouldn't the maxDate be +1 month?

As your script files are in the header you should be able to add the <script> above </head> and remove the time delay.

 

[RobM]

No javascript datepicker needs months from 0 to 11 and php goes from 1 to 12
The script tags enclose a jquery document ready so now it doesn't matter where they are. The only reason I have to put that in the front page is because I want to inject php and you can't do that with js files. The timeout was put in before the document ready was, I've removed it now but that makes no difference.
What browser/OS are you using? I should add that the line in the above posts could be completely irrelevant - if you are logged in the maxdate will obviously be whatever your account has permission to view.

 

[omcgb]

Sorry, my point was shouldn't maxDate be greater than today?

As before, same as you: Chrome 68 - Windows 7

 

[RobM]

Maxdate depends on your account access. If you visit the site and you are not logged in or on a free account maxdate is obviously the same day as today. That was the code I listed.
Any errors in your developer console? I can't repeat this issue with any browser/os combinations so is hard to get to the bottom of.

 

[omcgb]

Maxdate depends on your account access. If you visit the site and you are not logged in or on a free account maxdate is obviously the same day as today. That was the code I listed.
Any errors in your developer console? I can't repeat this issue with any browser/os combinations so is hard to get to the bottom of.

I am logged in and currently viewing the full list for the 11th

No errors showing in console.

 

[omcgb]

The delay has now gone but the maxDate is still 1970

$('#datepicker').datepicker({
dateFormat: 'dd/mm/yy' ,
minDate: new Date(2018, 7, 8),
maxDate: new Date(1970, 0, 1),
setDate: new Date(2018, 7, 8)
});

 

[RobM]

Can you paste what you see at https://ukdroplists.com/debugInfo.php or PM

 

[omcgb]

It works fine when I first sign in, so I think the issue is arising from logging in using cookies (remember me).

This is after a manual login:

1: 2018-08-08
2: 4
3: 6
4: 25
5: 2018, 7, 14

 

[RobM]

I'll look into that.
However I think there is only one or two cookies stored for a remember me - all other information (as the pasted above) is from server-side sessions to prevent issues. That last number is the exact same string that gets injected into the 'maxDate' and even if the system didn't recognise you as we've seen at php level it will inject todays date.

 

[RobM]

Yep you're right - cool thanks I now have the same error and can fix it

 

[omcgb]

I'll look into that.
However I think there is only one or two cookies stored for a remember me - all other information (as the pasted above) is from server-side sessions to prevent issues. That last number is the exact same string that gets injected into the 'maxDate' and even if the system didn't recognise you as we've seen at php level it will inject todays date.

It must be that some data is missing from the "remember me" sign in process.

This is debug now after revisiting:

1: 2018-08-08
2: 4
3:
4: 25
5: 1970, 0, 1

 

[RobM]

Fixed now.

 

[omcgb]

Yep, working perfectly now.