Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.5.32, csv import, extension
- This topic has 5 replies, 2 voices, and was last updated 6 years ago by Steven Zahm.
02/28/2017 at 11:50 am #413286
I purchased Connections Pro Pack yesterday, spent nine hours prepping data for import for a project that I’m on deadline to deliver, than at 11pm last night ran into the “not permitted for security reasons” issue that I spent another three hours trying to resolve, but to no avail.
I only installed Connections Pro Pack yesterday, so I have all the latest versions of the templates and extensions, and I’m currently on WordPress 4.7.2. The Disable Real MIME Check plug-in allows me to import a .csv file into the Media Library, but I still cannot import one into Connections. I’ve tried disable all other non-essential plug-ins on my site, but that did not resolve the issue either.
So… any suggestions?
Jerome02/28/2017 at 12:51 pm #413327
re: Disable Real MIME Check plug-in
This is not required with the latest version of the CSV import extension. It includes secure method to work with the new security checks on files uploads in WP 4.7.1.
If you are still receiving the incorrect file type or file was rejected for security reason, did you try the solution in this FAQ?
re: I spent another three hours trying to resolve, but to no avail.
Please feel free to ask before spending so much time. I try to answer quickly … if I’m online and weekends might not get to answer until Monday.
re: any suggestions?
I need more details…
When you click upload, do you get the mapping step? If yes, the file uploaded just fine.
When you click the import, what happens?
Did you follow the CSV File Setup Requirements and the Tips or refer to the FAQs? Specifically the Why is nothing being imported? FAQ?
Can you please attached a copy of the file you are importing? Please renamed it from
.txtfirst so the forum will accept the attachment.02/28/2017 at 6:04 pm #413342
No, I never get to the mapping step. I’ve adhered carefully to the CSV specifications, read the FAQ before I even started, double-checked the character encoding, and just to be sure, I first moved my data to the header file you provide. I tried a couple of variations on the CSV file, including the csv/txt rename, and I also tried importing both with and without the Disable Real MIME Check plug-in. But nada, nothing, zip, beyond the “not permitted for security reasons” error.
I’ve done many CSV uploads for a differing plugin, WP Google Map Pro, so I’m comfortable with the drill.
03/01/2017 at 9:55 am #413425
- This reply was modified 6 years ago by Jerome Carney.
Hmmm… odd one then. The uploads “simply” use the core WordPress upload functions so if it uploads elsewhere it should upload in Connections too.
I’ll need to take a closer look. Please attach a copy of the CSV file, renamed as mention in my last response. An outline of the desired mapping. And a WP admin login. I might need an FTP login too. All can be posted here as a private reply. As soon as I get the info, I’ll take a look.03/01/2017 at 11:46 am #413444
Hi Steven: finally tracked down what was gumming up the works: a single apostrophe from an external paste buried deep in my data, which was being read as an illegal character.
Thanks for your help, and for an amazing plug-in.03/01/2017 at 12:27 pm #413463
Hmm sounds like it was somehow messing with the parser because apostrophe should be just fine… unless it was not escaped and you were using single quotes in your CSV file. That would probably kill the parse because the file would not be valid. All speculation.
Great to hear you figured out the issue and were able to resolve it.
You cannot reply to this support topic. Please open your own support topic.