Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#7233 closed defect (invalid)

locale not found error because of typo in

Reported by: mettler@… Owned by: Ryan J Ollos
Priority: normal Component: WikiCalendarMacro
Severity: normal Keywords: locale compile_catalog
Cc: Steffen Hoffmann Trac Release: 0.12


allready posted this one, seems it disapperead.

in we changed

'locale/*/LC_M3SSAGES/*.mo', to: 'locale/*/LC_M3SSAGES/*.po',

else locales could not be found, leading to server errors.

..if i don't spell M3SSAGE with the '3', my report gets blocked because of spam filters!

good plugin! thanks alot!!

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by Ryan J Ollos

I think you may have posted the issue for WikiTicketCalendarMacro: see #7220. I'll try to get this fixes today.

comment:2 Changed 7 years ago by Ryan J Ollos

Resolution: invalid
Status: newclosed

This macro doesn't have a, so I think you must be referring to the WikiTicketCalendarMacro and the issue appears to have been fixed in the previously cited ticket.

comment:3 Changed 7 years ago by Ryan J Ollos

Cc: Steffen Hoffmann added; anonymous removed

comment:4 Changed 7 years ago by Steffen Hoffmann

Keywords: locale compile_catalog added; lacales removed
Trac Release: 0.110.12

Confirm. Only WikiTicketCalendarMacro has to be packaged as a Python egg to make it work with the bundled CSS and message catalogs for localization. Please don't mix with WikiCalendarMacro here.

At WikiTicketCalendarMacro this is also not the 0.11 but the 0.12 branch. Please make sure you always add the version you use, making it possible to give you upgrade hint's, if there is a later version available that has a fix.

Last, your report was invalid but still considered helpful, so I

1.) closed it as invalid with plenty of explanation why, 2.) I opened ticket #7221 to demonstrate that I still feel responsible for user headache 3.) modified and extended the wiki page for WikiTicketCalendarMacro at best knowledge to point out the necessary steps to save others from the reported experiences right from the start 4.) keep aforementioned documentation bug open for a while even if I feel it is already fixed

Please, act equally sensible and respect the effort by more correct contributions (as stated above). You'll always find someone helpful here, if mirroring the kindness received. :-)

Modify Ticket

as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.