I'm getting a validation error from the CMS when using the datepicker field in the CMS. Since there's been alot of changes to how the date fields work it isn't that surprising that this would start to fail, is there any fix on the horizon?
I've been mucking about abit but I'm not sure exactly what SS wants back from us right now.
I am having an issue with SS 2.3.7 and Image Gallery 2.3 branch. I have an Image Gallery Page with two Albums. I have done some debugging and found that Albums.MoreThanOnePage is using the Images Per Gallery limit as the Albums Paging limit as well. The result is that unless I have more than 16 Albums I don't get Album Pagination. Image Pagination within a gallery works fine also using the 16 limit.
That means the field has already been added to your form from another source. A lot of times that happens with legacy fieldnames, so it's really common with something like SimpleTreeDropdownField because it's based on a foreign key. You just have to get them cleaned up. As an experiment, just look at the source of your form and look for anything in there already named "LinkedPageID" (probably a hidden input). Try changing the field name to something else (even if it doesn't exist in the DB yet) and you'll see that it gets added. Usually just a namespace conflict.
Thanks for your reply. I have changed it to something obscure and the issue is still present. I may be wrong but it looks like a recently introduced bug because this same code has worked on previous SS sites we've done.