I'm stumped. I'm not so sure what is the answer to that question. I'll do some Googling and get back to you if I bump into an useful answer. You should email the people at iContact as they probably could help you..
Thanks very much for the input. The following happens (suggesting you are on the right track): now it shows:.
Warning: require(includes/functions/compatibility.php) [function.require]: failed to open stream: No such file or directory in /home/vhosts/...../...../htdocs/shop/includes/application_top.php on line 40.
Fatal error: require() [function.require]: Failed opening required 'includes/functions/compatibility.php' (include_path='.;./includes;./pear') in /home/vhosts/...../...../htdocs/shop/includes/application_top.php on line 40.
Again, file compatibility.php is there in the functions folder. In application_top it reads:.
Require(DIR_WS_FUNCTIONS'compatibility.php');.
Any more hints??.
Thanks...
Unfortunately, I am still stuck on the same problem. Any more ideas anybody??..
Well, I hesitate to have you change DIR_WS_FUNCTIONS to 'functions/' (from 'includes/functions/'), as that as may break something else. What you might try is in application_top.php, change.
Require(DIR_WS_FUNCTIONS'compatibility.php');.
To.
Require('functions/''compatibility.php');.
The same "hard coding" of the path may unfortunately have to be done in a number of other places in application_top.php, as well as any place else where calls to includes/... are made from a PHP file.
In.
Includes/..
Has anyone gotten any official word from PHP on changes in handling "current directory"? I find it hard to believe that such a major change would be made in PHP behavior without it being at least documented...
Thanks so much for sticking with me on this one, Phil!.
Now I at least have some action again, but have to rewrite column left an right to see what happens next. Will update later what happens!..
Now I can wrap up this topic - if anyone ever reads this, it might be helpful..
My provider answered (again) regarding this problem and wrote today: please check again - there was a mistake in the php.ini!.
(which I cannot access myself)..
Shop is healed. All is well..
Thanks again Phil...

