PhotoPost Classifieds 2.1 vB3 Enhanced upgrade

criscokid · January 18th, 2005, 06:35 AM

I've just upgraded from 2.02 to 2.1 - the upgrade was smooth and easy.

When editing the config-int file I noticed that it hasn't been changed and still refers to PhotoPost which may confuse some people - I assume these references are meant to be for Classifieds.

Attempted to login to the admin section of classifieds... enter username and password, and it takes me back to the login screen. From another post
'VB3 Integration of ReviewPost 282' which dealt with the same problem but with Photopost we were advised to remove some code...

so in Classifieds pp-inc.php I removed this:
$log = " · <a href=\"{$Globals['maindir']}/logout.php\">{$Globals['pp_lang']['logout']}</a>";

Still didn't help then checked my config-inc & config-int file and then the database...

In the lastest version of PhotoPost with vb3 intergration the cookie domain has been moved into the database but looking at Classifieds database in the settings table I can't find any reference to a cookie domain.

nexia · January 18th, 2005, 08:08 AM

these are bugs i was to report myself...

>> settings cookie_path and domain_path are not saved on the install/update, so they are blank...

Michael P · January 18th, 2005, 08:20 AM

Well, since the product is called PhotoPost Classifieds, I just left the wording as "PhotoPost" - I'll change it in the three palces to "Classifieds" to try and avoid any confusion.

It looks like the cookie values got placed in the wrong section and should be in section 13; these SQLs will move them into the right config area:

UPDATE settings SET section=13 WHERE id=181;
UPDATE settings SET section=13 WHERE id=182;
UPDATE settings SET section=13 WHERE id=183;

(be sure to add any prefix you might have)

Try going into the Admin Edit Config and check your settings and click SAVE; this will write you a new config-inc.php which doesn't have the values stored in the file which may be conflicting with the database settings.

You don't need to remove any code with this update since the vB3 Enhanced features are toggles with this update (ReviewPost hasn't been updated yet).

criscokid · January 18th, 2005, 08:40 AM

Done that which generated the following output:

UPDATE pp_settings SET section =13 WHERE id =181;# MySQL returned an empty result set (i.e. zero rows).
UPDATE pp_settings SET section =13 WHERE id =182;# MySQL returned an empty result set (i.e. zero rows).
UPDATE pp_settings SET section =13 WHERE id =183;# MySQL returned an empty result set (i.e. zero rows).

But I still can't login to the admin control panel. Looking at the pp_settings table I still don't see any reference to a cookie domain.

If it's any help here's the output from when I ran the upgrade script:

Preparing to update 2.0x database...
Performing MySQL command: REPLACE INTO pp_settings VALUES (84,'PhotoPost Classifieds Version','pversion','','2.1',53,0) ... Successful!
Performing MySQL command: REPLACE INTO pp_settings VALUES (37,'cright','cright','','Powered by: PhotoPost Classifieds --replaceme--
Copyright 2005 All Enthusiast, Inc.',300,'0') ... Successful!
Performing MySQL command: REPLACE INTO pp_admingroups VALUES (13,'Cookie Settings') ... Successful!
Performing MySQL command: REPLACE INTO pp_admingroups VALUES (14,'Forum Settings') ... Successful!
Performing MySQL command: UPDATE pp_settings SET section=14,optionorder=1 WHERE id=7 ... Successful!
Performing MySQL command: UPDATE pp_settings SET section=14,optionorder=2 WHERE id=41 ... Successful!
Performing MySQL command: UPDATE pp_settings SET section=14,optionorder=3 WHERE id=83 ... Successful!
Performing MySQL command: UPDATE pp_settings SET section=14,optionorder=4 WHERE id=163 ... Successful!
Performing MySQL command: UPDATE pp_settings SET section=14,optionorder=5 WHERE id=153 ... Successful!

Upgrade complete! You can now remove the upgrade.php script.

Michael P · January 18th, 2005, 08:50 AM

Did any of your new settings get added to your settings table?

lines 421-437 of the upgrade.php has a whole section of config settings that get moved from the config-inc.php file to the database.

Code:

Content visible to verified customers only.

Did these not get moved into your database?

Michael P · January 18th, 2005, 08:53 AM

If you haven't updated your config-inc.php (or have a backup), I just updated the build with a new check in the upgrade.php. You can upload the upgrade.php from the current build and run it again with the original config-inc.php and it should pick up the values and place them into the database.

criscokid · January 18th, 2005, 09:02 AM

I had a similar problem with stuff not getting written to the databse when I upgraded PhotoPost and ended up having to add it manually.

The only thing that has changed recently is the lastest version of PHP4 got installed... check my PHP and it seems that one the web service didn't have the correct permissions. Got that sorted :-)

Ran the SQL in your previous post, edited the table and added the cookie domain and now I'm able to login to the admin control panel :-)

Michael P · January 18th, 2005, 09:04 AM

If would have to be failing on this line:

if ( isset($ppboards) ) {

Which is simply asking if that variable has been set (which it would be with an old style config-inc.php). I'm wondering if the isset() is causing the problem.

criscokid · January 18th, 2005, 09:07 AM

Just want to check...

In the admin panel does the 'Debug Setting' now have two drop down boxes to choose from? (Same setting in PhotoPost only has one)
The 'Imaging Integration (IM or GD)' is a free text block but in PhotoPost it's a drop down box.

Michael P · January 18th, 2005, 09:14 AM

No, that's actually a bug. I've updated the adm-options.php in the current build to correct that issue. Thank you for pointing it out. If you grab the current build and upload the adm-options.php then it'll be fixed.

Michael P · January 18th, 2005, 09:35 AM

I have an idea on how to do the isset differently that should work better for everyone.

rastacat · January 24th, 2005, 06:47 PM

Just FYI:
ran into some of the issues mentioned. gave up and restored everything back to 2.02

Code:

Content visible to verified customers only.

++ plus a number of similar lines.

The classifieds came up afterwards, but no way to login - kept sending me in loops.

this was from 2.02 to 2.1

I'll try again in a week or so when the dust settles.

hope this helps.
Al

------
update.
found and reported a bug in the install after support provided the info about changing the database lines in 180-183 to get things working.
bb was going into the wrong field, was under paypal.