Yestarday I upgrade my CPG 1.3.2 to 1.4.1 beta. And I see, that pnCPG don't want to login users from MDPro1.0.7 to CPG1.4.1beta.
I tested it on two copies of CPG (I still have older version CPG 132 on the server - 141beta is an upgraded copy of older 132 gallery, placed in another directory and used own prefix, tables and cookies). Both pnCPG 2.6 and pnCGP 2.7 works good with CPG 132, but not with 141.
What is the effect? If I'm logged in CPG as... MrX (by current browser), and I have my MDpro in another label (eg. I'm in it as a guest) and I try to go to cpggallery from CMS level (by pnCPG menu-command), than gallery is opening, but with me logged as... MrX, not Anonimus.
When I'm logged in CMS as MrX and try to go to gallery used pnCPG, in CPG I see, that pnCPG try to login me, but in effect I stay unloged.
I can send CPG Debugger info generated after CPG is opening by pnCPG, if you need it.
Peter
Peter,
last stable release is 1.33, i am working on 1.4 but need further testing. UIt was working on the first relase of 1.4, so i need to download this latest version.
To be continued................
Cas
Cas
That's O.K. - a time ago I read in one description, that pnCPG (2,5? 2,6???) is optymized for CPG 1.4.1... but I understand situation. ;)
So I've got a time to test beta and write lang for it to the moment, new stable version will be send.
P.S. Do you need polish lang for pnCPG? It's possible to make it in shor time.
Peter
Peter,
any new language is welcome, I try to keep up withnall releases but definately language support is always welcome also for pnCPg.
Cas
Cas,
In file below there is polish lang fot pnCPG with additions:
1. In lang for random block I added a few lines, becouse random_block was a litlle bit modyfied by me - these lines are added on the top, so it'll be easy to delete them.
2. In package there is modyfied random-block for your test (I'm not a programmer, only a photographer and painter ;D) - on my side this kind of content displaying looks more frendly, but... you know.
3. Warning: in CPG prefix for files (eg. thumbnails) is defined by gallery owner; in pnCPG it's written in code, without possibility of changing it by Admin panel.
vbr
Peter
Peter,
thanks for your additions, will incorporate the language files in the next release and will chedck out the random block.
Cas
Any word on this?
I've just upgraded to 1.4.1 and such and i have postnuke .750 and it doesn't register when my users click the link to get to the coppermine. it opens but doesn't register that they're on coppermine.
cas?
someone?
anyone?
Sorry guys(girls), was travelling hence a late reply.
I still need to update the readme so people downloeade 3.1 might have this issue.
During the upgrade from 1.3x to 1.4.1 you have been asked if you like to start encrypting your passwords. If you said "yes" pnCPG will not work without changing a setting "under water".
Installing from fresh does not even ask, just encrypts.
I have asked the developers to have it available as a choice but they are (untill now) not willing to do so.
There is a way to make it work again :
1. Open the database with a tool like phpMyAdmin
2. Select the table cpg141-config (possible you have a different prefix)
3. Find the record with the key "enable_encrypted_passwords" (record 104 in a fresh install)
4. Set the value to 0
pnCPG will work fine again.
Perhaps if all users of pnCPG will ask the developers to make this option available as a choice (which is very easy) they might get convinved of the use of this.
After you have changed this setting it actually already shows up as an option.
Cas
thanx for the reply cas.
i'm following you on those instructions untill i get to 3.
my coppermine table in the database was called cpg132_config just for reference (even though i did upgrade)
so i open up that config file and i'm totally lost
i see to fields Name and Value and when i click on browse i don't see anything anywhere that says 'enable_encrypted_passwords'
so can you elborate on where to go once we get into the config please and thanks
still waiting on a reply for this.
cpg1.4.x goes unsupported, either standalone or integrated into postnuke using pnCPG. Unsupported means: there is no support for this version. Downgrade to the most recent stable version (currently cpg1.3.5) if you need support. You won't get an answer. This thread has been invalid in the first place. Marking it accordingly and locking it.