sgclark

I would like to do the opposite. I’m on a quest to clean up the disaster that is the back end of my WP site. For some reason, when I was a “noob” I had all my images uploaded to the /uploads/ folder only. As such, I have a ton of images in the /uploads/ folder. I have since changed WP to upload images to /uploads/year/month/ folder taxonomy.

I would like to move all the images that sit in /uploads/ into the appropriate /uploads/year/month/ on my site’s doc tree (based on image create date), without completely decimating my front end site that still actively has links/displays many of the images in the root /uploads/ folder.

I was excited to find your plug in to do this, but after installing realized that you don’t display the actual files in the /uploads/ folder.

Is there any way for me to do what I describe above other than moving the files individually/manually (like an animal) and then having to go fix the front end pages/code accordingly?

Thanks for the details. So yeah, it seems that the option combo I have selected has no impact on the serving of the images. I have tried the Tiled Gallery block but that look is not what I’m going for with my galleries, so that’s a non starter.

I’ll take a look at the plug-ins I employ to see if there is a conflict.

Hi

So I tested out all the variations of the options.

When I turn on “Enable Site Accelerator” and have both options enabled (Speed Up Image Load Times + Speed Up Static File Load Times), the issues that I describe happen.

When I select only “Speed Up Image Load Times”, the issues persist.

When I change to only select “Speed Up Static File Load Times”, the issues go away.

Could you explain what this should tell me? Could you also explain what the difference is between the two choices?

I have not yet disabled plugins and checked against them however I will do that over the next day or so.

Thanks
Stephen

That worked! Thanks Rui! Appreciate the quick response!

Thanks. Appreciate it.

The demo page is not even rendering either when I checked earlier.

sgc

Hi:

Thanks for sending this along. I was able to use this as you instructed and it did work with a couple of adjustments. The initial CSS code you shared only worked for the top level nav and not the sub nav. I repurposed what you shared for the sub nav and that seemed to work fine. Also, I was seeing a smaller ‘jump’ with the 5px you originally included. I adjusted that to 4px and it removed all movement! So I think we’re at a solution!

/*JUMPING TEXT FIX - FROM APP DEVELOPER*/
.mobmenu-content li a:active, 
.mobmenu-content li:active,
.mobmenu-content li a .mob-expand-submenu:active {
    border-bottom: 4px solid #fff !important;
}
.mobmenu-content .sub-menu li a:active, 
.mobmenu-content .sub-menu li:active {
    border-bottom: 4px solid #fff !important;
}
/*JUMPING TEXT FIX - FROM APP DEVELOPER*/

• This reply was modified 4 years, 6 months ago by sgclark.

Actually I spoke too soon. I disabled that plug in and the nav/menu seems to be working now. but the text jumping still appears to be happening. It happens on click. The text below the item I’m clicking jumps up a few pixels. It could be a CSS conflict…I’m not sure. I’ve looked and can’t figure it out so was jus wondering if you may know where i should look?

I had not seen it malfunctioning but I went ahead and disabled “SG Optimizer” (which is from my site host) and that did seem to do the trick! I did not catch that previously so thanks for pointing that out!

Stephen

I don’t understand what you mean by ‘the form is not visible as the main form element has ‘display:none;’. I’m seeing the form perfectly fine in my browser. Could you clarify what you mean?

What I want is for the “Submit” button to be moved up closer to the form itself. So there is not so large a gap of white space between the message field and the button. Make sense? See screen shot below.

https://www.dropbox.com/s/dx46no7raa1foi6/Screenshot_2020-05-20_17_56_29.png?dl=0

• This reply was modified 4 years, 6 months ago by sgclark.

Sorry, I don’t understand what you are saying. Could you re-phrase what you would like me to do. Alternatively, I’m fine just waiting it out until the next release. The current version is working just fine.

Sounds good. Will do.

The only other ‘enhancement’ I can think of right now would be to offer up some ‘out of the box’ design touches. For example, on my own, I implemented a little shading under the header when a user scrolls down the page. Would be a nice design touch to offer this and any other ‘basic’ embellishments as an option.

Whoo hoo! That did the trick too! Consider that item resolved. I’ll dig into my child theme or master theme code to see what is going on there.

Thanks for all your help today. Really appreciate it!

I have one enhancement suggestion however I don’t know if my ‘use case’ of using the “Mobile Menu” on any screen size (Menu Visibility = 5000px) is common or an outlier:

On the Menu settings, you provide the option to select the ‘Menu Panel Width’ which is a ‘global’ setting against any screen size. It would be awesome to see if there was a way to select one width for desktop size and another for mobile size. Essentially, I’d prefer to have the width of the “Menu Panel” be smaller/thinner on the desktop than on mobile. Right now, with the one ‘global’ control, it extends to 50% of the window for all screen sizes.

To be clear, this is a super super minor ‘nit pick’, and please don’t waste too much (if any) time on it, but just wanted to note it as something maybe to think about in the future.

Thanks again for all your help!

Regarding the header issue, I added that CSS snippet and that did the trick (without the !important). The header color issue has been resolved! Whoo hoo!

Thanks. I’ll try that CSS.

And I’m still seeing some minor CSS issues. For example, in Chrome (not seeing it in Safari), when I navigate to the sub-menu, the ‘parent’ menu item displays a thin dotted border around it. This did not happen in previous version. Have tried messing with CSS on my style sheets with no luck. Not sure what the root cause is. Please see screenshot below:

https://cl.ly/577c03c83510