4

I had similar needs some time ago and importer may have changed but it wasn't possible. What I ended up doing was adding an expiry time to the data imported like today + 24 hours then mapping that to the expiry field. The cron runs every day and if an entry isn't included it will simply expire meaning it won't be available. Has worked flawlessly for a ...


3

This error had to do with line endings in my CSV file. Our workflow is to create the entries in Excel 2011 on the Mac and Save As .CSV. Exporting Excel 2011 to .csv results in a file that is encoded "Western (MacOS Roman)" with line endings "Classic Mac (CR)". Changing line endings to either Unix or Windows style makes it work in ...


2

Automatic creation of password is exactly that: it automatically creates passwords for your users. These are random passwords, which are immediately encoded during the member import. This means that you cannot retrieve these passwords to send to users. Also, you cannot import your own passwords. From the in-add-on instructions: For security reasons, the ...


2

Had to submit a support ticket over at Solspace and got help right away. Solution was to set the Unique Field setting to something other than member_id and the import worked beautifully. Big thanks to Nicolas Bottari. :D


2

I think you should try to narrow down the error a little more. Cut the list in half and try each half individually. Does one half go through and the other error? Put aside the working half and cut the bad half into two, and do it again. Keep doing this until you get either a specific XML node causing the issue or figure out it's more about quantity. (You'd ...


2

Seems like your crontask isn't configured correctly. 1) Verify your curl statement works properly by running it in Terminal (Mac) or Putty (Windows). and 2) Verify you're configuring your crontask correctly. Are you storing it in the right file (or configuring it correctly in Plesk?). Consult your hosting company if need-be.


2

Thanks to a hint from Nicolas @ solspace's support, we found that a little htacces was blocking access to a javascript file. Below code breaks solspace's importer (and everything member related) # Prevent direct access to EE Member area # ------------------------------ RewriteCond %{REQUEST_URI} (member) RewriteRule ^(.*)$ http://%{SERVER_NAME}/404 [R=301,...


1

If you look at the data stored in exp_channel_data for regular EE File Upload fields, you'll see files stored this way, eg: {filedir_1}myfile.jpg, where 1 is your upload field ID (this changes depending on your upload directory), and myfile.jpg is your filename. To import File Upload field data, you would therefore need the filename, prefixed with {...


1

Hrmm. I think the first-party member module really depends on having an email address for an account, and really scanning through it to modify it is both a very bad practice and impractical. What I would suggest is generating dummy email addresses for your source file using a GUID for both the localpart and the domain, making it a statistical extreme that ...


1

Nope, Importer does not support importing into Grid fields, nor does it support creating/populating relationship fields. Have you looked at DataGrab? Solspace does have a 30 day money back guarantee.


1

For an operation of this size, you should be using an enterprise solution, not a web application. You should be exporting the data from the other SQL database in chunks so you can move it gently. What is the other SQL format? Directly moving the data files would be better than running a 9gb over-the-web import (too many chances for data to get wrecked, ...


1

I've used DataGrab to achieve this in the past. Solspace Importer will also do the same.


1

I would query the matrix table for an entry that doesn't work and one that does and compare the 2 to see if there is any difference.


1

Your errors are saying that files are missing so it's safe to deduce that something isn't set up correctly. I suggest redownloading the files from your Solspace account and reuploading them to your server to test your theory.


1

Apparently I did not have the default status group linked to that particular channel. That why Importer could not apply the 'Open' status...


1

Yes, you can empty it. Importer temporarily stores the file somewhere to read and use it, whether you submit your original data file through a manual upload, remote URL, server path, etc. The EE cache folder is where these files are temporarily stored.


1

Importer module doesn't support GRID fields.


1

Unfortunately that's not possible. You would need to combine those fields in your XML beforehand, i.e. before importing into your custom text field using Importer.


1

IF the channels share the same custom field group you should be able to use a bit of SQL to check for a specific channel_id and convert it to the channel_id you are keeping. If the channels do not share the same custom field groups you will need to export the data. This can be as simple as creating a template and setting it to XML, or using one of the ...


1

OK...progress, enough progress to be able to post an answer anyway. Turns out using Datagrab rather than Importer seemed to do the trick. Why that would make any difference whatsoever is beyond me as they're both great EE plugins. I'm open to suggestions on that one So, in a nutshell, I created the Image field in the new site using File as its field type. I ...


1

I've had similar try limiting the import to say 10 or 20 entries as every time this has happened its been caused by memory issues on the server. You could try increasing the memory which may help. But start with a small subset of data and build up from there.


1

Try the "Loose XML" option. Also run your xml through a validator just to make sure it's clean. You might also be missing the XML header in your XML file, eg. <?xml version="1.0" encoding="UTF-8"?> Finally, the <categories></categories> node should contain a string of category data, such as a comma-separated list of category names.


1

As of this writing, Importer does not import into Grid fields. I suggest commenting or adding your +1 in our feature request section found here: http://support.solspace.com/support/discussions/ In particular, this feature request thread seems spot-on: http://support.solspace.com/support/discussions/topics/33803


1

It is depended what do you want to do and how secure it must be. If just check it by s/n - make custom from, <form action="/site/sn_check/" method="post"> First name: <input type="text" name="firstname"><br> </from> then, using Mo’ Variables, get _POST value what user is entered and make request using Query module {exp:query ...


1

As of this writing, Importer does not read XML node attributes, such as lang="es" for example. Therefore, Importer will read only the first node of a series of nodes named exactly the same, <description> in this case. I recommend submitting this as a Feature Request under the specific add-on category. It'll also give other users the option to vote up ...


1

The latest version of Importer, as of this writing, is 2.2.3. This version adds EE 2.7 compatibility. Please upgrade to this version and let us know if the issue persists.


Only top voted, non community-wiki answers of a minimum length are eligible