hyssop
Forum Replies Created
-
The lockout team quickly resolved the issue. Thanks, again!
-Pete
Email sent.
Thanks!
Forum: Themes and Templates
In reply to: [Twenty Twenty-Two] Separate header template for mobile view@zoonini I agree. I think the simplest way would be template (and template part) controls that would allow for mobile and non-mobile visibility (toggle for one, the other, or both).
Forum: Themes and Templates
In reply to: [Twenty Twenty-Two] Separate header template for mobile viewHi @audunmb,
I ended up here while looking for the ability of having a different header logo for mobile (vs desktop) in the 2022 WP theme. My solution for now is adding a second image (for mobile) to my header. Both logo images are inside a vertical stack that’s inside a cover image. I added a class for each image and for the cover image in advanced, then used CSS to toggle the logos on/off, and to control the way the cover background image reacts. Here’s my CSS. It works perfectly. But… (see below)
.header-cover{ background-size: contain !important; min-height: auto; } .logo-mobile { display: none; } @media screen and (max-width: 782px) { .header-cover { background-size: cover !important; } .logo-mobile { display: unset; } .logo-wide { display: none; } }But… it would make more sense to have a mobile/non-mobile/all display option for templates as you asked about.
Related to this, FSE’s preview should respect that setting, as well as any custom CSS (which it ignores currently) as it does in the customizer preview. As it is now, I get to look at 2 logo images stacked in my header in the FSE editor.
I just checked Debug Log and it reads as follows:
[2019-09-04 19:01:53] API.INFO: Contact set to be created [“Extra information”,[{“form”:”Sign up for updates!”}]] []
[2019-09-04 19:01:54] API.INFO: http.status.bad_request: Bad request. [“Extra information”,[“[object] (stdClass: {\”error_key\”:\”http.status.bad_request\”,\”error_message\”:\”Bad request.\”})”]] []
[2019-09-04 19:01:54] API.INFO: Submitted contact data [“Extra information”,[{“email___ecd412e904309dcce66177488240b016”:{“key”:”email”,”val”:”[email protected]”},”email”:”[email protected]”,”list”:”1″}]] [](Please note: the staging version of the same site did NOT show this warning. AFAIK they are in perfect sync, except that the staging site doesn’t get contacts. So this must be related to visitor activity.)
-Pete
Support is already enabled. Debugging is currently empty. I will post back if/when it populates.
Understood… Thanks for the explanation.
-Pete
Hi @wfdave
I am aware of how to disable strict mode (but that’s only a stop-gap). That is supposed to result in errors being converted to warnings, but does seem to solve the errors. Doing as you suggested seems to support that finding. But…
On other applications that I have written, I have been able to insert IGNORE into the INSERT INTO statement to resolve the issue temporarily (until I can rewrite it properly). This has the advantage of not having to globally disable strict mode so I can see what else needs a tweak (like WordFence, apparently). I am using MariaDB 10.3.x and assume you are aware of the recent enforcement of strict mode. So I am wondering what db versions your code is tested with so far.
This is why I asked what I did above… I quote it again here:
“Have you tested you code with the latest MySQL/MariaDB versions? (If so, which are compatible?)
If you would provide me the file name(s) and (approx) line numbers for the INSERT INTO statements for the wfConfig and wfHits tables I will test whether adding IGNORE stops the errors/warnings. I went looking for these already, but couldn’t determine it exactly, not being familiar with your coding.”
Thanks, and please reply as soon as you can so I can test this (adding IGNORE) work-around.
-Pete
Strange about the email subject, but I won’t worry about it.
The warnings/errors I reference are SQL related in the db, and I’m thinking it’s related to strict mode being enforced beginning with MySQL 5.7 (and the MariaDB counterpart). The warnings are in the thousands, but what concerns me most are the table insert errors. (There were also db table crashes initially after the upgrade, but they cleared up upon table repair, and have not reappeared.)
I’m hoping WF will help me find the proper place in their code to modify for testing – it’s simple to do, but not easy to find based off of the error message itself. I’ll wait for someone to respond, if ever…
I understand you not wanting to take the time to check. Thanks anyway.
-Pete
Thanks @mountainguy2 At least I know my posts aren’t invisible. It’s true that free version users need to be patient. (“What do want for nothing, your money back?!” 😉 )
The subject line is what got me worried, but maybe it’s only that way for threads I initiate. Can you tell be what your email notification subject is for this post (if you email notifications)?
Also, would you be willing to check for the performance_schema errors/warnings on your installation? See my other post for details. (If that db is empty it needs to be turned on; I think it’s off by default.) In addition I’d like to know your WordPress, WordFence, and DB versions.
-Pete
What do you suggest? Have you tested you code with the latest MySQL/MariaDB versions? (If so, which are compatible?)
If you would provide me the file name(s) and (approx) line numbers for the INSERT INTO statements for the wfConfig and wfHits tables I will test whether adding IGNORE stops the errors/warnings. I went looking for these already, but couldn’t determine it exactly, not being familiar with your coding.
-Pete
I have already run a check/repair, but I ran it again for you – all were “ok.” I believe those were a one time event caused by the MySQL upgrade and WF not being compatible in some way.
I am still seeing table warnings (as exampled above). Additionally the table wfConfig throws an error (not a warming) on INSERT INTO. I believe this is all related to MySQL’s strict mode. I was going to add IGNORE as a test to see if that is a workaround, as it was for other code I had written in the past, but I wasn’t able to find the proper location.
-Pete
Forum: Fixing WordPress
In reply to: Page and post changes not saving to database properly in 4.5.2FYI, it turned out to be a chaching issue on the server…