netton1956

Kind regards,

Ton

Found a quick and dirty solution:

innodb_strict_modeOFF

ThnX for getting me in the right direction.

Ticket can be closed.

The current table:

-- Tabelstructuur voor tabel bfmCy0s7_tablesome_table_260

CREATE TABLE bfmCy0s7_tablesome_table_260 (
id bigint(20) UNSIGNED NOT NULL,
post_id bigint(20) UNSIGNED DEFAULT NULL,
author_id bigint(20) UNSIGNED DEFAULT NULL,
created_at datetime DEFAULT '0000-00-00 00:00:00',
updated_at datetime DEFAULT '0000-00-00 00:00:00',
rank_order varchar(255) DEFAULT NULL,
column_4 text DEFAULT NULL,
column_5 text DEFAULT NULL,
column_6 text DEFAULT NULL,
column_7 text DEFAULT NULL,
column_8 text DEFAULT NULL,
column_9 text DEFAULT NULL,
column_10 text DEFAULT NULL,
column_11 text DEFAULT NULL,
column_12 text DEFAULT NULL,
column_13 text DEFAULT NULL,
column_14 text DEFAULT NULL,
column_15 text DEFAULT NULL,
column_19 text DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci

After disabling the Debug plugin and restoring the wp-config.php the site returned to the previous state. The form is stored, the original problems with tablesome remain.

First action, filling the form:

This Debug plugin is a bit of a pain in the ass ?? It ‘destroys’ my homepage, and the console acts very strange:

autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303 POST https://desmaakvanespresso.nl/wp-json/contact-form-7/v1/contact-forms/504/feedback net::ERR_INTERNET_DISCONNECTED
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
n @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
l @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303 {code: ‘fetch_error’, message: ‘You are probably offline.’}code: “fetch_error”message: “You are probably offline.”Prototype: Object
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
Promise.catch (async)
l @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303
(anonymous) @ autoptimize_13c834859a432a75e5e1c8df37345f77.js:1303

I can assure you I am definitely not offline ??

The errorlog contains:

[16-Feb-2023 08:25:46 UTC] NOT NEW INSTALL
[16-Feb-2023 08:26:41 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:01 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:02 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:08 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:09 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:15 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:18 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:43 UTC] NOT NEW INSTALL
[16-Feb-2023 08:27:49 UTC] NOT NEW INSTALL
[16-Feb-2023 08:28:20 UTC] NOT NEW INSTALL
[16-Feb-2023 08:28:51 UTC] NOT NEW INSTALL
[16-Feb-2023 08:30:21 UTC] NOT NEW INSTALL
[16-Feb-2023 08:30:52 UTC] NOT NEW INSTALL
[16-Feb-2023 08:32:13 UTC] NOT NEW INSTALL
[16-Feb-2023 08:32:16 UTC] NOT NEW INSTALL

The messages on screen however do point to ‘something’:

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_21 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_24 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_25 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_24_meta text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_25_meta text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_21 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_24 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_25 text default '';

WordPress databasefout: [Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_24_meta text default '';

WordPress databasefout:?[Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs]
ALTER TABLE bfmCy0s7_tablesome_table_260 ADD COLUMN column_25_meta text default '';

This probably causes the problem with the second action, which for now I didn’t perform.

Hi Essekia,

Thanks for your prompt reply!

It is a very nice plugin!

The workflow:

The Forms settings:

Hope this is what you mean!

Regards,

Ton

Hi Danny,

Apologies! Still a bit shaky from the infection, It indeed looks like having been a rather persistent caching problem.

So it is resolved indeed, thaks for the help.

Kind regards,

Ton

Hi Danny,

Was caught with a bit of a bacterial infection, so sorry for my late reply.
I did what you advised (it was http, as that was the way the site started out, the ssl certificate was applied later), but now that’s fixed:
WordPress Address (URL)
https://scottishdommeshop.com
Site Address (URL)
https://scottishdommeshop.com
I deactivated and reactivcated your plugin, but still get the same error….

Hope you can advise some more.

Kind regards,

Ton

• This reply was modified 5 years, 7 months ago by netton1956.

I know ??

The image i use now is 1600 x 850 px:
<div class=”custom-header-media”>
<div id=”wp-custom-header” class=”wp-custom-header”></div>
</div>

and the cropped images show this:
779 X 624 pixels (intrinsic 1600 x 850 pixels)

Hoovering over the image url here shows the image as is, complete. So where the ‘cut-off’ at the bottom comes from is stil a big mystery tp me…

I’ll ask the one creating the images to extent it tp a 1600 x 1200 px one, but that doesn’t solve this mystery…

Yes, i know, same problem there.
I used 2000 x 1200 px on twentyseventeen and 1600 x 850 px on pureBlog. Why are these sizes advised when they will be cropped, is what i like to know.

Creating a new image is not the problem, the question is what size. Any idea?

Yur advice is very much appreciated!

I know that is too much ?? On purpose to show the image is cropped despite the advised height is used. The same happens in theme twentyseventeen. When installed the default imnage is shown completely, but when I change that to an image of my own, srcset is added to the img-tag and the image gets cropped vertically ;-(

So again: HELP!

Hi,

Thanks for your quick reply. When i add this css however, the top of the image goes off-screen, anf at the botton a part is gone and now black…

Please help!

Kind regards,

Ton

This item can be closed.
I assumed a missing close tag or quotation mark so the content of a cell further on in the table was rendered too.
It turned out to be something different. When the title was of such a width that the closing mark X needed a new line, it was rendered on a new line with opacity zero. In this way a see-through window was created in the tippy frame itself, showing content lying below. I found this out when I moved the tippy frame out of the way. I was so focused on a missing whatsoever that I was blind for this obvious solution.

Hi,

All problems fixed due to your fast and great help!

Thank you very much.

Regards,

Ton

Dear Tobias,

I experience the same problem here.
Both pagination and search box disappeared overnight.
jQuery is loaded:
`<script type=’text/javascript’ src=’https://www.boekentaal.eu/wp-includes/js/jquery/jquery.js?ver=1.11.0′></script&gt;
<script type=’text/javascript’ src=’https://www.boekentaal.eu/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1′></script>&#8217;
and the console displays no error or warning.
Would you be so kind as to take a look?
Thanks in advance.

Kind regards,

Ton