I started using https protocol and noted that the selections within the calendar becomes inactive ( e.g name, time slots e.t.).
after refreshing the page selections becomes active again til the page loads again.
Any one else having this issue?
Try them out, don’t worry about breaking it (it resets every AM). See if you can reproduce on there. Also give more details about what your specifically doing before you lose functionality.
Also, what’s your php and mysql version?
What’s your openemr version?
I’m a little lost in the code trying to find this. The “Day”, “Week”, “Month”, etc… links on my Calendar point back to http even though it is everything else runs under https. One difference, where you have “openemr”, I am using a sub-domain so “” is my $web_root.
It is something in . One of these files below is creaking the https links. One file has DOS new lines and another is is has Linux feeds, so it makes time difficult to diff the files. Also, they are almost identical files. If these were combined it would be easier to maintain:
Anyways, the resolves to the http address for my server, but the documents are all under https. When I view the source in the browser I see the link referring to http:
The rel-310 calendar worked under PHP 5.2.10 (did not test SSL). But under PHP 4.3.9 the calendar does not compile (no compiled classes under interface/main/calendar/modules/PostCalendar/pntemplates/compiled).
hi,
It’s quite possible our days of supporting php4 may well be over. Most of the developers have not been developing in php4 for some time now. Anybody else having calendar issues in php4?
-brady
Ok, I have upgraded to PHP 5. I can see the calendar now. It has the same problem though, the day, week, month, links refer to http. The difference now, I using the tag instead of the patch.
hey,
I wouldn’t feel need to go through the patch; tags will cover everything. After looking through, the other https bug somehwere else, so don’t expect the patch to fix this.
Are you forcing https in apache?
-brady
I was forcing https. We are just testing now, so I’m allowing http too. The main screens remain on https. It is possible that that data does not need to be encrypted; if there is no identifying patient info. It would be good to not have to use http one day though.