View Full Version : VBHome Lite problems...
MotownLF
05-24-2003, 11:25 PM
Warning: main(./home/xxxxx/public_html/dev/forums/admin/config.php) [function.main]: failed to create stream: No such file or directory in /home/xxxxx/public_html/dev/global.php on line 744
Fatal error: main() [function.main]: Failed opening required './home/xxxxx/public_html/dev/forums/admin/config.php' (include_path='') in /home/xxxxx/public_html/dev/global.php on line 744
I get this error when I put it on the subdomain.
How do I fix this?
filburt1
05-25-2003, 12:06 AM
Don't put it on the subdomain. :)
Seriously...it's because it can't find the vB files.
MotownLF
05-26-2003, 03:41 PM
So there is absolutely no way that this thing works with the forum in the subdomain?
Which presents a problem. Cause my forum IS on a subdomain.
So here is the question.
If I put this VBHome Lite in a top level directory, it's still going to error because the forums are in a subdomain?
DaveG
05-28-2003, 02:14 PM
I'm getting some pretty crazy errors this morning after my server admin changed a line in the php.ini file.
I am using webtemplates, but none of them are working now! The admin has since reverted to the original php.ini file, but all my nonVB webtemplate pages are giving me the following errors. here is an example from www.SprintUsers.com/news/index.php :
Warning: main() [function.main]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /home/sprint/public_html/news/index.php on line 8
Warning: main(http://sprintusers.com/forum/show.php?pg=news) [function.main]: failed to create stream: Resource temporarily unavailable in /home/sprint/public_html/news/index.php on line 8
Warning: main() [function.main]: Failed opening 'http://sprintusers.com/forum/show.php?pg=news' for inclusion (include_path='') in /home/sprint/public_html/news/index.php on line 8
Line 8 in my index.php file reads as follows:<?php include("http://sprintusers.com/forum/show.php?pg=news");
Any ideas? Help!
DaveG
DaveG
05-28-2003, 02:48 PM
Strangely enough, a Cpanel upgrade on my server resolved the issue.
I still wonder what went wrong here...
vBulletin® v3.8.12 by vBS, Copyright ©2000-2025, vBulletin Solutions Inc.