Hi Morten,

you can add this custom CSS to remove this padding around the table :

.wpDataTablesWrapper {
    padding: 0 !important;
    padding-top: 0px !important;
    padding-right: 0px !important;
    padding-bottom: 0px !important;
    padding-left: 0px !important;
}

If you need it just for this table, add this in table's Customize/Custom CSS;

or if you want the same style in all tables/remove padding;

add it to main plugin settings/Custom JS and CSS/Custom CSS.

Let me know if that helps.

Hi Morten,

1. In regards to the white frame around the table,

I am not able to see it on mobile, it looks the same as on desktop for me.

Can you try to highlight the area you are referring to on a screenshot, and compare it to how it looks on the desktop?

2. In regards to the border, yes - I can see this table header, for some reason on the mobile screen is showing the bottom border.

You can add this CSS, and the header's bottom border will be removed :

.wpdt-c .wpDataTablesWrapper table.wpDataTable thead th {
    border-bottom: 0 !important;
}

If you need it just for one table, add it in the table's Customize/Custom CSS;

or if you need this for all tables, add it to main plugin settings/Custom JS and CSS/Custom CSS.

Let me know if that helps.

Hi Morten,

i can see now, when I checked on another monitor,

this screen has more accurate colors, so I can see the white area and the gray color around it,

on the previous screen it all seemed kind of "white-ish" to me.

Can you try adding this CSS to your table's Customize settings,

.wpDataTablesWrapper table.wpDataTable {
    margin: 0 auto !important;
    margin-top: 0px;
    margin-right: auto;
    margin-bottom: 0px;
    margin-left: auto;
    width: 100% !important;
    padding: 0 !important;
}

or in the main plugin settings/Custom JS and CSS/Custom CSS,

if you wish to try add this style to all tables.

Let me know if that helps.

If not, can we also try some tests from the back-end settings?

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.

Hi Morten,

here is a CSS you can add, and this will affect only mobile screens because we are adding a "media query" breakpoint :

@media screen and (max-width: 769px)
.wpdt-c.wdt-skin-aqua .wpDataTablesWrapper div.dt-buttons {
    margin-top: 0 !important;
    padding-top: 0 !important;
    display: none !important;
}

I will also speak with our developers about this soon,

because I had a couple of other users that complained about this "gap" above the table that happens if we disable Table Tools,

but this element is somehow still in the HTML structure so it creates that "gap" that is the container for Table Tools.

We will do our best to improve that,  and to make some "conditional" logic for the Plugin's structure,

so that it removes the top gap when Table Tools are disabled;

That is my idea at least, we will see how difficult it is for the devs to add this.

I can't promise an ETA, but we will start working on it as soon as possible.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), 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.

Hi Morten,

no problem, i am happy to help.

2. In regards to the "Too many Requests",

What happens is,  when we have our auto-update cache enabled,

while using the Google Sheets API method,

any time the cron runs,  it does a couple of calls for each individual table connected with Google Spreadsheets API in order to get the information about the source Spreadsheet.

Due to Google API Quota limits,  in situations when users have a lot of tables on site,

it results in too many Google API calls and goes over the Google's Quota limits, 

that is why you can get the "Too many requests" errors from the Google API.

You can see more about that quota here.

-

A solution for this use-case can be one of two options :

1. You can either disable the Google API ( Remove your account information in our plugin settings/Google Spreadsheet API settings.

if you do that, then our plugin is going to "switch" to using the "old" Google Spreadsheet connection method for tables, and you will not be getting these errors from Google API.

( This method just has a limitation, it is not possible to use Private Spreadsheets)

2. Or, if you have to use Google API method to connect tables, 

that quota can be increased, but that requires an additional charge from Google (increasing the quota is not free).

you can see more about that on the page I sent, under section 'Request a quota increase'.

I hope this helps.

Hi Morten,

no problem, i am happy to help.

-

1. The sheet is shared so that everyone with the link can view. I assume that is enough to make the "old" Google Spreadsheet connection method work?

- Exactly, now it will work with the 'old Google Sheet method' without the API,  when you Publish the Sheet and set sharing to 'anyone with the link'.

2. If I want to change to the "old" Google Spreadsheet connection method all I have to do is remove the Google service account and all my tables/charts will still work after that? It would be quite a lot of work if I where to recreate them all.

- Yes, no worries about that, our Plugin will keep absolutely all data and table/chart settings the same,

if you remove the Google API Call from the mix, so no need to recreate anything.

3. What is the drawback from not using the Google API method? Apart from the sheet having to be shared with everyone. Any other drawbacks?

- No, the only limitation is for a scenario if you have to use Private Sheets;

but apart from this, there is not any technical difference in performance, etc;

You can just try our Cache and Auto-Update Cache feature,  and with this you can set up a Cron Job which can update your linked table in the time interval you set;

and this can also improve performance in table load, for example if you got tables of a couple thousand rows;

If any table goes above approximately 5, 6 thousand rows , then you will see too much slowing down for the load,

at that point, for larger data sets it is recommended to try importing the Sheet Data and go for the SQL based tables - then you have our server-side ( lazy load) processing feature.

-

Let me know if you have any additional questions.

Hi Morten,

1. Happy to hear that switching to the standard Google Sheet method without API has got rid of that error, great!

2. In regards to that left border on the last Column, yes, that looks weird.

I just did some 'quick' CSS fix that seems to do the trick.

You can try this selector - it will 'target' the last column :

.wpDataTablesWrapper table.wpDataTable tr td:last-child {
    border-left: 2px solid black !important;
    
}

Or, if you want to use this selector on any other specific Column,

you can add the Column name in the selector, like this :

.wpDataTablesWrapper table.wpDataTable tr td.column-bm {
    border-left : 2px solid black !important;
}

In this case, this origin column name was "bm" , so after "td."  we have "column-bm",

but for any other case/column name, you can check in the HTML what is that column selector,

and change it to "column-ColumnName".

I hope  that helps.

Hi Morten,

apologies for the waiting time once again.

I see what you mean. At this point, we might need to check this table setup from the back-end, too,

and have a closer look at everything.

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.

Hi Morten,

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.

-

This dashed left border comes from a line of Custom CSS which you added to this Table #38 on the page.

When we check the back-end of the table,

you added this CSS class to the last column "frontpagebenchmark1_column",

and in the Custom CSS of that table, you set the dashed left border on it.

table.wpDataTable td.frontpagebenchmark1_column  {
    border-left: 1px dashed #113049 !important;
     }

If we comment out that line, then this column has no left border.

So, it will be best if you can go through all your Custom CSS for this table,

and also i notice you have some Custom CSS added in the main Plugin settings;

Then check which styles you need, and which ones are not necessary.

Let me know how it goes, i hope it helps.

Hi Morten,

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.

-

Yes. In most situations like this, when we start adding Custom CSS, the more you add from your end,

it adds another level of difficulty to determine exactly which CSS might be causing some other issue.

The best is to first remove all the added CSS and see how the table looks,

then to go in and try to isolate it.

In situations like that, we are limited how much we can troubleshoot, depending if only some basic CSS is added,

but in this case, i am happy to see you found this main root of the issue.

Thank you for letting us know what it was.

Please don't hesitate to open new tickets if anything else comes up, we will do our best to help.