Hello,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

.

I am unable to find any table on the related Page.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

And point me to the table ID.

Thanks.

Hi Alison,

My sincere apologies for all the waiting time.

Thank you for your patience and for the Access.

I have isolated the issue.

For example, let's focus on this cell which is cut off :

"Bill of lading for a DPC Chariot and Harness shipped by T. Hanbury on the ship Baltimore, from London, to Daniel Park Custis, Esquire, Port of Virginia, Mar 12, 1753.  This original document was found in William Phelps Eno's 1877 bible, which is also in t"

It shows the same way in the HTML itself as it is cut visually on front-end.

And it also shows the same in the source Database Column.

Basically, when you imported the Spreadsheet into a Manual Table;

you selected the "one line String" for the Column type of the field "Notes".

That makes the Field type in the SQL Database as "VARCHAR" which has max limit of 255 characters.

-

There can be a couple of different solutions for this.

1.  For example, if we would go for a new Manual Table, this time you can double-check which Columns have some longer text ( more than 255 characters).

For these Columns, select the type in our Plugin as "multi line String" because this saves the Field in the Database as TEXT, which has a much longer text length limit.

In that case, it will import the full text on the "Multi line string" Fields.

2. Another way, if you know your way around the WP SQL Database, you can either access it directly via a DB Management Tool; ( e.g PhPMyAdmin)

or you can install this plugin WP PhPMyAdmin ( i installed it on your Site, I hope you don't mind);

and you can use it to access your Database.

Check under the Editing options of the Table, what is the MySQL Table Name, then find it in your DB.

There you can modify the Column settings, and change it from VARCHAR, and remove the character limit ( 255);

then save it to a "TEXT" type.

This will allow a much higher limit for text.

After this, you need to upload the source file again in the existing Table, we just advise caution which option you choose.

You can see more details explained on this Page - how this feature works, to update existing Tables via file upload;

Each of these options has its set of rules, which we explained to avoid any issues.

For example, for some of the options your file needs to have the same Column structure, to avoid 'breaking the table';

while the last option to completely replace the Data source can be used safely without breaking the Table.

( but you can see more details on that Documentation Page);

I made a duplicate Table now, just as a text and i can confirm this will solve the issue for your Table.

After the investigation, I removed the duplicate Table; 

and i deactivate the WP PhPMyAdmin Plugin.

I hope this helps.

Let me know if anything is unclear, if you have any questions at all.

Hi Alison,

Sorry, I also forgot to add one more detail;

A side note - not related to any issues.

I notice you still have not updated our Plugin to the latest 6.2.1 Version  - you should, we have added some new fixes/improvements, a couple of new Features, etc.

So I recommend to do that soon, to take advantage of the latest features/improvements.

Let me know how it goes and if you have any questions in regards to the previous details.

Thanks.

Hi Alison,

Sorry, I just wanted to do a quick summary of all the important points, since there were a lot of details, I don't wish to make it confusing.

So, for the time being, if you will only be updating the rows in your source Data without adding/removing Columns, or renaming Column Headers;

in this case, you can simply choose one of the first two options during Table update :

1. To replace all the rows currently in the Table,  from the rows of your updated file.

2. Or, to leave the current rows in the Table and just add new rows from a file.

If one of these two options works for you - then there will not be any issue, the Table is not going to change the 'long text' (TEXT) Column type back to "varChar" ( 255 character limit).

The third option, to completely replace the entire Table's Data and Structure is only used if you need to add a new Column/Remove a Column, or rename one or more Headers.

But still, I will speak with our Developers to see what we can do to improve that, and when they advise we will report back;

And we will check if there is any custom workaround for you to set each String Column to be set to "TEXT" by default in the Plugin.

Let me know how this seems for now - if maybe one of the two first updating options could work for you - if you don't plan to change the Data/Column Structure for this Use-Case.

Thank you.

Hi Alison,

This was quicker than expected - we actually have a custom workaround already which you can use.

You will be able to change this behaviour in a PHP file, if you edit with any text/code editor.

Please go in your WordPress Folder in your Hosting Files,  either via FTP or via Hosting File Manager and find this PHP file :

../wp-content/plugins/wpdatatables/source/class.constructor.php

You can use CTRL+F   to search and replace any "VARCHAR(2000)"  to "TEXT",  and then the new String columns will be created without character limit by default.

You would have to do this at every update for the time being, because the update will revert it to default;

but our developers are working to implement a better solution soon. 

I don't have an ETA on it, though, but they will do their best to be as soon as possible.

You can certainly follow our changeLog page if you'd like, where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

If you need me to edit that Code for you, I will need WP-Administrator access again and FTP credentials so that i can edit our Plugin's file.

If you send me credentials, just make sure it is in a PRIVATE reply, for safety.

Let me know if that sounds OK.

Thank you.

Hi Alison,

No problem at all, you can always take your time and we will be here to follow up.

Let us know if you encounter any issue with that custom workaround;

in the meantime, our developers will do their best to make an improvement on that front soon.

Thank you.