Thread

Keep the setting that is working for you.

So are we OK to close the thread?

Actually I’d like to get this working without having to keep a modified index.php.  Can you go to Admin -> System Preferences -> Output and Debugging and let us know what your Error Reporting level is?

I do not see a choice for Error Reporting.  Here are the settings:

Generate HTTP Page Headers?
  Yes    
Enable GZIP Output?
When enabled, your site will be shown in a compressed format for faster page loading
    No  
Force URL query strings
This is a safety mechanism for servers that do not support the PATH_INFO variable.
    No  
Redirection Method
      Location  
Debug Preference
1. PHP.SQL error messages shown only to Super Admins
 
Display SQL Queries?
If enabled, Super Admins will see all SQL queries displayed at the bottom of the browser window. Useful for debugging.
      No  
Display Template Debugging?
If enabled, Super Admins will see a list of details concerning the processing of the page. Useful for debugging.
    No

Yes my apologies, Debug Preference was the one I was after.

1 is a good setting there.

To confirm where we are at - if you upload a fresh copy of the default index.php, then when you login to the Control Panel, you get a blank page, even with extensions disabled?

Hello, I have not had a chunk of time to participate in the testing process once more, but will do so as soon as possible.  It is appreciated that you keep this thread open till then.

No worries.  Let us know you can answer Lisa’s questions above.  We’ll be here.

-greg

Hi again folks, I’ve been finding time to troubleshoot whether a fresh index.php file would work for the blank page on login problems we’ve been having with this site.  Just when I’ve cleared off the time to to this, the client gets in touch with me today to let me know that TinyMCE is no longer working.  I know I’m establishing multiple issues in one support request, but I’m mentioning that now because I’m going to start testing the index.php and log in issues, and can’t help but wonder if these two things are (somehow) related.  The only extensions I’m running are LG TinyMCE (with TinyBrowser) and TinyMCE Communicate.

OK, I’m going to run another test by uploading the fresh index from my downloaded 1.6.8 files, and I will let you know the results.

Hi again, I just disabled extensions, and uploaded the fresh system/index.php file. 
It’s working so far, I logged in and got access.  That’s great.  I’m going to enable extensions and report back.

OK, enabled extensions, and logged out, logged back in - works fine.

So, good.  The log in problems are gone, and I’m using the clean index.php file.

LG TinyMCE, TinyBroswer - still not working (TinyMCE not showing up at all).  I realize this might be a discussion on another thread.  However for testing sake - I’m going to give turning on error reporting a try and see if that works as well… and if it offers any insight into these issues while I’m at it.

Hi again, error reporting turned on and log on still working.  LG TinyMCE and TinyBrowser still not working. 

No php errors showing, I’m getting the same javascript error messages I got last time around:

Line 2344
tinyMCE is undefined.

I guess I’ll uninstall and reinstall the extension again - worked last time.

One quick question related to all this while the thread is still open - can any of this be related to cacheing?  I’ve checked out the options for emptying caches etc in the EE Admin and I don’t fully understand them and would appreciate insight.  I can’t figure out how errors are happening when I am in a period of not changing any files, or when there have not been changes on the server, and was thinking that cacheing could be related somehow?

Thanks so much, for answers on this thread, you have been very helpful.

Hi charmedworks-

Here is a good breakdown on how EE’s cache system works:
http://expressionengine.com/docs/general/caching.html

Also, we don’t offer support on third-party extensions (LG TinyMCE and TinyBrowser), but do let us know if you get the problem resolved.

Hi, ok looks like cacheing isn’t related to the issues in this case but thanks for the info!

I reinstalled the LG TinyMCE, from fresh files, and all is well again with our site.  I’m turning back over the client.

Thanks again for everyone’s assistance here.

Whew! Glad you were able to figure out what the problem was. Don’t hesitate to post again as needed.