I can confirm there will be no way for any user to reach the source Google Sheet from our linked table on your Page.
Even if the user has coding skills, they can only inspect the HTML and see the data which you present in the table, but nothing more than that.
In regards to this "Share" option. When you set a Sheet to be "anyone with the link can view". This means that only the people who you send the link to, are going to be able to click this link and see your Sheet. So it is perfectly secure in terms of nobody being able to reach the source Sheet from our table or the WP Page. In that sense, there is nothing to worry about.
In regards to the difference between our 'standard' Google sheet connection and using the Google API:
By default, when you edit something on the source sheet, this change shows in our table within 15 minutes, because this data is saved in the Google cache.
If you want to avoid Google's cache, you can try the Google API Method and see how that works.
The advantage of the Google API is that you can use private sheets ( doesn't have to be published). Just note that, in terms of security, as explained above, nobody can access published sheets either from the table, so both ways are secure in that regard.
In terms of performance, they are both absolutely the same.
If you make larger tables, like more than 2, 3 thousand rows - We recommend using our Cache and Auto Update Cache Feature. This is saving the row data in our own cache in your WP SQL Database, and makes the table load faster ( for larger tables).
You can also set up a custom update time interval with our Cache feature ( for the table to update data from source Sheet editing), so it can be shorter/or longer than 15 minutes via Cron Job ( the instructions are on the Documentation linked above).
My personal recommendation is to just use the standard Google Sheet method for small tables ( less than thousand rows). If any table gets larger, like 2, 3 thousand rows - Use our Cache and auto Update Cache for better performance and custom update interval.
Just note : If a table goes over 5, 6 thousand rows - Then the performance will suffer, it will become slower and slower, the larger it gets.
In that case, for that table, we recommend to switch to importing it into a Manual table - then you will have our server-side processing in that table, for much better performance. This is great for very large tables ( more than 5, 6 thousand rows).
Once the table is created, it is no longer linked to the source file, so changing data in the table will not show up in Excel or Google Spreadsheet, and vice-versa.
Hello, in the instruction there is mentioned:
"What you need to do in your Google sheet is to share this sheet with anyone."
Will all people visiting my website be able to check shared Google table and look down deep into data like automated scripts, data sources etc?
How can I prevent it? Will following another instruction 'connect WordPress tables with Google Sheets API?' change something in the mentioned respect?
Please clarify and recommend some solutions, their pros and cons.
I need to build relatively small data table, but will need to automate data updates. As of now, Im not into Excel or SQL db.
Hi Michal,
I can confirm there will be no way for any user to reach the source Google Sheet from our linked table on your Page.
Even if the user has coding skills, they can only inspect the HTML and see the data which you present in the table, but nothing more than that.
So it is perfectly secure in terms of nobody being able to reach the source Sheet from our table or the WP Page.
In that sense, there is nothing to worry about.
By default, when you edit something on the source sheet, this change shows in our table within 15 minutes, because this data is saved in the Google cache.
If you want to avoid Google's cache, you can try the Google API Method and see how that works.
The advantage of the Google API is that you can use private sheets ( doesn't have to be published).
Just note that, in terms of security, as explained above, nobody can access published sheets either from the table, so both ways are secure in that regard.
This is saving the row data in our own cache in your WP SQL Database, and makes the table load faster ( for larger tables).
You can also set up a custom update time interval with our Cache feature ( for the table to update data from source Sheet editing), so it can be shorter/or longer than 15 minutes via Cron Job ( the instructions are on the Documentation linked above).
If any table gets larger, like 2, 3 thousand rows - Use our Cache and auto Update Cache for better performance and custom update interval.
Just note : If a table goes over 5, 6 thousand rows - Then the performance will suffer, it will become slower and slower, the larger it gets.
In that case, for that table, we recommend to switch to importing it into a Manual table - then you will have our server-side processing in that table, for much better performance.
This is great for very large tables ( more than 5, 6 thousand rows).
If you import the file, the plugin reads the source file and creates a manual table.
Once the table is created, it is no longer linked to the source file, so changing data in the table will not show up in Excel or Google Spreadsheet, and vice-versa.
This table will be editable in our Plugin.
If you need quicker editing, you can either switch to the Excel-like view,
and then select and copy the range of cells you want to paste from the source file, and paste it in the Excel-like view,
or you can Update manual tables from source files (CSV, Excel or Google sheet) with three options :
I hope that helps. Let me know if you have any questions.
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
Hello Miloš, your explanation helps. I dont have any further questions in this matter.
Thank you!