I'm using the most up to date versions of both checkout(4.1) and paypal checkout(4.0)
The latest version of checkoutpaypal is code revision 1653 - which doesn't have anything "in modules/checkoutpaypal/classes/CheckoutPaypalHelper.class at line 51" that could throw an error.
I suspect you're using revision 1586 (which does) and that you should therefore update your codebase.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Tue, 2008-12-23 06:13
Solved! Thanks!
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 20:01
In my photo album page in the top left corner is "View BaskeT" note the capital T...where can I fix this? I've been trying to find where to fix this for two days now and can't seem to find where this is being pulled from.
alecmyers
Joined: 2006-08-01
Posts: 4342
Posted: Sat, 2009-01-10 20:03
Yes, it's, um, a typo in the en_GB translation - sorry about that. It's actually in the en_GB.po file, if you want to fix it and rebuild the .mo. Or wait for 0.4.3 which is nearly ready, and I promise to fix it there.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 21:25
Need it fixed today for the client, not sure how to do rebuild the .mo though...
By the way, if you're going to take money off clients for installing/supporting Gallery then you really need to make sure you have the technical skills to deliver what you're offering. Coming on a free support forum and announcing that you "need it fixed today" doesn't really cut it, as far as I can see.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 22:31
I don't normally work with gallery...I used at as a favor to a long time client because thats what they wanted. It's not what I wanted to use. This is my first time ever working with gallery and/or using it, most of the software I usually work with has better documentation than what I've found for gallery. And I've found it very unintuitive and one of the most frustrating pieces of software that I have worked with. And I've never worked with .po and .mo files as the software I normally work with does not use these, it uses straight php.
alecmyers
Joined: 2006-08-01
Posts: 4342
Posted: Sat, 2009-01-10 22:30
Quote:
And I've found it very unintuitive and one of the most frustrating pieces of software that I have worked with.
Experiences vary. I love it; I've found exceptionally elegantly written with even the opaque parts dissolving into crystal clarity when you take the trouble to understand what the developers were doing, and why.
To be honest, my opinion is that for a scripted (php) project, using the gettext translation system is a desperately poor choice because of the complexity of customizing the translations compared with the simplicity of editing the original text in the template files. I'm pleased to see that Gallery3 looks like it will be using something developed in house and much more easily tweaked.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 22:33
It seems much more difficult to make simple changes using it. I've never seen it used within any of the software scripts I normally work with (Joomla, Mambo, osCommerce, CRELoaded, etc).
I've downloaded Poedit and I'm attempting to make the changes, but I think I'm doing something wrong because its not changing when I upload the new files to my server.
alecmyers
Joined: 2006-08-01
Posts: 4342
Posted: Sat, 2009-01-10 22:40
Quote:
I think I'm doing something wrong
When you've edited the .po file, get the en_GB.mo file (I think poedit will compile to .mo files too, although that's not how I do it) then rename that to modules_checkout.mo and put it in the g2data/locale/en_GB/LC_MESSAGES folder.
The gettext system is designed for compiled languages where the translators are one-per-language and widely separated from the developers, and .mo files can be created for any language long after the application code is settled and released. It also handles multiple plural forms and all sorts of good stuff. It sucks (my opinion) where one person needs to change a couple of strings in the source code and propagate those changes to all the different translations. The Gallery-provided scripts improve the situation a bit, but ... not that much.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 22:41
Perhaps my frustration with it comes from not having the time to understand what the developers were doing and why. But at the same time, I can usually pick up a new peice of software and understand it fairly quickly, I have not found this true with Gallery.
DragonMistress
Joined: 2008-11-28
Posts: 9
Posted: Sat, 2009-01-10 22:46
Ahhh that was the key...I had the .mo file, but I didn't know to rename it to the modules_checkout.mo. Thanks so much!
Posts: 4342
Hello DragonMistress
The latest version of checkoutpaypal is code revision 1653 - which doesn't have anything "in modules/checkoutpaypal/classes/CheckoutPaypalHelper.class at line 51" that could throw an error.
I suspect you're using revision 1586 (which does) and that you should therefore update your codebase.
Posts: 9
Solved! Thanks!
Posts: 9
In my photo album page in the top left corner is "View BaskeT" note the capital T...where can I fix this? I've been trying to find where to fix this for two days now and can't seem to find where this is being pulled from.
Posts: 4342
Yes, it's, um, a typo in the en_GB translation - sorry about that. It's actually in the en_GB.po file, if you want to fix it and rebuild the .mo. Or wait for 0.4.3 which is nearly ready, and I promise to fix it there.
Posts: 9
Need it fixed today for the client, not sure how to do rebuild the .mo though...
Posts: 4342
overall instructions are here:
http://codex.gallery2.org/Gallery2:Localization
By the way, if you're going to take money off clients for installing/supporting Gallery then you really need to make sure you have the technical skills to deliver what you're offering. Coming on a free support forum and announcing that you "need it fixed today" doesn't really cut it, as far as I can see.
Posts: 9
I don't normally work with gallery...I used at as a favor to a long time client because thats what they wanted. It's not what I wanted to use. This is my first time ever working with gallery and/or using it, most of the software I usually work with has better documentation than what I've found for gallery. And I've found it very unintuitive and one of the most frustrating pieces of software that I have worked with. And I've never worked with .po and .mo files as the software I normally work with does not use these, it uses straight php.
Posts: 4342
Experiences vary. I love it; I've found exceptionally elegantly written with even the opaque parts dissolving into crystal clarity when you take the trouble to understand what the developers were doing, and why.
http://en.wikipedia.org/wiki/Gettext
To be honest, my opinion is that for a scripted (php) project, using the gettext translation system is a desperately poor choice because of the complexity of customizing the translations compared with the simplicity of editing the original text in the template files. I'm pleased to see that Gallery3 looks like it will be using something developed in house and much more easily tweaked.
Posts: 9
It seems much more difficult to make simple changes using it. I've never seen it used within any of the software scripts I normally work with (Joomla, Mambo, osCommerce, CRELoaded, etc).
I've downloaded Poedit and I'm attempting to make the changes, but I think I'm doing something wrong because its not changing when I upload the new files to my server.
Posts: 4342
When you've edited the .po file, get the en_GB.mo file (I think poedit will compile to .mo files too, although that's not how I do it) then rename that to modules_checkout.mo and put it in the g2data/locale/en_GB/LC_MESSAGES folder.
The gettext system is designed for compiled languages where the translators are one-per-language and widely separated from the developers, and .mo files can be created for any language long after the application code is settled and released. It also handles multiple plural forms and all sorts of good stuff. It sucks (my opinion) where one person needs to change a couple of strings in the source code and propagate those changes to all the different translations. The Gallery-provided scripts improve the situation a bit, but ... not that much.
Posts: 9
Perhaps my frustration with it comes from not having the time to understand what the developers were doing and why. But at the same time, I can usually pick up a new peice of software and understand it fairly quickly, I have not found this true with Gallery.
Posts: 9
Ahhh that was the key...I had the .mo file, but I didn't know to rename it to the modules_checkout.mo. Thanks so much!