sushikishi

After not making much progress, I decided to…check my spam folder. All of the
emails WordPress was sending me regarding my site errors ended up there. Nice!

If I use the official Bands Child Theme, previewing it or activating it throws this error:

An error of type E_COMPILE_ERROR was caused in line 286 of the file /var/www/html/wp-content/themes/bands/functions.php. Error message: require_once(): Failed opening required '/var/www/html/wp-content/themes/bands-child/plugins/plugin-activation.php' (include_path='.:/usr/share/php')

I downloaded the /plugins/ directory from the parent theme and uploaded it to the child theme folder, and everything seems to be working as intended now. I would have e-mailed support, but I think the issue is fixed now, and someone else might run into the same issue later.

Dang, I thought that might have worked, but no luck.

I have edited the bands2 theme I uploaded, but the default bands theme is there unmodified, and was just updated to 1.0.3. The official child theme doesn’t have a preview image when I look in at the Theme Selection page. When I use the Live Preview, it goes to the White Screen but I can back out and keep using the site. If I actually activate it, I need to FTP in and remove the theme to get back to the site.

It’s gotta be something like a plugin fouling everything up, when it’s not 3:40AM I’ll go through testing those one-at-a-time, I guess. It really could be anything, but the one thing i’m thinking of that directly affects the layout is a PHP Snippet plugin I’m using that adds something to the footer even if I’m not using a snippet on that page.

I tried that file and went one by one, but it just wasn’t having it. *shrug* I did find a plug-in that handled the changes for me (HTTP Headers), and explained what all of the options did. I didn’t get too fancy with it, I just added the headers that were recommended, and Site Health is happy now.

I wonder if maybe uploading it through FTP was changing the permissions/accessibility of the file itself. I decided to dive in head-first and build everything from the ground up on Ubuntu and learn as I go, so it’s entirely possible it’s some rookie goof-up like that. Either way, I’m marking it as solved — I got where I was going to in the end. Thank you!

When I turned on “Stop editing the .htaccess file”, the Really Simple SSL part of the .htaccess file was removed. I turned all of the Really Simple SSL .htaccess switches off and on again.

First, I turned Enable WordPress 301 redirect on, Enable 301 .htaccess redirect on, Stop editing the .htaccess file off. My htaccess file contained this:

# BEGIN rlrssslReallySimpleSSL rsssl_version[4.0.15]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

And if I were to insert the lines on that version, I’d put it after the first #BEING rlrsslReallySimpleSSL comment line. That’s what I tried before, though, so instead I:

Turned on “stop editing the .htaccess file”, which resulted in this .htaccess content before I did anything else:

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

And there isn’t a ReallySimpleRSS section to add the headers too, so I’d added them at the very top, except that still resulted in an internal server error and I had to revert my .htaccess file.

The contents of the file that didn’t work were:

# Really Simple SSL
Header always set Strict-Transport-Security: "max-age=31536000" env=HTTPS
Header always set Content-Security-Policy "upgrade-insecure-requests"
Header always set X-Content-Type-Options "nosniff"
Header always set X-XSS-Protection "1; mode=block"
Header always set Expect-CT "max-age=7776000, enforce"
Header always set Referrer-Policy: "no-referrer-when-downgrade"
# Really Simple SSL End

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Ahh, see, I understood how what you told me works, I just don’t always know what elements to have the CSS update for the thing I want to manipulate. I guess I’m hitting that “back in my day” part of my life now, I remember just typing in what I wanted where I wanted blah blah blah CSS grumble grumble grumble. I had fun in tech classes in middle and high school, mostly just stuck to WordPress stuff after that without diving too much into CSS and really tweaking the themes, then I just haven’t done any sort of web content outside of streaming to Twitch, so I’m still trying to cobble together the bits and pieces of things I picked up over time into something workable.

My best bet is probably to add the custom class. Even if what I wanted was to allow all of the images as much space as they want I don’t know how that will affect things elsewhere in the theme, and if I break something at least it’ll just be that one thing.

Thank you so much!

I’m using the Twenty Twenty theme, and yes, I mean images blocks with the Gutenberg editor.

I can see when using customizing CSS that the general page width for context and other elements expands or contracts as expected, but the image only expands so far and seems capped less than the rest of the content.

The site should be back live again, though now it has all of the default starting content. I’ll throw an image on there so someone can look at it, though.

Edit: Found the edit button, huzzah! The front page is now displaying the problem well, I think. https://sukidesu.live The images do appear as expected in the editor, but not live.

• This reply was modified 3 years, 9 months ago by sushikishi.
• This reply was modified 3 years, 9 months ago by sushikishi.
• This reply was modified 3 years, 9 months ago by sushikishi.

I don’t seem to be able to edit/delete my original post, but I wasn’t happy with how s l o w the shared server space is, so I decided to dive in head-first and try to install WordPress manually on an Ubuntu server.

So, for the time being, the page is wholly in accessible, but the question remains unsolved — the width of images seemed capped to a lower value than the width of the page.