I build Sharepoint webpart with RadScheduler on one server, then I deployed with sharepoint package on another server, why I get different layout for both server?
How to make it default like documentation on this link https://docs.telerik.com/devtools/aspnet-ajax/controls/scheduler/recurrence-editor/overview
4 Answers, 1 is accepted
the reason why I need "original" layout like documentation, because with dropdown recurrence selector, recurrence rule always use HOURLY frequency, event I already clear that drop down and fill it just with DAILY, WEEKLY and MONTHLY
RadDropDownList recurrenceAppointmentDropDwon = (RadDropDownList) recurrenceEditor?.FindControl("RecurrentAppointmentDropDown");
if (recurrenceAppointmentDropDwon != null)
{
recurrenceAppointmentDropDwon.Items.Clear();
recurrenceAppointmentDropDwon.Items.Add(new DropDownListItem(RecurrenceFrequency.None.ToString(),RecurrenceFrequency.None.ToString()));
recurrenceAppointmentDropDwon.Items.Add(new DropDownListItem(RecurrenceFrequency.Daily.ToString(), RecurrenceFrequency.Daily.ToString()));
recurrenceAppointmentDropDwon.Items.Add(new DropDownListItem(RecurrenceFrequency.Weekly.ToString(), RecurrenceFrequency.Weekly.ToString()));
recurrenceAppointmentDropDwon.Items.Add(new DropDownListItem(RecurrenceFrequency.Monthly.ToString(), RecurrenceFrequency.Monthly.ToString()));
}
when I create recurrent appointment with daily frequency, recurrence rule created with hourly frequency
How can I fix this?
To achieve the same look and feel as in the documentation screenshot, you should configure the Scheduler control to use its Classic Render Mode. This can be set via the RenderMode property.
You can find more information in this demo: Render Modes and the documentation.
Best regards,
Rumen
Progress Telerik
Hi Rumen
Thanks for answer, the problem is I run same code on both server, one server for dev environment, one server for production deploy with wsp, of course I use same RenderMode for both server, but it look like different
Any another suggestion?
The difference of the appearance on the development and production servers is most likely due to that the browser is put in compatibility mode.
Does the problem happen in IE only? Are you able to reproduce it in Chrome?
You can find explanation of this problem in the following article: Different appearance or behavior in Internet Explorer on local and production servers.
Best regards,
Rumen
Progress Telerik