View Full Version : Error when attempting vb3 header
July 11th, 2004, 01:08 AM
I was able to update from 4.7j to 4.8d with only the loss of my style sheets and headers so thought I would attempt to integrate to my vb3 header which I was unable to do with 4.7j because of broken images. Now if I edit the path in the header-inc.php file it produces the error
Fatal error: Failed opening required './languages/english/pp-inc.php' (include_path='.:/usr/share/pear') in /var/www/html/photopost/pp-inc.php on line 63
Thanks in advance for any suggestions.
July 11th, 2004, 07:47 AM
I have the same problem, but with a fresh install.
running vB 3.02 and the latest photopost. Have checked the paths and both are correct.
July 11th, 2004, 07:57 AM
Kesomir, I am running vB 3.03 if that helps figure this out. I think the 3.02 and 3.03 update came out the same day so they may be very similar.
July 11th, 2004, 08:52 AM
v-rodforums, found a fix;
open your config-inc.php file,
find the line $PP_PATH = "";
and hard code in the path there, eg;
$PP_PATH = "/home/user/public_html/gallery";
make sure theres no trailing /
July 11th, 2004, 09:13 AM
Kesomir that didn't help me, it led me to a complete new set of errors. Not sure why I ever try to update PP, it seems like a major ordeal and hundreds of errors to work out every time. I may just try to reload 4.7j that I finally got working and just forget it.
July 11th, 2004, 09:59 AM
The PP_PATH is the correct fix.
In a fresh install it tells you to input the path to Photopost right from the beginning. nothing may work on some servers.
In the upgrade instructions it tells you that if you have an older version you may need to add the variable into the config file.
I have upgraded many many versions of Photopost from 3 to 4.8 etc and there are not 100's of errors as long as the upgrade instructions are followed.
July 11th, 2004, 10:17 AM
The problem I have atm is trying to find where I can change the relative path for the stylesheet.
There is a call from the vb template headinclude -> $style[css] but I can't track it down to put the full path in there.
Any help on this one?
EDIT :: have hard coded the stylsheet for this theme for now, but being able to alter wherever the $style[css] call is made to would allow style changes to be made without breaking pp.
July 11th, 2004, 10:55 AM
Well Kesomir this is VBulletin your talking about. We have no control over how they code their program
We have a thread linked in just about every forum with VB integration facts. It notes VB's use of relative paths and how a user needs to correct the paths to use the VB header include.
Now as far as the stylesheet same thing apply's. Photopost is compatible as long you correct where ever this is defined. We have yet to see where this is defined. If you correct this path statement in $style[css] in VB yes it would work. I tell most people to use inline CSS instead of the file based since inline allows the style to be loaded in the head part.
If you find out in what phrase file etc the VB link statement is coded please do let us know and I will add it to the VB Integration FAQ
July 11th, 2004, 11:00 AM
omegatron, don't take it personal. I am not a programmer nor do I write any kind of code but really you should try to follow the directions supplied with your software sometime. They have got to be some of the most difficult to follow directions that there are.
"2) Upload all files - except config-inc.php, unless you modified it from the ZIP file - to
your server. You do not need install.php for an upgrade."
After reading that I did not upload the new config-inc.php file. Maybe it could be written with a little greater degree of accuracy
I didn't count the exact number of errors that I get I can tell you that upgrading from vb2-vb3 left me with zero errors and it is a much larger program and every update since left me with zero errors. Every time I attempt a PP upgrade it seems like it takes day's to work all the bugs out. Is it just me or is that the same thing I read here on these forums. Like I say don't take it personal, rather take it as a suggestion that no matter how good a program is if the instructions are poorly written the odds are many more problems will follow. Just my 2 cents.
July 11th, 2004, 11:34 AM
No one's taking anything personal my friend. ;) Just stating my 2 cents just as you did. I have done many many photopost upgrades.
The only thing I am noting and am saying is that you skipped right past the first step in the upgrade.txt upgrade instructions
1) Check for new config-inc.php variables, some recent additions are: BLAH BLAH BLAH
If you want a blow by blow change then the changedfiles.txt in the documentation folder have a blow by blow change.
Then of course the 3rd step is to run any applicable upgrade scripts from the version you are running to the current version. If all the steps in the upgrade.txt are followed a user should not experience a problem upgrading.
The issue you posted above was caused by not following step 1 of the upgrade instructions and is solved by going to the photopost admin section in the config and adding your path to photopost which is /var/www/html/photopost
July 11th, 2004, 11:40 AM
Sorry I went back through those instructions and still have multiple failures. No one blew past any step my friend, it seems the steps contradict each other so much your not sure which ones to follow and which ones to ignore. Just stating the point of someone that didn't write the software.
July 11th, 2004, 12:35 PM
Well no problem that is why I am here ;)
It was obvious from your original post step one was not done. That is what I said that the $PP_PATH variable is indeed the correct fix for an error that you posted and the other user in this thread posted he had and he indeed found it out.
I went to your site and see no errors with Photopost but then I dont see you using the header-include so I can not point you in the right direction to get it working.
As long as you place the right paths in the header-inc file and have the PP_PATH variable filled out you should have no problems.
You might want to also as a suggestion read the VB3 Integration FAQ thread at the top of this forum as if you use the header-include you need to correct some relative path issues in some VB3 templates.
July 11th, 2004, 12:53 PM
I no longer get broken images, what I get are script errors now. I will leave the gallery using the vb header for a few minutes if you want to take a look at the errors I receive.
July 11th, 2004, 01:41 PM
Okay well your errors have nothing to do with Photopost ;)
I had a feeling this is what you were referring to. I notice you have not put the header-inc up yet but I know exactly what your errors are.
Okay when using the header include for VB you need to do the following steps. This is outlined in the VB Intergration FAQ I referred to
1. Fill out Photopost header-inc.php with paths to forum and photopost. UPLOAD
2. In VB admin TEMPLATE EDITOR. Edit the VB header , header-include , footer and navbar to replace the relative paths
example href="profile.php" to href="http://www.v-rodforums.com/forums/profile.php"
3. In you main style editor you need to edit any image calls for gradients and such in the actual CSS to put the full url in as an example
url(images/blah.jpg) to url(http://www.v-rodforums.com/forums/images/blah.jpg)
July 11th, 2004, 01:52 PM
Everything you mention is done, I had to change it back because it was so annoying. If I had known your were going to take a look I would have left it but after a half hour of errors and emails from members about errors I just put the original header-inc.php file back.
July 11th, 2004, 02:21 PM
Well the problem is I was not sitting here at the computer waiting for a reply.
I have PM'd you if your around now go pop it up. Its 3:17 and I will stick around a few minutes although I might pop out back to smoke a cig I will be around and see if we can spot what the culprit is.
July 11th, 2004, 02:30 PM
I have PM'd you back. Thanks for putting up the header-inc
Your problem is the relative paths in the VB templates I meantioned. All relative paths in the templates meantioned need to be full url's. This should not affect anything else in VB and as I PM'd you I would be more than happy to assist.
July 11th, 2004, 03:19 PM
omegatron thanks so much for your help, you were correct it was just my lack of understanding that was keeping me from correcting the needed files. Thanks again.
July 11th, 2004, 03:57 PM
No problem glad to help
vBulletin® v3.8.1, Copyright ©2000-2014, Jelsoft Enterprises Ltd.