Moving EE between QA servers and experiencing an issue. The CP loads right up without issue. Can go straight to the home page as well (which is not managed with EE). However, when going to the blog channel (currently the only content we have managed with EE) the page gets stuck loading and never displays any content or errors. The loader in Safari's address bar just stop at about 10% and never loads.

Suggestions on places to look for issues? I've double/triple checked all paths and everything looks correct.

  • This looks like a infinite loop on a .htaccess file. Can you, please, update your answer and show the redirect and rewrite rules on this file? – Robson Sobral Aug 13 '13 at 0:18

If you go to (domain_name)/index.php does the page load? If this works I would suggest looking at your .htaccess file (supposing your server runs Apache), making sure it was copied correctly and nothing needs to be changed.

UPDATE: Since you say your page does finally load but after a crazy number of seconds, I recommend you try the following steps to troubleshoot your issue.

  1. Install EE Debug Toolbar;
  2. In the control panel, go to Admin>System Administration>Output and Debugging and turn on "Display Template Debugging?";
  3. Reload your front end page (while still logged in to the control panel as super admin);
  4. Use EE Debug Toolbar to identify any pain-points. The toolbar will show you the total template rendering time in the fifth box, and query execution time in the last box. Clicking on either will give you more detail.

EE Debug Toolbar's GitHub readme page gives you a high level idea of what the toolbar looks like and how it works.

Try these steps, see if it doesn't point out anything obvious to you, and if you have more symptoms but no answers, update your question so we can troubleshoot further. Best of luck!

  • So it just started loading but takes upwards of 45 seconds. When loading with the Network tab open in the inspector I see that "blog" takes at least 98% of the 45 seconds, then all assets (images, css, etc.) take the rest. – Brandon Durham Aug 12 '13 at 20:41
  • I've updated my answer with more steps you can try, given this new information. – Tim FitzGerald Aug 13 '13 at 14:27

Did you change all the server paths? Assuming they differed between the servers.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.