tarikhe shamsi

International Persian
1

salam doustan,

be nazaretoun momkene sohbat kardo taghvime shamsio tu noskheye baad dakhele yii dashte bashim?

2

[right][font="Tahoma"][rtl]

اگه منظورتون به صورت یک extension باید کسی زحمت تهیه اونو بکشه

[/rtl]

[/font] [/right]

3

می شه توضیح بدید چطور می شه از این تقویم استفاده کرد؟

4

man gire emtehanatam,age forsat kardid zahmatesho bekeshid vagar na iashala baade emtehanat ba ham radifesh mikonim

5

From my experience, this topic comes up regularly in Persian-speaking Yii communities, and the short answer is that it’s very unlikely the Yii core itself will ever ship with built-in Shamsi (Jalali) calendar support.

Framework cores usually try to stay neutral and minimal. Yii already relies heavily on PHP’s Intl extension and ICU data, which are fundamentally Gregorian-based. Adding a second calendar system like Jalali into the core would introduce maintenance, localization, and backward-compatibility challenges for a global audience that mostly doesn’t need it. For that reason, core teams usually prefer extensibility over embedding regional calendar logic.

That said, Yii is actually a very good candidate for clean Jalali support at the application or extension level. In real projects, I’ve seen three practical approaches work well:

  • Using a well-tested Jalali date library (such as those based on jdf or ICU wrappers) and integrating it through Yii components or helpers.
  • Handling Jalali dates at the presentation layer (forms, datepickers, views) while keeping Gregorian dates in the database for consistency.
  • Writing custom formatter classes so Yii’s date/time formatting pipeline can transparently output Shamsi dates without touching core code.

What’s interesting is that the same architectural pattern appears across different PHP ecosystems. I work mostly on Persian and Shamsi localization for PHP frameworks, and I’ve seen very similar discussions in Laravel, Symfony, and especially WordPress communities. In WordPress, because of its plugin-based architecture and large Persian user base, Shamsi date handling has evolved faster and more maturely as a standalone module. That ecosystem is often a useful reference for Yii developers who want to see how Jalali support can be cleanly isolated, maintained, and adopted without forcing changes into a framework core.

For example, some of the design decisions and edge cases around date conversion, admin UI consistency, and long-term maintenance are discussed and implemented in tools like the WordPress Shamsi module, which can offer practical insights even if your main stack is Yii.

In summary, I wouldn’t expect native Shamsi support in Yii core, but Yii already gives you all the hooks needed to implement it properly at the application or extension level. Looking at how other PHP platforms solved the same problem can save a lot of trial and error.