vB-Integration-Problem after upgrade to 3.32

[TheSonic]

I uploaded the new version 3.32 and - integrated with vB 3.6.1 - i get:

Warning: main(./languages/english.php): failed to open stream: No such file or directory in (strip)/rp/pp-inc.php on line 167

Fatal error: main(): Failed opening required './languages/english.php' (include_path='.:') in (strip)/rp/pp-inc.php on line 167

I disabled the integration and all works fine (looking bad - but no errors)
There is the problem ?

I used the prior veresions without problems and integrated

Thanks

PS: engelish.php is in the called directory

[TheSonic]

Got it... Old Config-File was overwritten (after upgrading PhotoPost i thought it was the same in RP).

Would be great, if Reviewpost also could contain only config-files called config???.php.new preventing overwriting the old configs.

Nevermind - it works.

Thanks!

[Chuck S]

Upgrade instructions just like Photoposts upgrade docs state not to overwrite the config.

[TheSonic]

Of course, but it would be easier if the config-int and config-intr would be renamed into something like config-inc.php.new (like Photopost 5.5 does - vBulletin does ist simular).

It's just an idea that makes life easier - Of course we (=the users) have to take care of our sites and in my case, i was a bit to quick Instead of getting a backup i filled the config-files up again, missed one line and go the above error.

Thanks - both upgrades (PP & PP) are working fine for me

[Chuck S]

Yes I see your point but can point out the other side of the coin there.

Several support threads where people never removed the .NEW from the config files when installing and had issues

[TheSonic]

I see - your are right too

But the company should follow ONE direction. If i install Photopost and where are .new-Configs (without killing my actual configs) ReviewPost should handle it the same... Or both should deliver overwrite-able configs

Most scripts i know delivering their scripts with "modified" filenames, but if you have too much supportrequests on that topic, i understand that you keep the original filenames.

One wish: Do it the same for all products of your company and we (customers) and you (devs) will be fine

Thank you