ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Error, but only for Super Admin, when logged in on front end

February 04, 2010 9:59pm

Subscribe [6]
  • #1 / Feb 04, 2010 9:59pm

    kstatham

    52 posts

    Hi,

    I only found a few cases of this error in the forums, and none of the causes for those cases appears to be the one I’m experiencing. Here is the error:

    Warning: Unexpected character in input: ''' (ASCII=39) state=1 in /home/xxx/public_html/xxx/core/core.functions.php(634) : eval()'d code on line 86

    This site has been online for a couple years now, and I recently updated it with no problems (about a week ago). The error didn’t appear until this morning (99% sure). I noticed after installing pi.cal_saef, but I’m not sure that’s what caused the error. When I uninstalled that plugin, the problem didn’t go away.

    The weird thing is, it’s only when I’m logged in as a super admin. If I login as a regular member, or don’t login at all, no errors.

    Thanks in advance for any help,
    Ken

    By the way, EE version 1.6.8, Build 20091002

  • #2 / Feb 05, 2010 2:03am

    John Henry Donovan

    12339 posts

    Ken,

    What other third party plugins or extensions do you have installed?

  • #3 / Feb 05, 2010 12:18pm

    kstatham

    52 posts

    Thanks for the help. Here are my extension and plugin lists:

  • #4 / Feb 05, 2010 12:44pm

    Ingmar

    29245 posts

    Can you try to disable your extensions globally for testing? See if that makes a difference.

  • #5 / Feb 05, 2010 12:50pm

    kstatham

    52 posts

    I’m happy to try that, but first, I have several fieldframe fields that are critical to the site… are they going to be gone when I disable Fieldframe? I’ll need to backup the database if that’s the case, but if it’s not, that would be great.

  • #6 / Feb 05, 2010 12:57pm

    Ingmar

    29245 posts

    You should definitely make a backup, just in case. That said, if you use the “big green button” to disable all extensions at once, individual settings should be kept. It’s only when you disable extensions one by one that their preferences and data are erased.

  • #7 / Feb 05, 2010 1:32pm

    kstatham

    52 posts

    Ok, thanks Ingmar… working on that now.

  • #8 / Feb 05, 2010 1:40pm

    kstatham

    52 posts

    Nope, no luck… the error is still there. I was able to successfully reenable extensions, so thanks for that bit of advice… I can disable them again if necessary.

  • #9 / Feb 05, 2010 1:41pm

    kstatham

    52 posts

    I do see some old plugins and extensions… I’m going to start updating them and removing some that I don’t think I need and see what happens.

  • #10 / Feb 05, 2010 3:09pm

    Sue Crocker

    26054 posts

    Let us know what you find out. We’ll be here.

  • #11 / Feb 05, 2010 5:21pm

    kstatham

    52 posts

    I’m back… I’ve removed a few plugins and an extension, but I’m still getting the error. I’m not sure what else to try. I guess the good news is, the site is functioning fine other than this, and since I’m the only one seeing it, I’m not too worried about it, but I’d sure like to figure it out and get it fixed.

    Thanks again for the help!
    Ken

  • #12 / Feb 05, 2010 7:53pm

    Adam Dorsey

    1439 posts

    Where exactly does this error appear?

    It wouldn’t hurt to upgrade EE to the latest build, to rule out file corruption, and we usually recommend upgrades for bug fixes and security updates anyhow.

    Thanks!

  • #13 / Feb 06, 2010 4:46pm

    kstatham

    52 posts

    Hi Adam and all the other people who have been helping me,

    The error was at the top of the page (before the doctype declaration).

    But the error is gone.

    Since the error was only showing up for me, as a superadmin, I decided to just wrap up my site updates so I could get paid. So, I was working on the SAEF for the calendar, and something I did made the error go away.

    I added a jquery datepicker (which I’m still working on), and updated the version of jquery in the head, but that’s basically all I’ve done.

    This is confusing.

    I do plan to update to the current version of EE as soon as I get paid for this job.

    Thanks, and I’ll let you know if anything else strange happens.

  • #14 / Feb 06, 2010 5:19pm

    Greg Salt

    3988 posts

    Hi kstatham,

    Glad that you got the problem sorted. Please post back if required.

    Cheers

    Greg

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases