Thread

It’s hard to tell what’s causing the problem, I’d tend to look at your rewrites and see if those might be causing some of the issue.

As best I can tell, the rewrites are fine.

For whatever reason, EE will not serve the content in the defined index page.  Where in the code is the determination made that the 404 handler needs to be called?  I started tracing through the pvwebsys/core stuff but there is alot there. 😊

Also:

url.com/index.php - returns EE 404 (when I add a echo “testing”; exit;, however, the page is being called)

url.com/index.php? - returns EE 404

url.com/index.php?/ - returns EE 404

url.com/index.php?/sub-page - works.

Hence - if I can see why EE can’t locate the index template, we might be able to lock this thing down.

thanks!

Hi ssebner,

In your template preferences are you using Strict URLs?
Can you give your cache a good clean via the Control panel and also manually by FTPing into system/cache/ and deleting all folders in there bar the index.html and htaccess file

What was the nature of your DNS change?

<< In your template preferences are you using Strict URLs? >>
No, and when I changed this, it had no effect.

All cache has been cleared (via the control panel and also manually), but the problem still persists.

<< What was the nature of your DNS change? >>
We changed the second site’s domain from redirecting to a sub-directory in the first site to pointing directly to the second site (e.g.: from first-site.com/second-site-content to second-site.com).

Where in the code is the determination made that the 404 handler needs to be called?

ssebner,

It’s time that we go in and have a look at this in order to get you a solution. Please be on the lookout for an email form me.

Cheers,

Dan, our company will not let you have access to our live system. However, I can set up a live meeting (or we can get on Skype) and I can do all of the navigating while you troubleshoot. Is that possible?

Hi ssebner,

I do understand the concerns your company may have, unfortunately that will limit the level of service we are able to provide. We’ll have to continue to try to work this issue via the forums.

I appreciate you patience on this. When you are talking about your MSM set, is the site that is 404, the “first site” or “second site”? Did any paths or URLs change as a result of the DNS changes that were made?

Cheers,

<< When you are talking about your MSM set, is the site that is 404, the “first site” or “second site”? >>
The first site.

<< Did any paths or URLs change as a result of the DNS changes that were made? >>
No.

Dan, can you tell me where in the code the determination is made that the 404 handler needs to be called? (I started tracing through the pvwebsys/core stuff but there is a lot there.) I’ve posted this question a couple of times, but never received an answer.

Hi ssebner,

I’ve spoken with one of our Devs about this in order to get some insight. Usually we could have handed up to them, but that often requires them to be able to log in. So I’ve come back with some options that will help us shed some light on the situation from here.

First, I would like to directly address your question. The problem with the answer is “several places”. The logic to determine 404 is spread out among several ExpressionEngine core files, so it’s not something that traces directly back to one place. But I have an option that will help us get some information that might be more useful than bypassing 404 altogether.

The first thing we would like to do is have you edit your primary site’s index template. This is *not* index.php, instead it would be the template that is served when you access http://yoursite.com/ Open that template, copy out the contents to a safe place, a plain, offline txt file perhaps. Replace the template’s code with a simple phrase, “Welcome to our Site” for example. Just some plain text. This will allow us to eliminate any errors in the template code that might be causing the issue. Let us know if the simplified template outputs as usual or 404s as well.

The second option, which you can do in conjunction with the first, is we would like you to turn on template debugging. This can be found in Admin-> System Administration-> Output and Debugging: Display Template Debugging? set to “Yes”. Copy and paste the output after turning on that option. This will allow us to see everything ExpressionEngine is doing in order to render your template and can get us the info we need to see why it is calling a 404 vs. rendering your index page.

Thank you for your patience on this and cheers,

The plain text template still shows the 404 page, and two versions of the debugging code are attached for comparison.

1. home-page-debugging-text-root.txt
Obtained via http://www.yoursite.com/ (which shows the 404 page)

2. home-page-debugging-text-site-template.txt
Obtained via http://www.yoursite.com/site/ (which is the working home page template view—site/index)

Thanks, Dan. Hopefully this will shed some light on the issue.

ssebner,

Thanks for doing that, I know it isn’t exactly fun. I’ll run this up to our Developers and they should be able to provide some insight based on the debugging output.

Cheers,

Hrm- well instead of serving up site/index, it’s pulling pages/campaign to parse for that default.

Now- I tend to lean toward something getting hinky w/the DNS change, but I can’t for the life of me imagine what that would be.  So from a purely EE perspective- two things would generate the above:

1. Your settings for the defaults.  Just to double check what the system is seeing- create a blank template, turn php parsing on, put the following code in it and view the output:

<?php
echo $this->EE->config->item('template');
echo '
';
echo $this->EE->config->item('template_group');
?>

What do you get?

2.  You’re using the Pages module have a page with that url.  Which… seems highly unlikely.  But anyway, worth checking for the possibility.

You are awesome, Robin- this is now fixed! 😊

Turns out when we expired one of our pages, somehow the URI was changed to “/”. It didn’t even occur to me to look at the pages URIs.

Thanks bunches!!!