boboldehampsink / import

DEPRECATED - Import plugin for Craft CMS
MIT License
177 stars 28 forks source link

Import task never begins #127

Closed chasegiunta closed 8 years ago

chasegiunta commented 8 years ago

Trying to import user data... My CSV (for testing) is as simple as this

email, username, highSchool
10920646@live.mercer.edu, 10920646@live.mercer.edu, PAULDING HIGH SCHOOL
112174.ch@gmail.com, 112174.ch@gmail.com, ROYAL CITY HIGH SCHOOL
14doughjerj@washk12.org, 14doughjerj@washk12.org, ENTERPRISE
15jvogel96@gmail.com, 15jvogel96@gmail.com, RIVERSIDE

Using emailAsUsername so including username data as a precaution, recommended on another issue. Everything seems to detect mapping correctly. image

Upon starting the import, nothing happens. A task is created, but never starts. It will remain on "pending" indefinitely. No other tasks exist, so no stuck tasks preventing. There is nothing showing up in Craft logs (no log files for import plugin exist).

Craft 2.6.2797 Import 0.8.32

boboldehampsink commented 8 years ago

Looks like a Craft issue to me. Have you set runPendingTasksAutomatically to false?

chasegiunta commented 8 years ago

I have not. Other tasks begin & run in entirety just fine.

boboldehampsink commented 8 years ago

As long as it's pending, the import hasn't even started. You should contact Craft support initially.

chasegiunta commented 8 years ago

I tracked this down to being an issue with Laravel Valet, which I'm using for my development environment and some incompatibility with how the tasks kick off. Not quite sure what exactly is the difference is with Valet, or why some tasks work fine and others don't, but running the site through MAMP resolves my issue with Import.

chasegiunta commented 8 years ago

Just an update: I've resolved the issue through a couple added lines in the plugin explained here: http://craftcms.stackexchange.com/questions/16096/tasks-either-dont-start-or-dont-run-as-background-processes

Given that Valet (and Caddy Server) are relatively new & gaining popularity, it might bea fix that could be added to core by P&T (unless it has some negative unrealized implications).