Thread

Hey bgarrant,

I know that you are on Windows. Checking in with kirkaracha.

Thanks,

Hey kirkaracha,

Believe it or not, Apache can run on windows. 😊

I just want to make sure that you are on Linux and not Windows.

Thank you,

I just sent you the details requested Shane.

I’m on Linux.

Same here. I’m on Apache.

K- I took a look at bgarrant’s install- let me lay out what was happening there.  Let us know if it did or did not fit your problem.

Site was setup fine- was off-line, tool bar should have been showing in publish.  I took a look at the error console and see that the action request that should be pulling in the toolset javascript is instead pulling back some simple text ‘The site is offline’.  Aha.  K- the link to that JS is using an action request- meaning it looks like:
http://www.domain.com/?ACT=23&cp=y&toolset_id=0&etc;......

The site was using htaccess to remove the index.php from the url- and thus in ‘Admin- General Config’, the field for the site index file name was left blank.  And because the site was off line- it was also set up to have an index.html file that showed an offline message.

Most servers are configured so if you go to http://www.domain.com they will show the index.html file contents by default.  Which is exactly what was happenig.  And that action request?  Was… pulling up the index.html page.  Which is just a static html page with ‘The site is offline’ on it.

Make sense what’s happening?  The action request should be pulling back a bunch of javascript and it’s not.

Short term fix is easy- add index.php as the site index file name in ‘Admin- General Config’- at which point the generated action request will look like http://www.domain.com/index.php?ACT=23&cp=y&toolset_id=0&etc; - which will pull back a bunch of javascript.

If the site defaults to pulling back index.php by default- then there would have been no problem.  But since it was pulling back index.html, the action request wasn’t pulling back anything.  So short term- add the file name or remove index.html (so it will default to index.php) and use a system message to display the ‘under construction’ message.

And let’s see if that cleared things up for anyone else.

K- I took a look at bgarrant’s install- let me lay out what was happening there.  Let us know if it did or did not fit your problem.

Site was setup fine- was off-line, tool bar should have been showing in publish.  I took a look at the error console and see that the action request that should be pulling in the toolset javascript is instead pulling back some simple text ‘The site is offline’.  Aha.  K- the link to that JS is using an action request- meaning it looks like:
http://www.domain.com/?ACT=23&cp=y&toolset_id=0&etc;......

The site was using htaccess to remove the index.php from the url- and thus in ‘Admin- General Config’, the field for the site index file name was left blank.  And because the site was off line- it was also set up to have an index.html file that showed an offline message.

Most servers are configured so if you go to http://www.domain.com they will show the index.html file contents by default.  Which is exactly what was happenig.  And that action request?  Was… pulling up the index.html page.  Which is just a static html page with ‘The site is offline’ on it.

Make sense what’s happening?  The action request should be pulling back a bunch of javascript and it’s not.

Short term fix is easy- add index.php as the site index file name in ‘Admin- General Config’- at which point the generated action request will look like http://www.domain.com/index.php?ACT=23&cp=y&toolset_id=0&etc; - which will pull back a bunch of javascript.

If the site defaults to pulling back index.php by default- then there would have been no problem.  But since it was pulling back index.html, the action request wasn’t pulling back anything.  So short term- add the file name or remove index.html (so it will default to index.php) and use a system message to display the ‘under construction’ message.

And let’s see if that cleared things up for anyone else.

Thanks Robin.  The toolbar is showing now.

Hey bgarrant,

That’s awesome. Is there anything else we can help with?

Cheers,

Hey bgarrant,

That’s awesome. Is there anything else we can help with?

Cheers,

I just need help with that weird paste issue: http://ellislab.com/forums/viewthread/216920/.

It looks like it is placing a
in place of some spaces.  Really strange behavior.  Does this happen to you when you test it?

Hey bgarrant,

We like to keep each issue separate, so I will respond to that thread in the order it was filed.

Thanks,

Toolbar is not showing yet, but the file Robin mentioned is loading fine.

Thanks!

Using Firebug, I found that this request is loading forever.

<a href="http://domain.com/renamed_admin.php?S=0&D=cp&C=content_files_modal">http://domain.com/renamed_admin.php?S=0&D=cp&C=content_files_modal</a>

Is this?

Still having the same issue.  Any help would be greatly appreciated.

Hi all,

Just updating this thread to let on lookers know that we are working offline with Robson and bgarrant. We will post back here when we have more!

Cheers!

Let’s see- I believe Robson should be squared away.  For others running into this issue- check if this may be the problem.

The problem has to do with a couple of configuration settings:

1. Show PHP errors was set to ‘none’- which is discouraged.  The site shouldn’t be throwing php errors and if it is, it’s better to know it and fix them.  I’ve switched it to ‘1’, so errors only show for logged in superadmins.  Leaving it set to ‘1’ solves the problem.
2. The $config[‘remove_unparsed_vars’] = ‘y’; setting in the config file.  IF errors are set to 0 AND that configuration is set?  It can strip out valid javascript if the javascript matches the pattern of an EE tag.  Which is what was happening here. 

So- either setting error reporting to 1 OR setting remove_unparsed_vars to n fixes the problem.  It’s not really a bug as the system is acting as it’s supposed to.  But it is one of the reasons running with errors completely suppressed is a bad idea.

Make sense what was going on there?  Basically, the javascript for the RTE was getting mangled due to the settings.  What I’d strongly recommend is keeping error reporting set to 1.

Anyone still having issues with the toolbar showing?  Double check your config to see if this might be the issue.  For the error reporting setting- you can check in ‘Admin- System Prefs- Output and Debug’.

And if anyone is still having an issue after that?  Let us know.

Hi Robin,

have a clean install of 2.5. We have index.php removed in Admin -> General Configuration as we’re removing index.php from our urls

Have checked the php errors and they are switched to 1 in Admin- System Prefs- Output and Debug

Am i missing anything else?