I’m uploading rows from an excel sheet. When I select “replace rows with source data” It gives me the error you see in the attached photo.
I’ve checked endless amount of times to verify the header rows in my excel spreadsheet match letter for letter the header rows in my table. Is this a known issue and what is the fix?
Can you tell me, are you including the wdt_ID Column in your source Excel?
If you are updating an existing Manual Table and if you try to include any of these 'premade columns' like wdt_ID, or wdt_created_by, wdt_created_at, wdt_last_edited_by and wdt_last_edited_at;
in that case, it will fail to import.
So please check and ensure that you only use your custom Columns in the source Excel file which is used for importing of the 'replace rows with source data' and exclude any of these 'premade manual columns' because they will auto-populate with auto-assigned wdt_ID and auto-asigned data for the user who uploaded the file and the time, when it was uploaded, etc.
I thought initially I had to ADD in the wdt_id column so I tried that and when that didn’t work too I deleted it. So I’ve tried a lot to get this to work is my point.
I believe the issue might be with the Header Names on some Columns.
Our Plugin is not capable of having several Headers with the same name.
For example, if your 'origin Header names' will have 'position' in more than one Column, in this case our Plugin only reads the first one - and 'ignores' the others with the same header name.
But I am not sure how you managed to create this table like that in the first place, since it shows the 'displayed headers' on the Front-End as multiple 'position' headers.
I suppose you named the 'origin headers' differently for some of these 'position' headers, then just changed the 'displayed header name' in the Columns settings of our Plugin?
For example, if I inspect the HTML of your Table on the Page, I can see, the first Header's 'origin name' says 'wdtcolumn';
then the second time the Position Header is shown, the actual origin header says 'wdtcolumn3' and so on.
So please go into each Column settings, in the Display settings , and check what is the Origin Header Name;
then rename your Excel Sheet Headers to match the origin Headers exactly as they are on your Plugin's Table.
I’ve uploaded the exact source file I used. I edited all the header names to reflect the “wdtcolumn1… wdtcolumn2… etc” names. I then went into the table in the back end in the plugin and edited those column headers to reflect exactly what I have in the excel spreadsheet (attached). It gave me the same error (also attached). This is all after hitting “Replace Rows With Source Data”.
Also as crazy as this may sound - I just kept uploading it and eventually something clicked and it uploaded. To respond to your curiosity of how I did it the first time.
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.
-
Thank you for sending the Excel file.
I am unable to reproduce any issue with your file.
If i create a new Manual Table from it - then I can update it with choosing the 'Replace Rows With Source Data' and as long as I have the same order and name of columns, there are no errors.
Did you maybe reorder/switch places between some columns, since I notice you got, for example, Columns from 0 to 2, then wdtcolumn9, and it continues in chronological order again, 3, 4, 5, then column 10;
then 7, 8, then 11.
For example, if I reorder the Columns, then i can 'trigger' the same error to happen.
Did you double-check are all your fields in the same order and same origin name as they are in your existing Manual Table?
I have made a WeTransfer account and downloaded the file. Apparently I need an mkv media player to watch it?
Reading your response I feel like the answer to this issue is in the video. I made the excel spreadsheet to match each column in the table exactly as it is. Even went as far as renaming the column headers to match their exact origin header.
To test out what I think may be in the video - I rearranged every column in the table to be chronological 1-11 and did the same in the excel sheet. Uploaded and got the same error. Trying with a completely new generated Table at this point but hoping I don’t have to create a new table everyone I want to upload new info into it. I’ll let you know how this goes.
Makes no sense. Made a new table and it uploaded. Changed the column headers to match the exact headers in the faulty wpdatatable… still breaks and refuses to upload. I figured it had to be something with the configuration at that point since that’s the only difference at this point so I went through every menu option and matched settings down to font. The new table works but the old one still doesn’t. Only thing I can think of at this point is some update pushed somehow Didn’t “grandfather in” a feature that’s causing the old one to break. Not saying this to put blame on anyone, that’s genuinely all I can think of. Still curious to see the video.
I’ve manually duplicated my table. Same exact settings all the way across. It is uploading now. I tested a few changed in the spreadsheet and reuploaded and everything seems to be working as advertised now. Baffled as far as what was going on and it sucks that I don’t have an answer for you to help you going forward but seems like the new one is working as needed now.
It’s happening again but with a different table and different error message saying I now don’t know how to count. Source file, table I’m trying to upload it to, and error message attached.
You will not be able to remove our wdt_ID Column, that is the primary Column needed for the Manual tables to function.
We are unable to reproduce the scenario you described in the latest messages;
we can use any Excel Sheet as the initial data for importing/making a new Manual Table;
then we can again use the same Sheet to update the existing Table without any errors.
1. Can you please first record your screen and send us a Video, so that we can see the exact steps, how it looks when you import your Excel initially to make a new Manual table;
then how it looks when you try to update that table later with the same Excel file/ how the error happens on your end?
If the Video gets too large for the ticket, upload it to weTransfer and send me a download link.
2. Then we can remote in to your Site and try to investigate how that happens, since we are unable to reproduce it on our end.
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.
I tried uploading this spreadsheet to the table you created for it. It worked. If you made this Table to correspond with this file, the only thing I changed was adding one link to one of the rows. Everything else remained the same. Also it was not on a column header row that I added the link just to be clear on that.
For further information - I deactivated the plugin on my backup/sandbox/developer website. The buy/hold/sell page holding that wpdatatable shortcode came back up. Reactivated the plugin and it made that critical error on that page again. Seems like uploading a spreadsheet into anything makes the table become lost.
No other tables or pages containing those short codes are affected.
I curiously made a new Buy/Hold/Sell chart using the same exact file that caused the critical error (also the same file I was using everyday to update it). It worked. Then I went into the Table and tried uploading it again just to be sure before I configured the chart to how it looked before all these errors (and to remove the critical error eyesore page from my site) and it worked again. So the temporary fix is in place….
The question now is just why did this happen and am I going to have to recreate every table I have again and upload the new short codes to each corresponding page before I upload the corresponding spreadsheets again? I’m currently scared to touch any table and I have some uploading work to do on some of them.
By the way I appreciate your help big time. Although it is extremely frustrating all these unknown errors are happening to me.
A further question I have is has anyone else experienced this where tables created on an older update (like my old 5.8.3) cause a critical error if the same spreadsheet is uploaded again on the version this was updated to? And further if it’s common to have to play hot potato with recreating tables all the time due to the seemingly ghost errors (the last issue) that can’t be recreated or that cause critical errors in this case?
Here is the good file in case you need to inspect it. this is the one I just used to create the new Table. Also the same one that caused the critical error on the old one.
If you need to see the corresponding table in wordpress it is [wpdatatable id=73]
The url is still https://brainyballers.com/buy-hold-sell-chart/ (I had to deactivate the plugin momentarily and change the shortcode to get around the critical error message.. in case you’re wondering how I changed it with a critical error)
For now I’m leaving all the bad “Buy/Hold/Sell” tables in the plugin just in case you want to see the critical errors. It’s just a message so there’s not much to see but just in case.
This worked. I cautiously uploaded the charts with the new fonts to the backup and it worked so I applied it to the front end table and it again worked.
Thank you so much for working through all of this for me. As frustrating and scary as it was when my site page went down (the best feature on my site so far too.. just didn’t want to say that in the moment to add to any pressure on you) This plugin has been phenomenal.
As tedious as it can be too it’s still much worth it. Thank you so much.
The solution found clearly was the issue. Although, my main device is IPad. It appears as though IPad or IOS doesn't always understand what an unformatted cell looks like.
Or at the very least it doesn't correspond with wpDataTable's definition of what that is.
For Example, I created a new excel document, and without touching any formatting I simply typed in my header rows and then uploaded and got that critical error that you ended up finding out was the formatting issue.
Is there a known work around to this? I even clicked on a random cell I never touched and pasted just the format. No luck. I've looked up on multiple forums IOS formatting las well. No luck there.
Just an update. I now do not think the formatting issue was the issue. I’m going to make a video explaining why.
What you’ll see is I duplicate a good “buy-hold-sell” wpdataTable and also a “rookie mock draft” wpdatatable.
What I will do is show you the good mock draft wpDataTable, and I will then save and upload the corresponding mock draft excel file into that Table where you will see the table in wpDataTable break.
I will then proceed to copy the header from that excel file which broke the “mock draft” wpDataTable into the corresponding “buy-hold-sell” excel file then proceed to upload that buy-hold-sell excel file into the corresponding wpDataTable for that file where you will see it succeeds using the header format which broke the other chart.
Further, I was never able to view able of your videos using WeTransfer as even after I downloaded them my research could not find anything showing me how to watch or reformat a .mkv file.
Further, I changed the font in the buy hold sell chart, saved, and uploaded. It still worked. There definitely is a different issue going on other than just the header font.
I looked into multiple things and thought hard about what the warning is trying to say.: “Column 'pos' cannot be null”
Tried allowing every column to “allow empty value” didn’t work. Got same error.
Tried deleting the “position” column and redoing it. Didn’t work. Same error.
Tried finding any hidden “pos” columns. Didn’t. Only the “position” column sounds like it but tried the above fixes to that column to no prevail.
Those are the top fixes I want to let you know I did. Everything else has been almost an hour of messing with fonts in excel and your plugin and a bunch of other different things. Although I realized it has to be something with my mock draft plugins. Maybe somehow I configured them just isn’t jiving with the most recent updates and my excel document anymore. Although I feel as though I’ve all but ruled out the header format being the issue.
Do you have any sort of troubleshooting code sheet you can pull up to look deeper into the “Column 'pos' cannot be null” warning? Maybe some developer has this. Usually those have an explanation attached to each code even if they’re hexadecimal to make them understandable. I copied and pasted that text from the warning so what you see is exactly as it shows: Column 'pos' cannot be null
Can I get your opinion on my video where I copy the format from an excel file that breaks the wpdatatable into another excel file where it then does not break the wpdatatable?
I was able to watch the video this time. Although it doesn’t really address that point where I copy the format from one excel file into another and try uploading to two different wpdatatables and get 2 different results.
Are you aware if Microsoft Excel’s default font change in January? They changed to Aptos. The buy hold sell table on excel that I am able to upload is still defaulted to Calibri add I believe I made that table before that update. Calibri IS unformatted in that spreadsheet.
The table that throws me the critical error in wpdatatable defaults to aptos. I tried changing the header font and I got two different results: one time the critical error then the next got a non critical error just saying it doesn’t recognize any headers.
Hi Zach, My apology, I missed to comment on the Excel default font change. I am confident that the font type should not have any effect on these issues.
I believe we are getting close to isolating what happens for the importing of Tables and updating them.
It seems it is related to that old 'issue' we had for a long time, as described in my previous reply, which is now fixed in the 6.3.2 wpDataTables version;
but it seems we have it completely fixed only when we 'link the table from Excel', but for some specific file it seems the issue still happens when importing the data for editable tables, our Plugin seems to be 'picking up' that there is 'something' after the last Column which 'was there' or 'should be in some cell that does not have a header name' and so on...
For example, I did notice on your last Table #122, in that Table you got one more additional Column "Team" which was not in the Excel file you sent me - that file had one Column less;
so if you can recall if you maybe did that scenario - to have more columns first, then to delete some column and save that Excel.
A scenario like that can 'trigger the issue' where Excel uses that 'cache' to 'memorize there was something there after the last column' and thus our Plugin 'picks that up'.
So to summarize, I believe there should be no font isuses, but if you can just try to keep the same number of columns, same header names when you are updating existing Manual tables, now from version 6.3.2, this issue should then stop happening for new tables.
Let us know how all that seems and if that can work going forward for your use-case.
So just to clarify, are you saying I should be able to upload the chart I provided to a new table in wpdatatables to make a new table with 6.3.2?
You were correct that I was missing a column, my apologies on that.
I tried the linked tables and it seems to work like a charm. When uploading an excel spreadsheet, should everyone lean towards the link option and not the manual excel spreadsheet upload option? I never understood the difference between them but if the linked is expected to be more consistent than the manual option has then I’m going to recreate all of my charts to be the linked option. This absolutely should work.
The Buy Hold Sell Table is working as always but with the old manual Table. Tried changing it to a linked table and wasn’t recognizing the repeat columns. Everything else is linking so just a heads up I could be back if that BHS manual chart also stops working at some point. Thank you so much for all your help!
I’m uploading rows from an excel sheet. When I select “replace rows with source data” It gives me the error you see in the attached photo.
I’ve checked endless amount of times to verify the header rows in my excel spreadsheet match letter for letter the header rows in my table. Is this a known issue and what is the fix?
Attached files: IMG_1285.png
Hi Zach,
Can you tell me, are you including the wdt_ID Column in your source Excel?
If you are updating an existing Manual Table and if you try to include any of these 'premade columns' like wdt_ID, or wdt_created_by, wdt_created_at, wdt_last_edited_by and wdt_last_edited_at;
in that case, it will fail to import.
So please check and ensure that you only use your custom Columns in the source Excel file which is used for importing of the 'replace rows with source data' and exclude any of these 'premade manual columns' because they will auto-populate with auto-assigned wdt_ID and auto-asigned data for the user who uploaded the file and the time, when it was uploaded, etc.
Let me know if that helped.
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Milos,
I am not using the wtd_id column. In my excel document I have the following columns from left to right:
Position, name, date added, position, name, date added, position, name, date added.
All starting in column A and ending in column I (9 columns).
This is the table I’m trying to edit via inputting my excel spreadsheet:
https://brainyballers.com/buy-hold-sell-chart/
I thought initially I had to ADD in the wdt_id column so I tried that and when that didn’t work too I deleted it. So I’ve tried a lot to get this to work is my point.
Any help on this?
Hi Zach,
I believe the issue might be with the Header Names on some Columns.
Our Plugin is not capable of having several Headers with the same name.
For example, if your 'origin Header names' will have 'position' in more than one Column, in this case our Plugin only reads the first one - and 'ignores' the others with the same header name.
But I am not sure how you managed to create this table like that in the first place, since it shows the 'displayed headers' on the Front-End as multiple 'position' headers.
I suppose you named the 'origin headers' differently for some of these 'position' headers, then just changed the 'displayed header name' in the Columns settings of our Plugin?
For example, if I inspect the HTML of your Table on the Page, I can see, the first Header's 'origin name' says 'wdtcolumn';
then the second time the Position Header is shown, the actual origin header says 'wdtcolumn3' and so on.
So please go into each Column settings, in the Display settings , and check what is the Origin Header Name;
then rename your Excel Sheet Headers to match the origin Headers exactly as they are on your Plugin's Table.
Let me know if that solves the issue?
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Table Link - front end
Miloš,
I wish I could be reporting back with good news.
I’ve uploaded the exact source file I used. I edited all the header names to reflect the “wdtcolumn1… wdtcolumn2… etc” names. I then went into the table in the back end in the plugin and edited those column headers to reflect exactly what I have in the excel spreadsheet (attached). It gave me the same error (also attached). This is all after hitting “Replace Rows With Source Data”.
What else can I try?
Thanks for the help!
Zach
Attached files: Buy Hold Sell Official copy copy.xlsx
IMG_1300.png
Also as crazy as this may sound - I just kept uploading it and eventually something clicked and it uploaded. To respond to your curiosity of how I did it the first time.
Hi Zach,
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.
-
Thank you for sending the Excel file.
I am unable to reproduce any issue with your file.
If i create a new Manual Table from it - then I can update it with choosing the 'Replace Rows With Source Data' and as long as I have the same order and name of columns, there are no errors.
Did you maybe reorder/switch places between some columns, since I notice you got, for example, Columns from 0 to 2, then wdtcolumn9, and it continues in chronological order again, 3, 4, 5, then column 10;
then 7, 8, then 11.
For example, if I reorder the Columns, then i can 'trigger' the same error to happen.
Did you double-check are all your fields in the same order and same origin name as they are in your existing Manual Table?
You can download my Video of this test here;
where i first re-order some columns;
then I order them again in the Table as they are from the Sheet and then there is no error.
Let me know if that maybe solves the issue?
Thanks.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Miloš,
https://www.howtogeek.com/200736/what-is-an-mkv-file-and-how-do-you-play-them/
I have made a WeTransfer account and downloaded the file. Apparently I need an mkv media player to watch it?
Reading your response I feel like the answer to this issue is in the video. I made the excel spreadsheet to match each column in the table exactly as it is. Even went as far as renaming the column headers to match their exact origin header.
Is there any other way to send me this video?
Thanks,
Zach
Miloš,
To test out what I think may be in the video - I rearranged every column in the table to be chronological 1-11 and did the same in the excel sheet. Uploaded and got the same error. Trying with a completely new generated Table at this point but hoping I don’t have to create a new table everyone I want to upload new info into it. I’ll let you know how this goes.
Makes no sense. Made a new table and it uploaded. Changed the column headers to match the exact headers in the faulty wpdatatable… still breaks and refuses to upload. I figured it had to be something with the configuration at that point since that’s the only difference at this point so I went through every menu option and matched settings down to font. The new table works but the old one still doesn’t. Only thing I can think of at this point is some update pushed somehow Didn’t “grandfather in” a feature that’s causing the old one to break. Not saying this to put blame on anyone, that’s genuinely all I can think of. Still curious to see the video.
Miloš,
I’ve manually duplicated my table. Same exact settings all the way across. It is uploading now. I tested a few changed in the spreadsheet and reuploaded and everything seems to be working as advertised now. Baffled as far as what was going on and it sucks that I don’t have an answer for you to help you going forward but seems like the new one is working as needed now.
Thanks for all the help!
Zach
It’s happening again but with a different table and different error message saying I now don’t know how to count. Source file, table I’m trying to upload it to, and error message attached.
Extremely frustrating
Attached files: IMG_1339.png
IMG_1338.png
IMG_1340.png
Just for the heck of it I created a new table using an excel spreadsheet.
I did not touch a single thing after that.
I then went into “data source” and tried uploading that same source into that table.
It then gives me an error saying the number of columns do not match.
How do I get rid of your wdt_ID column that is apparently causing these faults.
Hi Zach,
You will not be able to remove our wdt_ID Column, that is the primary Column needed for the Manual tables to function.
We are unable to reproduce the scenario you described in the latest messages;
we can use any Excel Sheet as the initial data for importing/making a new Manual Table;
then we can again use the same Sheet to update the existing Table without any errors.
1. Can you please first record your screen and send us a Video, so that we can see the exact steps, how it looks when you import your Excel initially to make a new Manual table;
then how it looks when you try to update that table later with the same Excel file/ how the error happens on your end?
If the Video gets too large for the ticket, upload it to weTransfer and send me a download link.
2. Then we can remote in to your Site and try to investigate how that happens, since we are unable to reproduce it on our end.
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.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
I genuinely hope you find that I’m doing something wrong so I can figure this out. Here’s the video:
https://we.tl/t-510AjLVFdx
H Miloš,
Just checking for an update on this.
Thanks,
Zach
Hi Zach,
My sincere apologies this is taking so long.
I am looking into this with the help of our 2nd level Team and going to report back as quickly as possible.
Thank you for all your patience.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Miloš,
No problem. Happy to know it’s not something obviously wrong I’m doing. I also verified I had the latest version of this (5.8.2) with auto updates on.
Thanks,
Zach
Also Now hesitant to upload any documents to any tables.
I tried uploading this spreadsheet to the table you created for it. It worked. If you made this Table to correspond with this file, the only thing I changed was adding one link to one of the rows. Everything else remained the same. Also it was not on a column header row that I added the link just to be clear on that.
For further information - I deactivated the plugin on my backup/sandbox/developer website. The buy/hold/sell page holding that wpdatatable shortcode came back up. Reactivated the plugin and it made that critical error on that page again. Seems like uploading a spreadsheet into anything makes the table become lost.
No other tables or pages containing those short codes are affected.
Miloš,
Final update for now:
I curiously made a new Buy/Hold/Sell chart using the same exact file that caused the critical error (also the same file I was using everyday to update it). It worked. Then I went into the Table and tried uploading it again just to be sure before I configured the chart to how it looked before all these errors (and to remove the critical error eyesore page from my site) and it worked again. So the temporary fix is in place….
The question now is just why did this happen and am I going to have to recreate every table I have again and upload the new short codes to each corresponding page before I upload the corresponding spreadsheets again? I’m currently scared to touch any table and I have some uploading work to do on some of them.
By the way I appreciate your help big time. Although it is extremely frustrating all these unknown errors are happening to me.
A further question I have is has anyone else experienced this where tables created on an older update (like my old 5.8.3) cause a critical error if the same spreadsheet is uploaded again on the version this was updated to? And further if it’s common to have to play hot potato with recreating tables all the time due to the seemingly ghost errors (the last issue) that can’t be recreated or that cause critical errors in this case?
Here is the good file in case you need to inspect it. this is the one I just used to create the new Table. Also the same one that caused the critical error on the old one.
If you need to see the corresponding table in wordpress it is [wpdatatable id=73]
The url is still https://brainyballers.com/buy-hold-sell-chart/ (I had to deactivate the plugin momentarily and change the shortcode to get around the critical error message.. in case you’re wondering how I changed it with a critical error)
For now I’m leaving all the bad “Buy/Hold/Sell” tables in the plugin just in case you want to see the critical errors. It’s just a message so there’s not much to see but just in case.
Attached files: Buy Hold Sell Official.xlsx
Miloš,
This worked. I cautiously uploaded the charts with the new fonts to the backup and it worked so I applied it to the front end table and it again worked.
Thank you so much for working through all of this for me. As frustrating and scary as it was when my site page went down (the best feature on my site so far too.. just didn’t want to say that in the moment to add to any pressure on you) This plugin has been phenomenal.
As tedious as it can be too it’s still much worth it. Thank you so much.
Zach
Milos,
The solution found clearly was the issue. Although, my main device is IPad. It appears as though IPad or IOS doesn't always understand what an unformatted cell looks like.
Or at the very least it doesn't correspond with wpDataTable's definition of what that is.
For Example, I created a new excel document, and without touching any formatting I simply typed in my header rows and then uploaded and got that critical error that you ended up finding out was the formatting issue.
Is there a known work around to this? I even clicked on a random cell I never touched and pasted just the format. No luck. I've looked up on multiple forums IOS formatting las well. No luck there.
Miloš,
Just an update. I now do not think the formatting issue was the issue. I’m going to make a video explaining why.
What you’ll see is I duplicate a good “buy-hold-sell” wpdataTable and also a “rookie mock draft” wpdatatable.
What I will do is show you the good mock draft wpDataTable, and I will then save and upload the corresponding mock draft excel file into that Table where you will see the table in wpDataTable break.
I will then proceed to copy the header from that excel file which broke the “mock draft” wpDataTable into the corresponding “buy-hold-sell” excel file then proceed to upload that buy-hold-sell excel file into the corresponding wpDataTable for that file where you will see it succeeds using the header format which broke the other chart.
https://we.tl/t-nVcFbilOeu
Further, I was never able to view able of your videos using WeTransfer as even after I downloaded them my research could not find anything showing me how to watch or reformat a .mkv file.
Further, I changed the font in the buy hold sell chart, saved, and uploaded. It still worked. There definitely is a different issue going on other than just the header font.
I looked into multiple things and thought hard about what the warning is trying to say.: “Column 'pos' cannot be null”
Tried allowing every column to “allow empty value” didn’t work. Got same error.
Tried deleting the “position” column and redoing it. Didn’t work. Same error.
Tried finding any hidden “pos” columns. Didn’t. Only the “position” column sounds like it but tried the above fixes to that column to no prevail.
Those are the top fixes I want to let you know I did. Everything else has been almost an hour of messing with fonts in excel and your plugin and a bunch of other different things. Although I realized it has to be something with my mock draft plugins. Maybe somehow I configured them just isn’t jiving with the most recent updates and my excel document anymore. Although I feel as though I’ve all but ruled out the header format being the issue.
Do you have any sort of troubleshooting code sheet you can pull up to look deeper into the “Column 'pos' cannot be null” warning? Maybe some developer has this. Usually those have an explanation attached to each code even if they’re hexadecimal to make them understandable. I copied and pasted that text from the warning so what you see is exactly as it shows: Column 'pos' cannot be null
Miloš,
Can I get your opinion on my video where I copy the format from an excel file that breaks the wpdatatable into another excel file where it then does not break the wpdatatable?
I was able to watch the video this time. Although it doesn’t really address that point where I copy the format from one excel file into another and try uploading to two different wpdatatables and get 2 different results.
Are you aware if Microsoft Excel’s default font change in January? They changed to Aptos. The buy hold sell table on excel that I am able to upload is still defaulted to Calibri add I believe I made that table before that update. Calibri IS unformatted in that spreadsheet.
The table that throws me the critical error in wpdatatable defaults to aptos. I tried changing the header font and I got two different results: one time the critical error then the next got a non critical error just saying it doesn’t recognize any headers.
Hi Zach,
My apology, I missed to comment on the Excel default font change.
I am confident that the font type should not have any effect on these issues.
I believe we are getting close to isolating what happens for the importing of Tables and updating them.
It seems it is related to that old 'issue' we had for a long time, as described in my previous reply, which is now fixed in the 6.3.2 wpDataTables version;
but it seems we have it completely fixed only when we 'link the table from Excel', but for some specific file it seems the issue still happens when importing the data for editable tables, our Plugin seems to be 'picking up' that there is 'something' after the last Column which 'was there' or 'should be in some cell that does not have a header name' and so on...
For example, I did notice on your last Table #122, in that Table you got one more additional Column "Team" which was not in the Excel file you sent me - that file had one Column less;
so if you can recall if you maybe did that scenario - to have more columns first, then to delete some column and save that Excel.
A scenario like that can 'trigger the issue' where Excel uses that 'cache' to 'memorize there was something there after the last column' and thus our Plugin 'picks that up'.
So to summarize, I believe there should be no font isuses, but if you can just try to keep the same number of columns, same header names when you are updating existing Manual tables, now from version 6.3.2, this issue should then stop happening for new tables.
Let us know how all that seems and if that can work going forward for your use-case.
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Miloš,
So just to clarify, are you saying I should be able to upload the chart I provided to a new table in wpdatatables to make a new table with 6.3.2?
You were correct that I was missing a column, my apologies on that.
I tried the linked tables and it seems to work like a charm. When uploading an excel spreadsheet, should everyone lean towards the link option and not the manual excel spreadsheet upload option? I never understood the difference between them but if the linked is expected to be more consistent than the manual option has then I’m going to recreate all of my charts to be the linked option. This absolutely should work.
The Buy Hold Sell Table is working as always but with the old manual Table. Tried changing it to a linked table and wasn’t recognizing the repeat columns. Everything else is linking so just a heads up I could be back if that BHS manual chart also stops working at some point. Thank you so much for all your help!