Profields Table CSV Importer / Exporter

[olafgleba]

Hi @adrian, thanks for your suggestion. I will try it on a clean install on sunday. And will try the module on other installations (with a vary set of modules) just for testing. I'll get back to this...

[olafgleba]

Hi again @adrian, it turned out the module just doesn't work well if the table field is part of a RepeaterMatrix (Pro)Field (at least with my version combi). Beyond this the table field + your module works flawlessly ;-). And because my abilities are still limited with module building, probably i'll can't fix it by myself and send a Repo PR, sorry.

Processwire 3.0.221/224 dev, ProFields Table 0.2.4, ProFields Repeater Matrix 0.0.9, latest Table CSV Import/Export Module (2.0.16).

Because i didn't mentioned it so far,- thanks and kudos to you for the module.

 

 

 

[adrian]

Hi @olafgleba - I just tried a table field in repeater matrix and it looks ok here so I really don't know what's happening at your end I am sorry. Maybe a conflict with one of the other fields in the RM field? Does it work with only a table field in the RM field? Perhaps you can start with the simplest example of just a table field in a RM field with nothing else and if that works try to figure out what it breaking it. Sorry I am not much help :)

[olafgleba]

Hi @adrian, strange. I did exactly what you suggested,- add a new RM field, add just one type with one table(ProField) field. Even with the similiar values ;-). Also placed it on a template with no further RM field (prevent possible interfering). Same module/field/PW versions as posted before. On top with an upgraded PW (latest dev (3.0.237)). The views remains broken(s. screen).

I suppose your RM version is set to latest (0.1.1.)? If so, maybe there is a change left where to look at. Otherwise i am running out of ideas i am afraid ;-(

But regardless the result, i really appreciate your answers and willing to help! ?

 

[adrian]

Yep, running 0.1.1

Any chance you could post this on a live site somewhere you could give me a superuser login to test it out for you?

[olafgleba]

Sent a DM ?

[elvina]

Hi

I'm having problems importing to a csv with a page(select) in one column. Whatever I put in the correct column the title or name, I am getting an error that says

Quote

 

TypeError

ProcessWire\FieldtypeTable::wakeupFile(): Argument #1 ($page) must be of type ProcessWire\Page, null given, 

 

I've tried pasting it in, and using a file. I've tried tab and comma delimited. I even tried filling in one row, adding it. Then I exported it as a csv and tried to import that file, and i get the same error.

Is there anything specific I might have missed?

its 5 columns, 2 of which are page(select) fields, the others are just plain text fields

[adrian]

Hi @elvina - sorry, but I am having troubles reproducing this - I have successfully imported and Page Select columns matched the page based on the title I entered in the CSV.

Even if I enter a page title that doesn't exist, I don't get that error - the row just doesn't populate anything for that field.

What version of this module and FieldtypeTable are you running?

[elvina]

Hi

Table CSV Import / Export Version    2.0.17  (just updated)
ProFields: Table    0.3.0

I wonder if I somehow am doing this wrong! I have used the csv import very successfuly with page creation, so I thought I was doing the same.
I tried changing some settings in the table columns, and another row.

example of what i have pasted into csv import box (which is the contents of the exported file) 
position and country are pages.

position.title    name    email    organisation    country.title
"Vice President"    "FirstName Surname"    name.surname@gmail.com    UFRGS    Brazil
 

Settings as tab seperated. so with this one, I got the error

Unknown Selector operator: '[empty]' -- was your selector value properly escaped? field='Vice', value='President', selector: 'Vice President'

[adrian]

It looks to me like it has something to do with your table settings under the "What pages should be selectable?" section. Can you try a simple example with just a template, eg:

If that works, then maybe you can help to figure out what selector is causing the issue.

[elvina]

Hi,

it is just single template. actually i just realised what I had changed to get the 2nd error message, i tried using Page (autocomplete) instead of Page (select).

I put it back to Page (select) and tried with basic page template, and i get the first error again.

ProcessWire\FieldtypeTable::wakeupFile(): Argument #1 ($page) must be of type ProcessWire\Page, null given, called in domain.org/site/modules/FieldtypeTable/FieldtypeTable.module on line 1189

 

 

[adrian]

That line #1189 suggested there is an image subfield/column involved:

I wonder if there is some old image field that wasn't properly deleted. If you look at the database table for the table field, does it contain any unexpected fields? Or maybe the json settings for the field have reference to an image field?

Can you please try on a new table field built from scratch with just the fields you need and see if that still has issues?