English Post your requirements here

Question regarding skins and languages

In looking through the code, I see some of these are hard-coded. How does this work with multi-lingual sites and new skins? Also, how does the auto-update feature work with customized sites?

Hi, I just discovered YACS yesterday and the demo has blown me away! Wizards for posting articles and creating forums - I've never seen that before in a CMS!

I'm also impressed by the apparent flexibility of where discussions can take place on a site. It seems that anywhere there is an article, there can be a snippet of a discussion forum related to that article. This is wonderful and much better than any 'blog'.

However, before I jump in and commit my site to this software, I took some time to look over the code to see how well designed it is and how easy it will be to customize.

Customization brings up one question, especially with the auto-update feature. If I customize anything, am I force to then manually update the software from that point on?

And since there are several language variables defined within the code, it seems that changing even one of them will change the MD5 hash and trigger the update process, thereby destroying the modifications.

What would be great would be if the software had many different 'hooks' where custom code files referrenced in the database could be included. This is something that is done in LDU and Seditio (http://www.neocrome.net) and seems to work great. This way, customizations could be added without changing the MD5 hash of the main files.

Also, if language variables were defined in separate files, then they could be ignored during the upgrade process and customizations maintained.

The other questions I want to know about regards the hard-coding of specific templates (layouts) in the main index file (around lines 578 to 608). How does a new skin or layout get included without modifying the code? Again, this is a concern about the auto-update feature.