This has been resolved during a live-chat session by ensuring both the slider background image and the hover image are exactly the same dimensions and set to the same position in the layout. :)

Hi there Nico I got a reply back from the developer who suggested decoding the hex values in the URL with a simple tool like this one: http://ddecode.com/hexdecoder/ ...then enter the resulting HTML directly in the 404 whitelist field, like so: forms/sell-your-car/{Upload Passenger Side Front Corner:24 I tested the above on my test site and it works just fine. :) Could you please test on your site in latest Defender to see if that works for you as well?

Hi there Sascha There are no plans to support converting transparent PNG to JPG as the JPG format does not support transparency. :) And no, I'm not aware of any plans to support transparent PNG at all; they are simply ignored by Smush. So if you have transparent PNG images that you'd like to optimize or convert to JPG with any solid background, you'd want to do that before uploading them using either any image optimization software you may have installed on your computer, or try an easy online tool like this one: https://tinypng.com/

Hi there Phil Samcro Following up on the question you asked about this in live chat, you'd want to replace this in your code: <circle fill="none" stroke="currentColor" stroke-miterlimit="10" cx="115.985" cy="115.985" r="115.485"></circle> ...with this instead to create a simple hexagon with a thin outline: <polyline points="87,0 174,50 174,150 87,200 0,150 0,50 87,0" style="fill:none;stroke:currentColor;stroke-width:1"/>

Yes indeed, both options work just fine for subsites at their original un-mapped URLs. The issue happens when a subsite is mapped to a custom domain; for some reason, the code doesn't recognize the domain-mapped subsites and can't link to them. For example, here's a little video showing how option #2 works for non-domain-mapped subsites (same result in subdomain or subdirectory multisite): https://recordit.co/kq7IEnMVTY In that example, the user is a user on both the main site and one subsite. Regardless of what may be set as the Primary in the My Sites screen, the menu item I added always links to that subsite. And that same link still points to the same user's subsite when added to the menu on other subsites as it checks for the current user and points to that user's site.

Hi again Peter Fae I got your email with the FTP creds, but did not need to use them after all. Once I read your latest post above, I did some more testing on my test multisite with domain mapped subsites and can confirm the same behavior as you observed with both of those plugin options. Further testing on my test site with various other approaches in the code reveals that nothing seems to be working as we want: none of the options I've tested actually recognize a domain-mapped site, much less link to it. Both options work splendidly with subsites that are not domain mapped, but can't get it to work at all with domain mapped ones. So I'm afraid this may need more extensive custom development than we can provide you. For that, you may want to consider contacting the fine folk over at Codeable.io where you can get a $65 discount off your first job with them using the coupon link from our partners page: https://premium.wpmudev.org/partners

Hi again Peter Fae Sure thing, I can check that. Please send FTP credentials using our secure contact form here: https://premium.wpmudev.org/contact/#i-have-a-different-question Be sure "I have a different question" is selected in the options there. Then use this as the Subject line to ensure it gets routed to my inbox: Attn: Patrick Cohen

Yup, I see the new site, good job. Now just go here: https://premium.wpmudev.org/hub/hosting/?view=site&site_id=leyakoreya And fill out the form in the popup with the FTP credentials to connect to the existing site. If you don't see the form right away, go to the Tools tab and click Begin Migration to make it appear. And no, the existing site won't be affected at all. The migration tool actually copies everything over to the new site to make an exact duplicate of the existing site here. You can then check that everything works and looks OK on the new site here, and compare its performance to the existing one before deciding if you want to point the domain name to the new site here.

Hi again, #1: Correct, in WordPress multisite, they sign up on the main site, so they're added as users to the main site, whether BuddyPress is installed or not. #2: Wherever they are in the network, if the adminbar is accessible, they just click the My Sites link to see all sites they belong to; see screenshot :) #3: You'd add either code snippet I provided as a mu-plugin; same process as with the snippet provided by Adam in that other topic. You could also add the code to that existing mu-plugin you already have, after the existing code in the mu-plugin; just be sure to remove the opening <?php tag from the code you add or the thing will break. ;) Then use this in the URL field of a custom menu item: #bp_site_link# #4: Oh, I thought you wanted to direct them to the wp-admin of their site lol. So to fix that in whichever snippet you choose to use, change this line: 'content' => $user_blog->path . 'wp-admin', ...to this instead: 'content' => $user_blog->path,