[The M.I.P.]

Hi Toxin,

Originally Posted by toxin

My website directories are:

DOC ROOT: /home/httpd/vhosts/mydomain.com/httpdocs/
VBULLETIN: /home/httpd/vhosts/mydomain.com/httpdocs/forums/
PHPADSNEW: /home/httpd/vhosts/mydomain.com/httpdocs/adserver/

so I have used /adserver as the path in the vBulletin Server Settting and Optimization.

since version 1.0.1 of this plugin, the path to a local phpAdsNew is a "normal" filesystem path.
So in your case, the correct setting in vBulletin options is either /home/httpd/vhosts/mydomain.com/httpdocs/adserver or ../adserver. I'd prefer using an absolute path (the former one), even though a relative one (the latter one) is easier to type.

@Xstreamist:
I currently have no time to check, but I'll have a look at it after weekend.

@djsydeburnz:
When logged in as phpAdsNew admin, you have to add appropriate rights (zones, etc.) to the client. Please have a look at the excellent phpAdsNew handbook.

@Triple_T:
Regarding the temporary solution, have a look at lines 25,26 of your attached inc_features.php.
Fill in the DB settings of your Photopost database (or your vbulletin database when Photopost tables are inside vBulletin database; in line 25 replace $dbuserid with your db username, $dbuserpassword with the db password and in line 26 pp_database with the correct db name) and uncomment these lines in your original inc_features.php.
This makes Photopost use a separate db connection and should solve the problems you mentioned above.
I'm still trying to get my hands around a recent Photopost version to be able to check it out and present a clean solution.