Thread

When I go to the EE admin area, I’m not able to log in (I know my username and password are correct). The problem is related to the fact I’ve just switched servers. But I don’t know how to solve the problem and it’s urgent that I do. I’m presented a log in box but with this text near the top:

Warning: include(http://www.tickerville.com/amember/plugins/protect/php_include/reload_if_cookie.inc.php) [function.include]: failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /mnt/target02/341565/341577/www.tickerville.com/web/content/tvsystem/index.php on line 3

Warning: include() [function.include]: Failed opening ‘http://www.tickerville.com/amember/plugins/protect/php_include/reload_if_cookie.inc.php’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /mnt/target02/341565/341577/www.tickerville.com/web/content/tvsystem/index.php on line 3

I recently switched servers and am wondering if I’m making a common mistake. I’ve check the server and the file ‘reload_if_cokkie.inc.php’ exists. I’m using amember and the filename suggests a connection with amember, but amember’s support says it isn’t anything to do with their files. Also this used to work on the old server, something got screwed up in transit (I’m guessing). Any idea?

Any help is appreciated as it’s urgent that I get this in working order today.

TIA

Sam

Those are definitely not ExpressionEngine files, if you download EE you’ll not find them anywhere.  From the 403 forbidden, though, it sounds like it can find them, but not load them.  If you put a simple image or some such in that directory (the one in the first error), does it let you visit it?

While I do not use aMember, since they say it’s not their own file; yet it is in the plugins directory for the system; I’d imagine it is a third-party aMember plugin.  YOu’ll need to locate the plugin author (try opening the plugin file and see if there is contact information at the top?) for help.

In short, while I am doing my best to help, this is definitely not an ExpressionEngine file or issue. =)

Thanks Lisa,

I wanted to post the eventual solution.

The problem stemmed from my implentation of a solution documented here http://expressionengine.com/wiki/aMember_Integration/ that I used to in order to make EE and aMember ‘remember’ my members when they log in. If you don’t use this fix then your members can’t be ‘remembered’ even if they check the ‘remember me’ checkbox. The problem was when the tutorial said to do the following I didn’t use a relative path:

// the next line is to call the aMember system to load the login
include “path_to/amember/plugins/protect/php_include/reload_if_cookie.inc.php”;

Keep in mind this edit is for the index.php file. I probably don’t even need it for the admin index.php file, but for whatever reason I added it. I wasn’t aware what the “path_to” part would be, so I used an absolute path. This is what caused problems after the server move. Not sure why but an absolute reference worked on the old server but not on the new server.

<?php

include 'http://www.tickerville.com/amember/plugins/protect/php_include/reload_if_cookie.inc.php';

error_reporting(0);

$pathinfo = pathinfo(__FILE__);
$ext = '.'.$pathinfo['extension'];

require './core/core.system'.$ext;

?>

and now the new code using a relative url for the include

<?php

include '/mnt/target02/341565/341577/www.tickerville.com/web/content/amember/plugins/protect/php_include/reload_if_cookie.inc.php';

error_reporting(0);

$pathinfo = pathinfo(__FILE__);
$ext = '.'.$pathinfo['extension'];

require './core/core.system'.$ext;

?>

so apparently on the old server, the absolute url path was okay. But on the new server, a path relative to the server’s own structure was required. It’s amazing how little details like that can derail a person’s weekend 😊

Sorry it jammed your weekend- but very glad you shared the fix.  (Could be a difference in allow_url_fopen setting- though that is a guess.)

qman,

I almost hate to post this, but sorry I didn’t see that saturday.  I ran up against this about a month ago and wasted an hour or so before I remembered that I edited that line in the index.php file. 

Just an FYI.  You do not need that in the admin index.php. 

Regards,

Rick