samwilson

No, I’m afraid at the moment Tabulate does not support any sort of ‘file’ field. Such a thing is planned however, and the feature is being tracked at https://github.com/tabulate/tabulate/issues/23

Sorry to disappoint. Thanks for your kind words. ??

You could try changing your temp directory by putting this in your wp-config.php:

define( 'WP_TEMP_DIR', ABSPATH . 'wp-content/tmp/' );

Other than that, you should ask your database administrator about granting FILE privilege to your user.

Does your MySQL user have write access to that directory? Does it have the FILE privilege on the database server?

There are more details here:

https://tabulate.readthedocs.io/en/latest/faq.html#what-reasons-exist-for-the-unable-to-create-temporary-export-file-error

You could try changing the temp directory to another one.

No, not directly I’m afraid. It would be hard to identify what fields to search — or do you mean to search all fields in multiple tables?

I think one solution could be to create a view that combines the tables you want to search, and contains an additional field that contains all the text you want to search, and then expose that field as the search field.

Can you provide more detail about your use case?

Okay, 2.10.2 has just bee tagged and should be available for upgrade pretty soon.

Thank you for reporting this! This bug has been fixed, and I’m preparing a new release now.

It seems that it’s pretty hard to solve this for all the different varieties of currency input value (multiple languages, formats, etc.). Perhaps someday we’ll have a better import system that allows you to specify formats at import time (like LibreOffice etc. do), but it’s not coming this year I think. ?? Sorry!

I don’t think this plugin is supported any more, now that it’s functionality has been moved into core.

Good question!

Yes, it’s because of the dollar sign and comma that it’s not interpreting the value as a proper decimal number.

The tricky thing is how to solve this…

I shall have to investigate a bit, but off the top of my head unfortunately the easiest thing to do will be to change the spreadsheet formatting before import. Sorry!

But I’ll let you know if there is a better way.

No, I’m afraid at the moment it cannot. Sorry!

But it’s a great idea, and I’ll see about adding the feature. I’ve added it as #51. Follow that issue for updates.

If you have any dramas getting it working, please do post more here.

Thanks!

This is already a feature! ?? Cross-references will use the first unique column (after the primary key) as the text to display to users.

If this isn’t working, perhaps the unique key on the cross-referenced table comprises more than one column?

Basically, there should be a primary key (i.e. ID) and a separate unique key (i.e. Title).

This has been fixed in the recent update. If you’re still having this trouble, could you please file a new issue? Thanks! And sorry about the trouble.

Image fields are on the roadmap; it will probably be a few more months before they’re ready though! Sorry. ??

I’ll mark this as resolved for now, as we’re tracking image field types in a GH issue.