skinny8

I am going to try a WildCard Let’s Encrypt SSL certificate, currently, it is https://moreskinny.io/

I don’t recall the origin of the current SSL as it has been a while and I changed it a few times during the life of the site.

I will or would like to use Really Simple SSL once I complete the WildCard Let’s Encrypt SSL certificate install/setup. Is there any files I need to edit after, or is it purely detecting the SSL config?

Okay, a little more info. domain/wp/ recognizes the root directory SSL but issues the warning ‘install the certificate in trusted root authorities store’ . . .

The plugin is still giving various warning including, “No SSL detected. Use the retry button to check again.”

I solved the issue, it had something to do with the clarify plugin. It worked before, so I assume it had to do with an update conflict.

The screen size issue I didn’t solve totally but made it somewhat workable!

@iandunn Regarding ‘classic’ issue, I gave theme support team login details, and they suggested, “I can see the issue you are facing and tried to debug it. But I am not able to find the source for this. Can you please try temporarily deactivating all plugins for a few minutes and see if that helps. Also, install and activate the default WordPress theme (Twenty Nineteen ) and observe differences.”

I will try this again in a more detailed way, and maybe even delete all plugins and reinstall them one by one this weekend.

I will update this thread if I figure out what caused it, it seemed to occur suddenly and may have coincided with an update.

@iandunn Regarding Screen size (and since I can’t edit actual pages because of the other issue, this may be tricky to experiment with without breaking my page or converting it to ‘classic’ blocks if I save anything).

Basically, the starter site I began with has a header image that goes behind the logo and menu. The site is santa-fe.tours. This image is set to 1920 pixels on the page and boxed, in a section block. The primary header is set to ‘content width’ is the header section of the Customize.

It would be hard to find all the different sections I played with trying to fix these issues with the other situation, but on the page I choose somewhere ‘use customize settings’ and tried to play with spacing (both margins and padding) in this section block to fix both the iPad/tablet and larger screen sizes with no effect.

The issue with my design is the logo is transparent and the text is white which looks best over the images (also the menu text is white), but if the background image doesn’t cover or align the logo title and menu aren’t visible in these other sizes. It also appears to zoom in on the background images in these sizes, or outside of laptop and mobile (to correct this I tried various combos of cover, and image alignment with no result).

Besides the super-zoomed in images, I could just make my logo and menu text another color, but it looks really good in white ?? I just don’t see, as I said, with all these controls why boxing the design on larger screens isn’t working or why if there are going to be all these options, why I can’t solve one part of this issue by displaying the mobile version on tablets/ipads.

I also am not totally unfamiliar with design issues and it is really hard to believe that the regular WordPress user isn’t going to have even more issues with all these controls and the seemingly very difficult task designing a relatively simple site for both mobile and desktops. I’m am not asking that it be responsive at all levels, and am fully happy with a workable mobile and laptop version if the remaining sizes don’t look totally messed up as they appear to now.

@iandunn Regarding “Classic” Blocks

Here is the other, similar earlier issue that sounds similar: https://www.ads-software.com/support/topic/can-get-out-of-classic-block-editor/

I looked at HTML, and the comments you describe appear in sections affected but appear to describe the incorrect block.

Here a block of another configuration originally was converted to a paragraph:

<!– wp:paragraph –>
<p></p>
<!– /wp:paragraph –></div></section>
<!– /wp:uagb/section –>

The reusable blocks, I assume this is one, I can’t tell likely without going to the reusable block editor page likely, but maybe they’re being converted to paragraphs also.

<!– wp:block {“ref”:1332} /–>

What is weird, is I tried to recreate my footer section when this first occurred using a more advanced block with columns and a background image, likely various elements within a section. Anyway, when I try and edit this block all these elements are removed now in this new block too.

I’m not sure what the ‘classic’ block label means, but maybe it is just converting certain or even all blocks to paragraphs.

Actually, in Revolution Slider there were several ways to bypass the issue. From kind of a protective mode if another JS was interfering to serving slides only on mobile or desktop thus getting at the root of my need/issue by dealing with those images separately.

In the end though, I went for a boxed layout and have been letting Cloudinary take care of images, am aiming to have it take over retina.js functions too.

[ It seems to, was working before I installed/activated it. Granted, I’m also running minification and a number of optimation steps after on everything, so there are various layers of possible additional errors and worlds of hurt which may be going on too.

Although Revolution slider seemed to break even with all or must of these cleared, just after activation. ]

Page builders and Revolution slider have issues but are popular and useful for features and convenience in WP, as is WP itself over cleanly coding each page individually. There are tradeoffs for sure, but like with Retina.js and the @2x file naming convention, it would add a lot of convenience/value for not just me if the rwp-not-responsive class could be applied specifically on files named a certain a way, or to have that option in what seems like a great/useful plugin.

I’m hearing document.querySelectorAll() and querySelectorAll could do something like this, and maybe I can hack together a sidecar JS somehow, but I don’t think I’d be the only person with this issue/need who is not a programmer, and it might be a logical step to making the already present rwp-not-responsive class easier to apply.

https://stackoverflow.com/questions/50894245/adding-specific-class-to-all-images-with-specific-naming-convention-with-js?noredirect=1#comment88788658_50894245

I am not a programmer, and on the user end, it would be really helpful if we could exclude images based on naming the images (like with Retina) and then something in the code, or additional code, would then automatically add in an exclusion.

Like this, but it is beyond me to adapt it:

https://stackoverflow.com/questions/35928150/adding-a-class-to-all-the-images-within-a-div-using-javascript-vice-versa

Okay, turns out I can serve different image sizes to Revolution Slider via turning slides off and on different devices.

So all I need to know is how to exclude Revolution slider from Responsify WP?

All I can find that may fit this situation is to:

“Ignored images
There might be times when you simply don’t want RWP to do anything with an image. This can be achived by adding the rwp-not-responsive class to the image.”

I guess I need to somehow apply this class all revolution slider images.