Forum Replies Created
-
in reply to: Removing breadcrumbThis reply has been marked as private.in reply to: Removing breadcrumb
Thanks, this is perfect! Have a good day
in reply to: Removing breadcrumbThis reply has been marked as private.in reply to: Removing breadcrumbThis reply has been marked as private.in reply to: Removing breadcrumbThis reply has been marked as private.in reply to: Removing breadcrumbOk, but before we exchange credentials, I guess the solution is just to hide it using css:
.header_page{
display: none;
}Or perhaps a custom child theme?
Thank you
in reply to: Unexpected warning with header style optionI’ve reinstalled everything on a remote Debian install, but then I could not reproduce the problem, so I’ll leave it to that at this point and come back to you if anything.
in reply to: Unexpected warning with header style optionAlso, there is this other issue which might be related to this one. There is a very weird formatting with the header. I’ve tried and reproduced this issue on a fresh install:
– create a fresh wordpress install on a new database
– install specular and all of its required plugins
-> at this point the header displays normally on chrome or firefox
– change the header style to any other style
– change it back to simple style (or use the reset option)
-> the header lack any spacing (on firefox or chrome (cache deactivated))Thanks for your help
in reply to: Unexpected warning with header style optionAdding header_2 to the conditions seems to be enough. Does it make sense with the rest of the code?
in reply to: Unexpected warning with header style optionI’ve added a debug line in header-classic.php, and as the warning said, the variable does not exist at line 74. Printing some more shows that “codeless_get_mod(‘header_style’)”‘s value is ‘header_2’, so that initialization of said variable is skipped all together on condition of line 44
in reply to: Unexpected warning with header style optionAll these variables where updated accordingly in the php.ini and php version was updated to 8.2.0, but the warning’s still there