If you insert a table multiple times on a page as a shortcode, the same method is always rendered.
I still think that you don't need these variables when you deactivate the editing mode on the user front end. Values that are needed separately from edit mode, such as paging, should be put in a separate variable set. So that only the necessary variables are rendered. This drastically reduces the content, which would be very, very important for SEO.
In regards to the point #1, the same method always rendering for inserting a table multiple times;
Yes, this is the current behaviour, but I will pass this feedback to our developers.
They will do their best to make an improvement on that, but we can't say an ETA on it.
For #2, the variables you mention, if you mean the JS files from your screenshot :
If I recall properly, the developers explained that these scripts are needed for our table's basic JS functionalities, but I am sending this to them just to be sure.
If an improvement is possible on that point as well, they will do their best to achieve it or remove it if it is not absolutely necessary to achieve better SEO optimizations.
In regards to #3, the Suggested Feature, we still did not make significant progress on that improvement, I'm afraid.
Our management and the developers are doing their best to handle all the requested improvements and tasks according to how many users requested it and combined with other priority tasks, so we can't say a realistic ETA on that, too.
Sorry that we are not able to provide any estimates at this time for this.
You are absolutely right, I have already mentioned this topic and the reason given was that it is needed in the tables.
But I have looked at the values more closely again and have found that you definitely do not need around 70% if you are not in the admin area and have not activated the edit mode in the user frontend.
Excample:
- "tableNameEmpty":"Table name cannot be empty! Please enter a name for your table."
Why do I need the value for entering a table name if you as an end user cannot enter a table name on the website?
- "invalid_email":"Please enter a valid email address for the field"
The same applies to the email address. If I have deactivated the edit mode, I cannot enter an email address, etc.
- "settings_saved_error":"The plugin settings cannot be saved. Please try again or contact us via the support page."
I can only make settings for the plugin in the administration area.
As an example, I have marked all the fields that could be removed.
The files should be structured and loaded in such a way that the user is loaded depending on the mode. To do this, the files would only have to be structured differently.
based-strings - Strings that are absolutely necessary in every mode (such as paging, button-names, status information ...)
admin-strings - Strings that are used in the administration area
edit strings - Strings that are used in edit mode
I hope I was able to describe the whole thing a little better for the developers.
Hello again,
If you insert a table multiple times on a page as a shortcode, the same method is always rendered.
I still think that you don't need these variables when you deactivate the editing mode on the user front end. Values that are needed separately from edit mode, such as paging, should be put in a separate variable set. So that only the necessary variables are rendered. This drastically reduces the content, which would be very, very important for SEO.
The last point is once again a small status query on this point. Is there anything new here?
https://features.wpdatatables.com/202
Kind regards
Jens
Hi Jens,
In regards to the point #1, the same method always rendering for inserting a table multiple times;
Yes, this is the current behaviour, but I will pass this feedback to our developers.
They will do their best to make an improvement on that, but we can't say an ETA on it.
For #2, the variables you mention, if you mean the JS files from your screenshot :
If I recall properly, the developers explained that these scripts are needed for our table's basic JS functionalities, but I am sending this to them just to be sure.
If an improvement is possible on that point as well, they will do their best to achieve it or remove it if it is not absolutely necessary to achieve better SEO optimizations.
In regards to #3, the Suggested Feature, we still did not make significant progress on that improvement, I'm afraid.
Our management and the developers are doing their best to handle all the requested improvements and tasks according to how many users requested it and combined with other priority tasks, so we can't say a realistic ETA on that, too.
Sorry that we are not able to provide any estimates at this time for this.
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š,
You are absolutely right, I have already mentioned this topic and the reason given was that it is needed in the tables.
But I have looked at the values more closely again and have found that you definitely do not need around 70% if you are not in the admin area and have not activated the edit mode in the user frontend.
Excample:
- "tableNameEmpty":"Table name cannot be empty! Please enter a name for your table."
Why do I need the value for entering a table name if you as an end user cannot enter a table name on the website?
- "invalid_email":"Please enter a valid email address for the field"
The same applies to the email address. If I have deactivated the edit mode, I cannot enter an email address, etc.
- "settings_saved_error":"The plugin settings cannot be saved. Please try again or contact us via the support page."
I can only make settings for the plugin in the administration area.
As an example, I have marked all the fields that could be removed.
The files should be structured and loaded in such a way that the user is loaded depending on the mode. To do this, the files would only have to be structured differently.
based-strings - Strings that are absolutely necessary in every mode (such as paging, button-names, status information ...)
admin-strings - Strings that are used in the administration area
edit strings - Strings that are used in edit mode
I hope I was able to describe the whole thing a little better for the developers.
Kind regards
Jens
Hi Jens,
Thank you for this update, which provides more details and helps clarify all the points needed for your desired SEO optimization improvements.
I am passing everything to our developer team; they will carefully review everything you have described.
While I can't guarantee they will be able to address all of these points, they will do their best.
We are currently unable to provide an ETA.
If they require any further clarification on any of these points/details during their work, we will reach out to you.
Thanks again for your continued suggestions for our plugin improvements; we greatly value them.
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