andynz

Thanks for taking the trouble to try and replicate the problem.
I did some further tests and it is ‘possible’ that the problem occurs when using the block editor on the Lightstart maintenance page – but goodness know how WP photo album gets involved.
Anyway, I can do without Lightstart (now deleted), but cannot do without WP photo album.

Tried to make a donation (you have also helped a few times in the past), but it seems that PayPal has restrictions on payments to other countries.

Andy

Sorry, I overlooked that option.

All Ok now.

Thanks for the reply.
I changed the settings as suggested and the formatting is improved but, instead of just one cover photo, thumbnails of all images are displayed (which I do not really want),
I thought that changing the short code to
[wppa type=”cover” album=”@all”]
might make a difference, but you can see that the two widgets are identical.

The change to settings has, of course, also affected non-widget displays as at https://test.pat.gen.nz/gallery/
With the original setting of Standard MCR, only one cover image was displayed as here (in a quite different site):
https://waibopscd.org.nz/gallery/

Album displays on normal pages are far more important to me than the widget displays so, I will revert to the previous settings if there is no obvious solution.

Thanks
Andy

Thanks for the advice and I agree that WP base should never be modified. This was a patch on my test site for evaluation.
However, here are links which appear to relate exactly to my problem (failed attempt to preview a block theme).

https://github.com/WordPress/gutenberg/issues/53284

https://core.trac.www.ads-software.com/ticket/59000

It does not affect normal operation of the website so I will wait to see if it is fixed by 6.3.2.

Thanks for your expertise which extends way beyond TablePress.

Andy

Further investigation indicates that the problem goes away if all of the following plugins are deactivated:
Tablepress
Password protected
WP photo album plus

Alternatively, I can activate all of the above and add the following code (found in another forum) to capabilities.php
include_once(ABSPATH . ‘wp-includes/pluggable.php’);

but this is probably not good in the longer term.

Andy

Thanks for your quick response. Here is the full log whenever I try to show a live preview of theme 2023.
I could not see how to attach a file to this post, so hope an embed is OK.

[05-Oct-2023 22:44:36 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_get_current_user() in /home/patgennz/public_html/wp2021/wp-includes/capabilities.php:877
Stack trace:
#0 /home/patgennz/public_html/wp2021/wp-includes/theme-previews.php(17): current_user_can('switch_themes')
#1 /home/patgennz/public_html/wp2021/wp-includes/class-wp-hook.php(310): wp_get_theme_preview_path('tempera')
#2 /home/patgennz/public_html/wp2021/wp-includes/plugin.php(205): WP_Hook->apply_filters('tempera', Array)
#3 /home/patgennz/public_html/wp2021/wp-includes/theme.php(317): apply_filters('template', 'tempera')
#4 /home/patgennz/public_html/wp2021/wp-includes/theme.php(328): get_template()
#5 /home/patgennz/public_html/wp2021/wp-includes/l10n.php(1306): get_template_directory()
#6 /home/patgennz/public_html/wp2021/wp-includes/l10n.php(1331): _load_textdomain_just_in_time('wp-photo-album-...')
#7 /home/patgennz/public_html/wp2021/wp-includes/l10n.php(185): get_translations_for_domain('wp-photo-album-...')
#8 /home/patgennz/public_html/wp2021/wp-includes/l10n.php(297): translate('General', 'wp-photo-album-...')
#9 /home/patgennz/public_html/wp2021/wp-content/plugins/wp-photo-album-plus/wppa-setting-see-also.php(15): __('General', 'wp-photo-album-...')
#10 /home/patgennz/public_html/wp2021/wp-content/plugins/wp-photo-album-plus/wppa-init.php(75): require_once('/home/patgennz/...')
#11 /home/patgennz/public_html/wp2021/wp-content/plugins/wp-photo-album-plus/wppa.php(15): require_once('/home/patgennz/...')
#12 /home/patgennz/public_html/wp2021/wp-settings.php(462): include_once('/home/patgennz/...')
#13 /home/patgennz/public_html/wp2021/wp-config.php(89): require_once('/home/patgennz/...')
#14 /home/patgennz/public_html/wp2021/wp-load.php(50): require_once('/home/patgennz/...')
#15 /home/patgennz/public_html/wp2021/wp-admin/admin.php(34): require_once('/home/patgennz/...')
#16 /home/patgennz/public_html/wp2021/wp-admin/site-editor.php(12): require_once('/home/patgennz/...')
#17 {main}  thrown in /home/patgennz/public_html/wp2021/wp-includes/capabilities.php on line 877

The trace mentions both my active theme ‘tempera’ and plugin wp-photo-album-plus, but disabling these makes no difference.

Running PHP 8.1.21

Andy

Thanks Tobias, for going the extra mile with a solution, as always.
Your suggested CSS is a good compromise.
Andy

Thanks Tobias, should have guessed that you would come up with a solution!
I have made a design change which avoids the need to search on a hidden column, but your idea is preferable so I will probably implement it later.

Thanks again
(10am here in NZ, so must be late at night with you!)

All seemed Ok, but I then found a snag with using CSS to hide a column. If I use datatables_buttons to export the table to Excel, the hidden column is included in the sheet.

This does not happen if I use hide_columns.

Andy

I have done a further test where the short code is:
[table id=57 responsive=collapse/]
As the table-width exceeds the width of the display, the table is displayed in collapse mode (green cross symbol in the first column).

If I add CSS:
.tablepress-id-57 .column-1 {display: none;}
and leave the short code as it is, the table is displayed in normal mode. Just the first few columns are displayed (no green cross symbol in column 1).

If I change the CSS:
.tablepress-id-57 .column-3 {display: none;}
and leave the short code as it is, the table is displayed in collapse mode (green cross symbol in the first column) with column 3 omitted.

It seems that the CSS method only works if the column to be hidden is not column 1. On reflection this seems quite reasonable. I will just need to move column 1 to a new position.

Andy

Thanks for the tip.
The leaflet map was coded with each short-code on a new line:
[leaflet-map zoom=”5″ height=”450″ lat=-40.83824 lng=173.7252058]
[leaflet-marker lat=-37.72 lng=175.12]Auckland [/leaflet-marker]
[leaflet-marker lat=-41.21 lng=175.47]Wellington [/leaflet-marker]
etc
The solution was to code them as a continuous text stream.

Andy
`

Thanks for the advice.

Those options certainly disable zooming of the map itself (but not, of course, the browser window in which the map is displayed).
Regards
Andy

That was a bit premature.
If I hide the header row (row 1), the fixedcolumns stops working.

Oh well, I will have to dispense with fixed columns on this table.
Andy

Thanks for looking into it, Tobias.
I have a rather unwieldy solution which is to:
– Leave row 1 as it is (although cells can be cleared).
– Option settings: Row 1 is header
– Enter headings in row 2 which is formatted as a header.
– Set row 1 to non-display.

Note that row 1 has to be defined as a header in order to allow datatable functions.

Regards
Andy