Plugin Contributor
Savvas
(@savvasha)
Hi @chriskchris,
Can you try to increase your PHP Memory Limit and try again?
See the above link for more information
https://premium.wpmudev.org/blog/increase-memory-limit/
Thanks,
Savvas
Hi Savvas,
I tried to increase PHP Memory Limit as described in the link. I still get the same message. Any other idea?
Thanks in advance
Chris
Plugin Contributor
Savvas
(@savvasha)
I am sorry to hear that…
Can you please paste the content of your CSV file so as to try it in a localhost environment?
Thanks,
Savvas
Plugin Contributor
Savvas
(@savvasha)
Hi Chris,
I just checked your csv and noticed that there a lot of empty lines between your data.
There is a sample csv file inside SportsPress (https://github.com/ThemeBoy/SportsPress/blob/master/dummy-data/events-sample.csv)
You can use that as a starting point.
Thanks,
Savvas
Now we’re getting closer. I updated the file to force the problem. For sure it’s not a real use case, although it shows the problem. I’ve updated the file, so only one event is imported with a lots of dummy players.
If you import this file, you will see: the import stops when row 299 is reached. Afterwards no more text will be imported.
Hey Savvas,
do have any new insights about this problem?
Thanks in advance
Chris
I was importing schedules into my site and saw some odd behavior. I used the event-sample.csv to make my file and have 500 events in it. If I just grabbed my csv and imported it, I could get 41 events to import. Since I was just putting in date/time/venue/home/away, I discovered if I click on the column headers and picked –deactivate, then more data can come in and I can import 324 rows. I have not been able to get it above that number so I am importing in chunks which turned out not to be so bad. I was not able to tweak my memory settings in my php file so just used this work around.
Plugin Contributor
Savvas
(@savvasha)
@chriskchris and @texlax,
Event importing has a huge demand of resources, thats why it stops after some/many rows.
We are in the process to replace Events-Import with Fixtures-Import and Event-Performance-Ipmport which are more optimized. Unfortunately we cant give an ETA.
Meanwhile you can override those limitations using “batches” of 150 rows for each import. Not an ideal solution, but it can do the job.
Hey Savvas,
okay.
Thanks for the feedback and support.
So I will work with the work around.
Greetings
Chris