We’re getting this error, visible when viewing the site to any logged in user (not just superadmins). It is site wide :

Parse error: syntax error, unexpected ‘=’ in /home/valleyte/public_html/valmet_admin/core/core.template.php(3028) : eval()‘d code on line 1

We’re running on version 1.6.3, build 20080319

Test site is at www.valleytest.com/index.php

Greetings,

I’m not seeing an error, has this been resolved?

impdesigns, have you made any modifications to that file?

As a non-logged in user, I’m not seeing that message.

Since you are a build behind, can you upgrade to the most recent build? That would shake out any problems with that particular file.

I’ll update to the latest build and see if that resolves the issue. We’re moving our offices tomorrow, so can someone come out here to Raleigh and shoot me?

OK, just let us know how it goes

Just surfaced from the move and have noticed that you guys have released 1.6.4… I assume that will have any updated files that updating to the latest build would have given me, yes?

Yes. In fact, that is the latest build

Duh… sorry about that. I still have a “moving hangover.”

Total brain function should return in a day or two.

LOL- yea, moving will do that.  Let us know how it goes post-upgrade.

Hello,

We’ve upgraded to 1.6.4 and still have the issue… we also have more clues. First, the error message again:

Parse error: syntax error, unexpected ‘=’ in /home/valleyte/public_html/valmet_admin/core/core.template.php(3057) : eval()‘d code on line 1

Now the extra info:

It seems to only manifest itself when two of us are logged into the same admin account. It will display on the second logged in machine. It only appears on templates that are NOT index pages (for the purpose of preserving the existing site’s URL structure, each section of the site has it’s own template group).

Good news: the client doesn’t see it.. we’ve given them unique logins. Doesn’t seem to “hurt” anything… it’s just freaking us out. Another bit of info… this site has a… what’s the technical term…. oh… BUTTLOAD of entries.

Hee- just noticed you’re in Raleigh.  I’m in Greensboro!  Hardly ever notice folks from the Carolinas on here.

And you bring us such fun questions.  The error makes no sense to me.  Do you have any php in the templates- particularly something that would only be on non-index templates (perhaps a conditional so it only happens there).  This isn’t the error I’d expect for that- and the whole bit about showing on the second logged in machine is… no idea on that.  But good debugging on figuring out the weird circumstances that trigger it.

Oh- anything extra going on in either the main index.php file or path.php- custom code, anything?

Greensboro! Awesome! We love EE… have a TON of sites on it, but this is the largest by far. We got this contract specifically because the principals involved saw the SXSW presentation and they were knocked out by EE. They found us on the Pro Network section of the EE site…

I’ll check into all these things… it’s very strange indeed. As I said, it doesn’t seem to adversely affect anything. But the error warning is freaky and makes us nervous as we’re targeting a “soft launch” for next weekend.

Hee- glad you’re enjoying it.  And yea, little quirky errors like that just bug.  We should be able to track it down- but it’s just odd.

Let me know about the php/etc when you have a chance to look.

-edit- Nevermind, apparently I misunderstood what you guys were talking about.

Just doing some housecleaning- and wondering- if you put up a non-index template with nothing but ‘this is a test’ on it- do you still get the error under the dual-login situation on that template?  If not- and you are getting it on the other non-index templates, it would give us a hint.