EE 3.3.2 Error on fresh install

What version of PHP are you running?

version 5.4

Should be okay as EE3 if 5.3.10 and up To explain. when logged in as admin, the frontend will then show error messages - these will otherwise be supressed for non admin people. This is of course for security as it could reveal information to them. That is why it displays when logged in.

You have two errors. The second is only caused because of the first error being thrown. so ignore that for now. When looking at the first error - i found:

http://expressionengine.stackexchange.com/questions/37546/ee-3-3-3-error-cannot-modify-header-information

I would suggest following that and seeing if what they advise helps. N

Thanks for the clarification on why the error only appears when I’m logged in; that makes total sense.

I’ve reviewed and tried the fixes on the link to no avail. It doesn’t seem like the problem can be a template specific issue (as suggested in the link) because this is the default template which should be setup to work, right?

This is a fresh-fresh install that I’m working with because I was trying to diagnose the error mentioned above. Under the previous install (on the same shared hosting plan) I was receiving the error mentioned about as well as periodic errors when I try to do other operations through the admin interface such as deleting custom field sets even though the operations would actually complete. I can’t reproduce that error at the moment but it seems to suggest that there is something wrong with the installation package or something is wrong with my server side setup.

Ive just fired up a test install and had no issues my self. Tried across a few different version of PHP without issue. Have you tried the EE test script to see if that identifies any potential issues in the hosting setup?

https://docs.expressionengine.com/latest/installation/requirements.html#server-compatibility-wizard

I get the same error, whether I run a fresh Core 3.3.3 install under MAMP, or from my host (Gigahost.dk) who allow me to set everything, that has to do with PHP and so on. So I run PHP 7 on both, after reading this.

The error refers to line 1876 in DB_active_rec.php which has to do with creating the ‘select’ portion of a query.

Also, the log-in form expires very quickly, and you’ll need to do as described below, to be able to log-in again.

What works is: Removing all cookies from your browser, for example cookies from Firefox and all “Website Data” as it’s called in Safari, displays the site just fine.

However:

• For the back-end you’ll need to go back to the base back-end URL, without everything after /admin.php and log-in again, then it works.

• The home-page however, works after removing cookies, here you just need a refresh.

So something to do with older cookies from the site you’re developing, throws this error. Is this a bug, or are we not seeing it’s purpose? Some people advice you to out-comment the slider on the home-page, but I found that clearing cookies/website data did the trick.

It’s an annoyance for someone who’s been away from EE for some time, because I was waiting for version 3 to base future sites on, to find these errors, especially since we’re at version 3.3.3 and not 3.0 beta ;-)

Anyways, I think you guys need to take a look at this bug, if it is a bug, because google is flooded with many, many strange ways to get around it.

Thank you anyways for creating EE 3 - can’t wait to read the manual and learn all the new goodies!

Love, Thomas

PS: If you’re not fast enough writing your forum-post, after some minutes this form will also expire, so make a copy of the text before you press Preview or Submit, or your writings will be gone. I learned this the irritating way :)