Hello
I’m using the Events Calendar widget with the Korean locale (ko) , and I noticed that the date cells display text like “3일”, “15일” , etc.
I would like to hide the “일” suffix so that only the number (e.g., “3”, “15” ) is visible in each date cell.
Thank you for your support!
Best regards,
Joshua Kim
1 Like
Irene
August 7, 2025, 3:16pm
2
Hello Joshua
Let me ask the devs how can we do that for you. Will be back with the news as soon as possible
2 Likes
Irene
August 8, 2025, 11:24am
4
Hi there, @user12542
Great news – the devs managed to remove the suffix with the help of a special JS code for you! Wanted to remind you that it doesn’t affect the editor view, but you should see the change on your website
Could you please check it and let me know if this is what you had in mind?
I’m happy to see that it’s the possible option with the JS, and thank you all for the efforts to acheive it!
On the first load, I can see that all the suffix has been removed, but when I navigate to other months, all the suffix appears again. Can I get the solution for this?
Have a good day
And the other way around, there has to be suffix ‘일’ in the right format of Korean Date in the popup, like “8월 8일 - 8월 10일”.
I attached the image of the current format missing the suffix ‘일’, which gives much awkwardness to the Korean users.
Thank you again for your support.
Irene
August 14, 2025, 11:58am
8
Hi, @user12542 ! I’m sure that we’ll manage to fix it all up for you
For us to provide a more accurate fix, could you please send me a direct link to the webpage with the widget? It will help us to test everything out in your website’s environment before applying the solution
Here it is! Thank you again to you all
1 Like
Max
August 18, 2025, 5:55pm
10
Hi there, @user12542
Thanks for sharing a link!
Your request is with our devs now. I’ll report back as soon as I have any news
Max
August 19, 2025, 10:22am
11
We’ve replaced the previous script with the new one and now everything seems to be working fine:
function listener(selector, callback) {
const firstTarget = document.querySelector(selector);
if (firstTarget) {
return callback(firstTarget);
}
const observer = new MutationObserver((_, observer) => {
const targetNode = document.querySelector(selector);
if (targetNode) {
observer.disconnect();
callback(targetNode);
}
});
observer.observe(document.body, { childList: true, subtree: true });
}
listener('.eapp-events-calendar-calendar-component', (container) => {
const mutationObserver = new MutationObserver((_, observe) => {
const days = container.querySelectorAll('.fc-daygrid-day-number');
if (days.length) {
observe.disconnect();
days.forEach((day) => {
day.textContent = parseInt(day.textContent);
});
observe.observe(container, {
childList: true,
subtree: true
});
}
});
mutationObserver.observe(container, {
childList: true,
subtree: true
});
});
Please check it out and let me know how it works on your end
Thank you very much! It’s working perfectly now. Could you also help me with the other request I mentioned above? It begins with “And the other way around,~”.
Have a good day
1 Like
Max
August 21, 2025, 11:13am
13
Ah, sorry for missing that!
I’ve forwarded your request to the devs and will report back once I have any news
1 Like
Max
August 25, 2025, 11:45am
14
Thank you for waiting!
We’ve changed the display date format for the Korean language in your widget, and now it looks the way you need.
Please check it out and let me know if everything is fine
Unfortunately, after checking on my side, I wasn’t able to confirm the recent changes. Could you kindly assist me with this issue?
Additionally, I would like to suggest one more improvement related to the Korean date format.
Current display:
8월 25 1:20 오전 - 8월 30 1:20 오후
Suggested correction:
8월 25일 오전 1:20 - 8월 30일 오후 1:20
To clarify:
The suffix “일” (meaning “day”) should follow the date number.
In Korean, AM/PM is expressed as “오전/오후” and placed before the time , not after.
Thank you as always for your kind support. Wishing you a wonderful day.
Best regards,
Joshua
1 Like
Max
August 26, 2025, 10:59am
16
Huh, that’s weird, as it worked fine initially:
Thanks for bringing this to our attention! I’ll discuss this and a.m/p.m display format with the devs and let you know once I have any news
1 Like