Forums

Is it possible? If yes, what exactly to do?

the comments templates need to be edited, check the "showcase" forum posts for some examples!

Regards
Max

First of all, thank you for clean and simple component.

the comments templates need to be edited, check the "showcase" forum posts for some examples!

Regards
Max

Shure, I understand that. I ment overriding in whole site template, something like

site.com/templates/my_template/html/com_chronocomments/...

Not now yet as I can see..

No problem. Any way I already did a lot of of changes in a code of many files for translating many things to Russian. In fact, I have to re-assemble component for live site, but it's worth-while🙂

What I could suggest:

1. Re-think langs phrases. Otherwise some phrases overriding other langs definitions. Example: definition 'Previous' & 'Next' in comments lang file overriding others (for pagination, e. g.). May be 'Next_comment' or some other suffix or prefix?

2. I'm not sure yet for 100% but looks like same situation with some CSS classes. I'll make more tests.

Regards,
Artem

Hi artem,

Thanks for the suggestions, we have a Russian language files, this didn't work without hacks ?

Regards
Max

Hi artem,

Thanks for the suggestions, we have a Russian language files, this didn't work without hacks ?

Regards
Max

Files are ok, except overriding 'NEXT' for other RU lang file (don't now which one exactly, ru-RU.ini might be). I've translated plugin lang file (i can send you but don't know were it using), templates and JS files that do not use lang definitions but have a lot of English (BBCode, validation, etc.). No other way as I understood?

May be I mixing some things with CF, doing many things simultaneously, sorry.

2. I'm not sure yet for 100% but looks like same situation with some CSS classes. I'll make more tests.

Yes, at least class .active in /com_chronocomments/style.css making my menu items bold.

Hi Almer,

Yes, NEXT shouldn't be in the langauge defines for the plugin - you can comment it out and the system will use the default value, or you can rename it to CF_NEXT but you then have to find and replace all the uses in ChronoComments.

Bob