Also getting syntax error

  • Resolved Emmageddon

    (@emmageddon)


    7 years, 6 months ago

    Hello having been told I need to start my own thread to bring up an issue others are having, I would like to report that although on one site the syntax issue has been solved with the updating to 4.3.1, on anther clients site I have had to disable the plugin completely and am resorting to using Jetpacks mobile site which I do not prefer over the WPTouch plugin as I am getting a syntax error similar to others:

    /wp-content/plugins/wptouch/core/class-cache-smash.php on line 104”

    I use the WP Super Cache plugin and the only other cache I use is WP Optimize for images.

    Had to disable as it showed this error on the desktop and mobile version of the site and rendered the admin area completely unusable as it displayed this too.

    Any help would be gratefully received. Also apologies for what was claimed to be a hijacking of a thread – was not my intention – was just trying to show I had the exact issue others were commenting on and didn’t want to deluge the forum with another topic on the same issue already raised. I will take the moderators notes on board.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Emmageddon

    (@emmageddon)

    7 years, 6 months ago

    Just want to add, I checked on my hosting account and found we were at 5.2 PHP – I have now upgraded to 5.3 – after doing so I renamed the wp-touch plugin back to its proper naming convention and attempted to reactivate but got a message telling me the plugin had been deactivated to stop a fatal error.

    Thread Starter Emmageddon

    (@emmageddon)

    7 years, 6 months ago

    YES! Just wanted to say the latest update 4.3.2 has resolved all my issues.

    Thank you to the team for working on this over the past couple of days. I really appreciate all the hard work gone into fixing these errors for all us users and for listening to the issues and acting on them accordingly.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Also getting syntax error’ is closed to new replies.