ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 3 replies, has 3 voices, and was last updated by  Roman Grebenchuk 2 years, 4 months ago.

  • Creator
    Topic
  • #7564

    kingosoul
    Participant

    Hello All

    I’m trying to tie my google apps account to OroCRM but it is coming up with the following error:

    Loading emails from “INBOX” folder …
    Query: “”””.
    Found 398 email(s).
    The synchronization failed. Error: DateTime::__construct(): Failed to parse time string (Sun, 27 Jul 2014 09:55:59 UT) at position 26 (U): The timezone could not be found in the database.
    The synchronization failed. Error: DateTime::__construct(): Failed to parse time string (Sun, 27 Jul 2014 09:55:59 UT) at position 26 (U): The timezone could not be found in the database.
    Finding an email origin …

    As you can see it is connecting fine, it seems to be an issue with the fact the time string from google has UT at the end, but I cant seem to figure it out.

    Can someone please help me with this issue.

    Thanks in advanced,

    James

Viewing 3 replies - 1 through 3 (of 3 total)
  • Author
    Replies
  • #7568
    Dima Soroka
    Dima Soroka
    Oro Core

    Which version you are running on? We had a fix for this released in 1.4.2, please check it out and let us know if it doesn’t help.

    #7569

    kingosoul
    Participant

    I am on 1.4.1 so thats why.

    But I am currently trying to perform an update to 1.4.2 and am running into the following error when I run
    git pull

    You are not currently on a branch, so I cannot use any
    ‘branch.<branchname>.merge’ in your configuration file.
    Please specify which remote branch you want to use on the command
    line and try again (e.g. ‘git pull <repository> <refspec>’).
    See git-pull(1) for details.

    How do I get around this?

    I am following the instructions on https://github.com/orocrm/crm/blob/master/UPGRADE.md

    #7575

    You can skip git pull step and run composer update

    and then update crm

    Before update we recommend backup DB

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.