Closed ksdavidc closed 3 months ago
I thought perhaps it was a conflict with either the Natural Language Dates plugin, or the Templates plugin, but even with these off it doesn't work.
Was just testing on a vault with many plugins loaded, got similar errors, on a fresh vault it works normal. I will be looking into this.
The issue was that the element identifier I used to get the parent element for the datepicker element seems to have been too specific, and it changes under some cases, perhaps because of some plugins.
I changed this just to a class name and the problem seems to be fixed.
I created a new release 0.3.8 containing this fix + some other small improvements/fixes
Thank you for opening this issue.
Please let me know if you have any other comment before I close this issue.
can't check it right away but will soon THANK YOU
On Sat, Jul 13, 2024, 08:55 joycode-hub @.***> wrote:
Please let me know if you have any other comment before I close this issue.
— Reply to this email directly, view it on GitHub https://github.com/joycode-hub/datepicker-plugin/issues/1#issuecomment-2226541770, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO2Y35EKTKS7EKFA6JHMRDLZMBUGVAVCNFSM6AAAAABKYKIMGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGU2DCNZXGA . You are receiving this because you authored the thread.Message ID: @.***>
Success!!! thanks
was working but now I am getting error:
datepicker.log
not sure how to debug...
I expect it is a plugin conflict as I have many installed, but wonder if you might have a clue where to look.