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.

Issue with 1.6 to 2.5 upgrade: multiple syntax errors

September 04, 2012 4:45pm

Subscribe [1]
  • #1 / Sep 04, 2012 4:45pm

    ShueLace

    1 posts

    I really could use a hand trouble shooting a few issues with my live site that I need to get functioning again.  Post disclaimer; I am not a developer and code troubleshooting is beyond my capabilities, but I am the only one available with the keys to our company site and it needs fixed nonetheless.  The site was built by a third party in 2008 using EE-core 1.6. and our Media Temple server recently migrated to PHP 5.3. I learned (quickly) that I needed to install a new, current version of EE. (Somewhat reassuringly, I can see that I am not the first to have dealt with this similar issue.)

    Followed the steps from ‘Upgrading from 1.x to 2.x’ and was again able to login to the EE control panel after a successful install,  so I am using EE v2.5.2 w/ build of 20120606. I needed to fiddle with changing a few files and paths, as the original developer had changed the system folder to something else.  I matched the file naming, and several sub pages are now visible and active, but not all of the text is displaying properly on all pages.  In addition, there are several key significant issues that are readily visible (and hopefully none that are obscured from view):

    The home landing page throws the following error

    Error
    
    The following tag has a syntax error:
    
    {exp:markdown}
    
    Please correct the syntax in your template.

    And one sub page displays the following syntax error.

    Error
    
    The following tag has a syntax error:
    
    {exp:trunchtml}
    
    Please correct the syntax in your template.

    I have searched both of these errors in the forum and have not found a similar instance with a solution that seems to apply (that I can fully grasp).  Via the control panel, I can see Magpie and XML Encode are installed plug-ins, and there are matching php files in the system/plug-in folder.

    I’ve run the server compatibility wizard, and it would appear that

    MySQL (Version 4.1+) support in PHP is ‘unsupported’.  Via MediaTemple, we are in a shared host environment, so I don’t know how to address this ‘MySQL issue’. And I am unsure what my next steps should be.

    If anyone possibly has the patience to walk me through any next steps, I would be most appreciative.

     

  • #2 / Sep 06, 2012 12:35pm

    Kevin Smith

    4784 posts

    Hi ShueLace,

    Welcome to the forums! I’m sorry to hear you’ve had a bit of a time getting your site back online, but I think I can help you get these two errors fixed right up. The short of it is this: the errors are there because you have code in your templates that’s meant to work with plugins or modules that aren’t installed. To fix it, you just need to go grab the right add-ons and install them.

    The second error should be fixed up by downloading the EE 2-compatible version of this add-on.

    I’m less sure about the first error since I cannot find a plugin or module simply called “Markdown”. I suspect that add-on is no longer in development. I’ve found several that make use of the markdown syntax, though, so this add-on might be a good replacement for it.

    Could you search in the template manager for this string: “exp:markdown”? Find the template where that tag is used and share with me the context in which it’s used. That might help with us finding a replacement add-on for you!

  • #3 / Sep 06, 2012 2:13pm

    ShueLace

    1 posts

    Thanks for the guidance and I am making progress!

    The home landing page is the one with the {exp:markdown} syntax error, and the full template text is here.  I edited the template to simply remove the string

    {exp:markdown}
     {summary}
     {/exp:markdown}

    and the redaction was successful in getting the landing page to display.  I realize that is not a permanent solution if somehow that string or plug in is valuable, so I am happy to replace or install a substitute PI as needed. 


    The TruncHTML file I’ve installed in the /expressionengine/third_party/ directory, and while the error message no longer appears, the result is a white screen and no page content or graphics. Not sure what I may have missed here to install this element correctly.

    Lastly, a great deal of the original content formatting is askew and content displays extra hashtag and asterisk characters on multiple pages as if the subfield markers and fields are not being recognized. Will all of my page content need to be edited manually to remove the hashtags, etc?

    Thanks for the help.

  • #4 / Sep 07, 2012 3:50pm

    Kevin Smith

    4784 posts

    Thanks for the guidance and I am making progress!

    Awesome!

    The TruncHTML file I’ve installed in the /expressionengine/third_party/ directory, and while the error message no longer appears, the result is a white screen and no page content or graphics. Not sure what I may have missed here to install this element correctly.

    Hmm. Could you follow these steps to help diagnose what might be causing that blank page?

    Lastly, a great deal of the original content formatting is askew and content displays extra hashtag and asterisk characters on multiple pages as if the subfield markers and fields are not being recognized. Will all of my page content need to be edited manually to remove the hashtags, etc?

    I’m not quite sure I follow. Could you attach a screenshot so I can see the problem you’re talking about?

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

ExpressionEngine News!

#eecms, #events, #releases