opusklassiek

I noticed that it is working on Desktop (except Firefox) and Android (GSM), but not on iPad. Safari I don’t know because I don’t use it on desktop.

As said: GOT IT, but it does not work on iPad. It works on desktop and Android GSM though.

GOT IT!

No luck, Tobias. Same problem.

This is it stands now:

.tablepress thead th,
.tablepress tfoot th {
background-color: #F8F8F8;
color: #FFFFFF;
}

.dataTables_filter input[type=search]::-webkit-search-cancel-button {
-webkit-appearance: searchfield-cancel-button;
}

It still doesn’t work.

After adding the code I get this after saving (first portion is red coloured and automatically removed):

.tablepress thead th,
.tablepress tfoot th {
background-color: #F8F8F8;
color: #FFFFFF;
-webkit-appearance: searchfield-cancel-button;
}

I suppose this is it. In the search field there is no clear button.

Hi Tobias, liebe Grüsse!

Readers told me that when they use the ‘search’ option on the (home) table page that after having found what they had been looking for, not to be able to go back to the main page. I told them to clear the search box, which brings them automatically back to the home table page. Maybe, it would be better to have the ‘previous’ page option, clicking as much as needed to go back to the main page. That would be more intuitive, I think. Thank you for your attention.

Sorry, Tobias. Error seemed to be mine. Thank you for your excellent help.

Seems to be an error in the code: no page numbers and no pagination.

Dearest Tobias,

I think that basically this should NOT be the default behavior as it is most inconvenient to visitors when dealing with a large table, like ours. And, additionally, the default should also be page numbers at the bottom, which are now lacking (only <previous and >next now). But apart from that: the default value (back to the first row of the table when clicking the < button in the browser) does not apply to all browsers and/or PC’s. I have four PC’s here, and with two of them there is no problem: when using the < bottom the browser page remains to be the (correct) last one coriginally clicked on and not the first part of the table. Last but not least the row number should be extended to ALL and not just to 100 (current limit). These are in my opinion nothing more but basic rules for any data table, and should not be part of any premium version. Thank you for your attention.

• This reply was modified 1 year, 7 months ago by opusklassiek.

This is indeed an important issue. I think this should have been included in the data tables as an option right from the beginning. In a database of more than 100 rows the visitors have no clue that there are more than just the given maximum of 100. Our database contains 200 rows, but the box does not reach further than 100. Weird!

Indeed, it has disappeared this morning!

Wordpress 5.8.3, php 8.0

This is the error message:

Een fout van het type E_ERROR werd veroorzaakt op regelnummer (line no.) 90 van het bestand /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php. Foutmelding: Uncaught Error: Failed opening required '/home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php' (include_path='.:/usr/share/pear') in /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90
Stack trace:
#0 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-listener.php(402): Automattic\Jetpack\Autoloader\jpf11009ded9fc4592b6a05b61ce272b3c_jetpack?10_4\PHP_Autoloader::load_class('Automattic\\Jetp...')
#1 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-listener.php(338): Automattic\Jetpack\Sync\Listener->get_actor('jetpack_plugins...', Array)
#2 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-listener.php(199): Automattic\Jetpack\Sync\Listener->enqueue_action('jetpack_plugins...', Array, Object(Automattic\Jetpack\Sync\Queue))
#3 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(303): Automattic\Jetpack\Sync\Listener->action_handler(Array, Array)
#4 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
#5 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#6 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/modules/class-plugins.php(173): do_action('jetpack_plugins...', Array, Array)
#7 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(303): Automattic\Jetpack\Sync\Modules\Plugins->on_upgrader_completion(Object(Plugin_Upgrader), Array)
#8 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array)
#9 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#10 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-admin/includes/class-plugin-upgrader.php(371): do_action('upgrader_proces...', Object(Plugin_Upgrader), Array)
#11 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-admin/includes/ajax-actions.php(4477): Plugin_Upgrader->bulk_upgrade(Array)
#12 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(303): wp_ajax_update_plugin('')
#13 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)
#14 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#15 /home/vhosts/opusklassiek.nl/httpdocs/wordpress/wp-admin/admin-ajax.php(187): do_action('wp_ajax_update-...')
#16 {main}
  thrown

Hi Serge,

I was just told by www.ads-software.com that the post/topic cannot be removed. There is no permission to do so as there are no ‘security risks’ by posting the debug.log.

I see no admin section right from messages.