Dave Gaskin

I have found the exact same issue with the WooCommerce Stripe Payment Gateway plugin. When activated, I get 500 error on /zh and /ja translations. When deactivated, it goes away and I can access those translations.

Diana,

Thank you for the reply. We’ll give that a try and get back to you if we have further issues.

David

Hi Diana,

Sorry for the delay. I’ve applied the additional style declaration that you suggested and I’m not sure if it’s had any visible effect. What I have noticed is that if a page is not zoomed to 100% on desktop, the “perceived” image size in the browser can cause the zoom function to trigger early/late, i.e: when not hovering over the image or when hovering over the image.

I use the WP Image Zoom plugin on a sister site to the one I linked to previously. Currently, the zoom function isn’t working at all on this sister site: https://bodegabar.ca/.

I’ve verified the .zoooom class is applied to the images (menus) and no custom CSS is added on the images. I’ve also deactivated Lazy Loading on Jetpack by still I’m not able to trigger the Zoom function.

On the back-end of Elementor, when I edit the image, I can see the class applied and see the text on the image that says ‘Zoom applied to the image. Check on the frontend’.

I’m hoping you can take a look at the sister website and diagnose what is wrong?

Thanks very much,
David

• This reply was modified 2 years, 2 months ago by Dave Gaskin. Reason: Add additional detail

Thank you, that worked great!

Much appreciated!
Dave

Hi Rafiz,

Thanks for the response. I strongly prefer not to use a plugin. Is there a code snippet you can suggest that I can put in my child theme functions.php file instead?

Hi Diana,

My apologies, I had hidden the tabbed section and changed the display to fix the problem temporarily.

I’ve set up a test page to recreate the issue: https://tapabar.ca/test-page/

Please be sure to check both tabs, accessing the image from different angles, and refreshing the page, as sometimes the behavior changes.

My instinct tells me this has something to do with the container the images are in. Possibly setting a flexible height or fixed height on the container may be something to do with resolving this.

Thanks for you attention on this,
David

Okay, but isn’t your plugin supposed to prevent users like this from being able to “register”? What am I doing wrong?

Okay, I looked at the Activity and Traffic and it appears like these two IP’s were attempting to do some malicious stuff.

https://drive.google.com/file/d/1jF265gVVqxgqdCfZr86Pk8a28BkNPv2K/view?usp=sharing

I guess my question is, what do I do from here? Are they already in the system? It says they’re Local users? Do I need to take action?

Alright, I solved this.

Before, I was stuck in a redirect loop when I tried logging in to my subsites from my main network admin dashboard.

With the help of this article https://bobcares.com/blog/wordpress-multisite-redirect-loop/, I simply added the following lines to my wp-config in the folder where my multisite install lives after all the multisite definitions and still in the “safe zone”.

define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');

I created a new staging site in the server root and converted it to multisite. So far so good.

Now trying to add ‘New Sites’…

I can only use subdomains in this case. Problem is, the subdomains I want to use already exist on the server.

So after adding them and clicking on ‘Dashboard’, I’m sent to login to my existing subdomain.

How can I get around this? Create another staging site of my subdomains??

Thanks @jnashhawkins. I would have liked to have done that (install the multisite in the server root) but there was already an active site there. I guess I can attempt to use the Staging feature in cPanel to create a copy of the current live site and attempt to make the transition there. I wish I would have known that form the start! lol

I feel like I’m really close on the current set up but that to fix the issue would require a search and replace in the database for the subsite and I still don’t know if that would fix the issue.